fomo-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/fomo-automation --openclawFomo Automation via Rube MCP
Automate Fomo operations through Composio's Fomo toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/fomo
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Fomo connection via
RUBE_MANAGE_CONNECTIONSwith toolkitfomo - Always call
RUBE_SEARCH_TOOLSfirst 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_TOOLSresponds - Call
RUBE_MANAGE_CONNECTIONSwith toolkitfomo - 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: "Fomo 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 Fomo task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["fomo"]
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_CONNECTIONSshows ACTIVE status before executing tools - Schema compliance: Use exact field names and types from the search results
- Memory parameter: Always include
memoryinRUBE_MULTI_EXECUTE_TOOLcalls, 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 Fomo-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit fomo |
| 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
Source
git clone https://github.com/ComposioHQ/awesome-claude-skills/blob/master/composio-skills/fomo-automation/SKILL.mdView on GitHub Overview
This skill automates Fomo operations through Composio's Fomo toolkit via Rube MCP. It emphasizes discovering tool schemas first to adapt to changes and avoid hardcoding slugs or arguments.
How This Skill Works
Connect to Rube MCP and ensure RUBE_SEARCH_TOOLS is available to fetch current Fomo tool schemas. Use the Core Workflow Pattern: discover available tools, verify an ACTIVE Fomo connection with RUBE_MANAGE_CONNECTIONS, then execute tools via RUBE_MULTI_EXECUTE_TOOL using the discovered slug and schema-compliant arguments, always including memory. This avoids stale configurations and supports pagination and session reuse.
When to Use It
- You want to automate recurring or batch Fomo tasks with up-to-date tool schemas.
- Tool schemas may change and you must fetch the latest slugs and arguments before execution.
- You need to verify an ACTIVE Fomo connection before running any workflows.
- You want to execute multiple Fomo operations in a single workflow using a single session.
- You’re performing bulk or bulk-like Fomo operations via remote benches.
Quick Start
- Step 1: Ensure RUBE_SEARCH_TOOLS is available by verifying RUBE MCP is connected.
- Step 2: Connect to Fomo with RUBE_MANAGE_CONNECTIONS using toolkit 'fomo'.
- Step 3: Discover tools and run a chosen tool slug with RUBE_MULTI_EXECUTE_TOOL, including memory and a valid session.
Best Practices
- Always call RUBE_SEARCH_TOOLS before any tool execution to fetch current schemas.
- Check that RUBE_MANAGE_CONNECTIONS shows an ACTIVE status before executing tools.
- Use exact field names and types from the live search results; never hardcode slugs.
- Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if empty.
- Reuse session IDs within a workflow and generate new ones for separate workflows.
Example Use Cases
- Discover available Fomo tools with RUBE_SEARCH_TOOLS and run a single Fomo operation.
- Connect to Fomo via RUBE_MANAGE_CONNECTIONS with toolkit 'fomo' and execute a discovered slug.
- Run multiple Fomo actions in sequence using RUBE_MULTI_EXECUTE_TOOL within one session.
- Perform bulk Fomo operations through RUBE_REMOTE_WORKBENCH using run_composio_tool().
- Fetch the full tool schemas with RUBE_GET_TOOL_SCHEMAS and adapt your workflow to schemaRef.
