$ ~/registry/skill/composiohq-composio-skills-templated-automation

SKILL

templated-automation

Name: templated-automation
Author: Composio

Automate templated workflows via Rube MCP after checking current tool schemas.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

Prompt only, no code
Open source
Community-trusted· 64.7k

Summary

This skill is primarily a prompt-style wrapper, but it is designed to drive remote Templated operations via Rube MCP, so the overall posture is best rated as caution rather than high risk. The materials do not require local API keys, and the source is a high-star open repository, which lowers supply-chain risk; however, actual use depends on external MCP services and remote connections, creating normal data egress and remote action exposure.

CredentialsCaution

The material states there are no local API keys, but it requires activating a `templated` connection through `RUBE_MANAGE_CONNECTIONS` and following an auth link to complete setup. This shifts credential handling to the Rube/Templated connection layer; while there is no explicit sign of credential theft, it still involves the normal exposure surface of third-party authorization tokens.

Network egressCaution

The README explicitly requires adding the remote MCP endpoint `https://rube.app/mcp` and using Composio/Rube to discover and execute tools; therefore task inputs, session IDs, and tool arguments may be sent to that external service. The endpoint is consistent with the stated purpose, and there is no clear sign of unrelated or hidden exfiltration, but normal remote data transmission is involved.

Code executionLow risk

Based on the objective checks, this skill is prompt-only and does not itself include auditable local code execution, process spawning, or system command capabilities. The documented execution path is through remote MCP tool calls rather than directly asking the host machine to run scripts.

Data accessCaution

The skill itself does not claim direct local file read/write access, but through remote tools such as `RUBE_SEARCH_TOOLS`, `RUBE_MULTI_EXECUTE_TOOL`, and `RUBE_REMOTE_WORKBENCH`, the effective data scope depends on the connected Templated/Composio tool schemas and granted permissions. The materials do not show obviously excessive system permission requests, but remote tool use still warrants minimizing the data you provide.

Supply chainLow risk

The source is an open GitHub repository with strong community adoption (64.7k stars), which materially lowers supply-chain risk; the materials are also consistent with a skill-description/README artifact. Although the license is not declared and maintenance status is unknown, that governance gap alone is not enough to justify a high-risk rating.

Recommendations

Enable it only after confirming that `rube.app/mcp` and Composio/Templated are the services you expect, and verify the OAuth authorization domain.
Do not submit unnecessary sensitive data in tool discovery, execution arguments, or session context; minimize inputs wherever possible.
Review the granted scopes when connecting `templated`, and regularly remove unused third-party connections and tokens.
For higher assurance, inspect the linked toolkit docs and actual schemas to confirm the precise data permissions of the remote tools.

Audited by: gpt-5.4 · 2026-06-16

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "templated-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/templated-automation/SKILL.md
2. Save it as ~/.claude/skills/templated-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// docs

Templated Automation via Rube MCP

Automate Templated operations through Composio's Templated toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/templated

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
Active Templated connection via RUBE_MANAGE_CONNECTIONS with toolkit templated
Always call RUBE_SEARCH_TOOLS first to get current tool schemas

Setup

Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.

Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
Call RUBE_MANAGE_CONNECTIONS with toolkit templated
If connection is not ACTIVE, follow the returned auth link to complete setup
Confirm connection status shows ACTIVE before running any workflows

Tool Discovery

Always discover available tools before executing workflows:

RUBE_SEARCH_TOOLS
queries: [{use_case: "Templated operations", known_fields: ""}]
session: {generate_id: true}

This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls.

Core Workflow Pattern

Step 1: Discover Available Tools

RUBE_SEARCH_TOOLS
queries: [{use_case: "your specific Templated task"}]
session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["templated"]
session_id: "your_session_id"

Step 3: Execute Tools

RUBE_MULTI_EXECUTE_TOOL
tools: [{
  tool_slug: "TOOL_SLUG_FROM_SEARCH",
  arguments: {/* schema-compliant args from search results */}
}]
memory: {}
session_id: "your_session_id"

Known Pitfalls

Always search first: Tool schemas change. Never hardcode tool slugs or arguments without calling RUBE_SEARCH_TOOLS
Check connection: Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools
Schema compliance: Use exact field names and types from the search results
Memory parameter: Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({})
Session reuse: Reuse session IDs within a workflow. Generate new ones for new workflows
Pagination: Check responses for pagination tokens and continue fetching until complete

Quick Reference

Operation	Approach
Find tools	`RUBE_SEARCH_TOOLS` with Templated-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `templated`
Execute	`RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs
Bulk ops	`RUBE_REMOTE_WORKBENCH` with `run_composio_tool()`
Full schema	`RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef`

Powered by Composio

Automate Agenty tasks via Rube MCP after checking current tool schemas first.

ComposioGet→

$ loading_