Skyfire Automation
This skill automates Skyfire operations using the Composio Skyfire toolkit via Rube MCP. It's designed for users who need to streamline and automate tasks wi...
Install
npx promptshop add skyfire-automationDetails
What This Skill Does
This skill automates Skyfire operations using the Composio Skyfire toolkit via Rube MCP. It's designed for users who need to streamline and automate tasks within the Skyfire platform. The skill ensures tools are up-to-date and connections are active before executing workflows.
When to Use
- Automate Skyfire tasks.
- Discover available Skyfire tools.
- Check Skyfire connection status.
- Execute Skyfire tools.
- Update Skyfire tool schemas.
- Verify active Skyfire connection.
Key Features
- Uses Rube MCP to connect to Skyfire.
- Discovers available tools via RUBE_SEARCH_TOOLS.
- Manages connections via RUBE_MANAGE_CONNECTIONS.
- Executes tools via RUBE_MULTI_EXECUTE_TOOL.
- Provides toolkit documentation link.
- Requires active Skyfire connection.
Manual Installation
Skyfire Automation via Rube MCP
Automate Skyfire operations through Composio's Skyfire toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/skyfire
Prerequisites
Rube MCP must be connected (RUBE_SEARCH_TOOLS available) Active Skyfire connection via RUBE_MANAGE_CONNECTIONS with toolkit skyfire 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 skyfire 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: "Skyfire 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 Skyfire task"}] session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS toolkits: ["skyfire"] 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 Skyfire-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit skyfire |
| 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 |