$ ~/registry/skill/composiohq-composio-skills-apitemplate-io-automation

SKILL

apitemplate-io-automation

Name: apitemplate-io-automation
Author: Composio

Automate Apitemplate.io template generation and document workflows through Rube MCP.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

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

Summary

This skill is essentially an open-source prompt/workflow guide with strong public visibility and relatively low inherent risk. The main caution is that actual data egress and account authorization boundaries lie in the external Rube MCP and Apitemplate IO services it relies on.

CredentialsCaution

The material says no API keys are needed, but the README explicitly requires establishing an ACTIVE `apitemplate_io` connection via `RUBE_MANAGE_CONNECTIONS` and completing authorization through a returned auth link. So while no local env vars are required, third-party account tokens are still involved, creating normal OAuth/connection misuse risk.

Network egressCaution

The README instructs users to configure `https://rube.app/mcp` as an MCP server and use Composio/Rube to invoke Apitemplate IO tools. User prompts, queries, session IDs, tool arguments, and potentially business data are expected to be sent to these remote services. This egress is consistent with the stated function, but it is a clear external data boundary.

Code executionLow risk

Based on the provided material, this is a prompt-only skill/workflow guide and does not itself declare local process spawning, script execution, or system-level execution privileges. The documentation describes invoking remote MCP tools rather than local code execution.

Data accessCaution

There is no stated access to local files or local system resources. However, once the Apitemplate IO connection is authorized, the remote tools can access or operate on templates and related automation data within that authorized account scope, and they maintain context via session and `memory` parameters, so this should be treated as third-party SaaS account data access.

Supply chainLow risk

The skill is hosted in a public GitHub repository and is marked open-source with high community adoption (64.7k stars), which are strong risk-reducing signals. Caveats are the unspecified license, unknown maintenance status, and the fact that actual execution depends on external Rube/Composio services, so the auditable boundary is not identical to the README itself.

Recommendations

Authorize Apitemplate IO only when needed, preferably with a least-privilege or test account.
Before connecting to `https://rube.app/mcp`, confirm your organization allows sending relevant business data to Rube/Composio and Apitemplate IO.
Avoid placing unnecessary sensitive information in queries, sessions, or tool arguments.
Before production use, review Rube MCP and Composio privacy policy, log retention, and token revocation procedures.

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

// install

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

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

// download

Download SKILL.mdInstall manifest ↗

// docs

Apitemplate IO Automation via Rube MCP

Automate Apitemplate IO operations through Composio's Apitemplate IO toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/apitemplate_io

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
Active Apitemplate IO connection via RUBE_MANAGE_CONNECTIONS with toolkit apitemplate_io
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 apitemplate_io
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: "Apitemplate IO 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 Apitemplate IO task"}]
session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["apitemplate_io"]
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 Apitemplate IO-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `apitemplate_io`
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 PDF API IO workflows via Rube MCP using current tool schemas first.

ComposioGet→

$ loading_