skyfire-automation

Automate Skyfire operations and workflow execution through the Rube MCP gateway.

74.2k|8.5k|Updated Oct 17, 2025
One-click install
npx skills add https://github.com/ComposioHQ/awesome-claude-skills --skill skyfire-automation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skyfire-automation
Source: https://github.com/ComposioHQ/awesome-claude-skills/tree/main/composio-skills/skyfire-automation
Command: npx skills add https://github.com/ComposioHQ/awesome-claude-skills --skill skyfire-automation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the complexity of managing Skyfire operations by providing a standardized, automated interface for tool discovery, connection management, and multi-step execution.

Core Features & Use Cases

  • Dynamic Tool Discovery: Automatically fetch current tool schemas and execution plans via Rube MCP.
  • Connection Lifecycle Management: Verify and manage active Skyfire connections to ensure reliable workflow execution.
  • Multi-Step Execution: Execute complex, schema-compliant tool chains with integrated memory management.

Quick Start

Use the skyfire-automation skill to discover available tools and execute a workflow for your specific Skyfire task.

Frequently Asked Questions about skyfire-automation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I discover available Skyfire tools?

Call the RUBE_SEARCH_TOOLS function with a specific use case query to retrieve current tool slugs, input schemas, and recommended execution plans.

How to verify if my Skyfire connection is active?

Use the RUBE_MANAGE_CONNECTIONS tool with the 'skyfire' toolkit parameter to check the current connection status and obtain authentication links if needed.

Why must I call RUBE_SEARCH_TOOLS before execution?

Tool schemas and slugs are subject to change; calling the search function ensures you are using the most current, valid input parameters for your workflow.

What is the purpose of the memory parameter in RUBE_MULTI_EXECUTE_TOOL?

The memory parameter maintains state across tool executions within a session, and it must be included in every call, even if passed as an empty object.

Can I reuse session IDs for different workflows?

No, you should generate new session IDs for distinct workflows to prevent state contamination, while reusing them within a single workflow for consistency.