factorial-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/factorial-automation --openclawFactorial Automation via Rube MCP
Automate Factorial operations through Composio's Factorial toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/factorial
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Factorial connection via
RUBE_MANAGE_CONNECTIONSwith toolkitfactorial - 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 toolkitfactorial - 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: "Factorial 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 Factorial task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["factorial"]
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 Factorial-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit factorial |
| 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/factorial-automation/SKILL.mdView on GitHub Overview
Automates factorial operations using Composio's Factorial toolkit through Rube MCP. It relies on discovering current tool schemas with RUBE_SEARCH_TOOLS before each run and requires an active connection to the factorial toolkit.
How This Skill Works
First, discover available factorial tools with RUBE_SEARCH_TOOLS to fetch current input schemas and tool slugs. Then verify the connection via RUBE_MANAGE_CONNECTIONS and, when ACTIVE, execute the selected tool with RUBE_MULTI_EXECUTE_TOOL, passing the required memory payload. This workflow emphasizes using dynamic schemas rather than hardcoding tool details.
When to Use It
- When you need to run automated factorial computations across datasets with up-to-date tool schemas.
- When you must verify and maintain an ACTIVE Rube MCP connection before execution.
- When tool slugs or input fields change frequently and hardcoding is risky.
- When batching multiple factorial tasks in a single session for efficiency.
- When you want to reuse session IDs to streamline follow-on factorial steps.
Quick Start
- Step 1: Add https://rube.app/mcp as an MCP server in your client configuration.
- Step 2: Run RUBE_SEARCH_TOOLS to fetch current factorial tool schemas.
- Step 3: Run RUBE_MANAGE_CONNECTIONS to ensure ACTIVE, then execute tools with RUBE_MULTI_EXECUTE_TOOL using memory and a session_id.
Best Practices
- Always call RUBE_SEARCH_TOOLS before executing any workflow to obtain current tool slugs and schemas.
- Check that RUBE_MANAGE_CONNECTIONS reports an ACTIVE status prior to running tools.
- Use the exact field names and types returned by the tool schemas.
- Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
- Reuse sessions where possible and handle pagination tokens when listing tools.
Example Use Cases
- Discover factorial tools and run a single computation using a discovered slug.
- Batch run multiple factorial operations in one session to optimize throughput.
- Monitor and re-authenticate the Rube MCP connection when it becomes inactive.
- Fetch updated tool schemas mid-workflow to adapt to changes.
- Use RUBE_REMOTE_WORKBENCH to run composio tools at scale.