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

SKILL

kit-automation

Name: kit-automation
Author: Composio

Automate Kit tasks via Rube MCP with schema lookup first.

Stars

★ 73,862

Source

GitHub

Updated

2026-08-29

// securityCaution

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

Summary

This skill is primarily prompt/documentation-based and does not itself require local installation, secrets, or built-in code execution. However, it directs users to connect to a remote Rube MCP service and perform external tool operations via Composio/Kit, so external-service and authorization considerations warrant mild caution overall.

CredentialsCaution

The material says 'No API keys needed,' but it requires establishing an ACTIVE Kit connection via `RUBE_MANAGE_CONNECTIONS` and following an auth link to complete setup. This implies possible third-party account authorization or OAuth tokens, while the document does not specify scope or storage details.

Network egressCaution

The README explicitly instructs adding the remote MCP endpoint `https://rube.app/mcp` and using Composio/Kit to discover and execute tools. Queries, session IDs, and tool arguments would be sent to declared external services; the exact data egress depends on workflow inputs.

Code executionLow risk

Based on the material, this skill is prompt-only operational guidance and does not include local scripts, install commands, or direct requests to start local processes. While it references remote tool capabilities such as `RUBE_MULTI_EXECUTE_TOOL` and `RUBE_REMOTE_WORKBENCH`, the skill itself does not show local code-execution privileges.

Data accessCaution

The skill text does not declare direct local file read/write access, but it would handle user-supplied task data, arguments, and session information through remote tool discovery, connection management, and execution flows. The actual data scope depends on permissions granted after connecting Kit, and the document does not define least-privilege boundaries.

Supply chainLow risk

The source is a GitHub-hosted open-source repository with strong community adoption (~64.7k stars). The audited artifact itself is documentation/skill content, which is relatively auditable. Although the license is unspecified and maintenance status is unknown, the supply-chain risk is overall low given the prompt-only nature and strong community signals.

Recommendations

Before connecting, verify the privacy policy, data retention, and authorization scope for `rube.app/mcp` and Composio/Kit.
When completing `RUBE_MANAGE_CONNECTIONS` authorization, grant only the minimum permissions needed for the task.
Avoid submitting unnecessary sensitive data in tool queries or execution arguments.
Test in a controlled environment first and document which external tools are called and what data is sent.

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 "kit-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/kit-automation/SKILL.md
2. Save it as ~/.claude/skills/kit-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// docs

Kit Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/kit

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["kit"]
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 Kit-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `kit`
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 V0 workflows via Rube MCP using current tool schemas first.

ComposioGet→

$ loading_