algodocs-automation
npx machina-cli add skill ComposioHQ/awesome-claude-skills/algodocs-automation --openclawAlgodocs Automation via Rube MCP
Automate Algodocs operations through Composio's Algodocs toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/algodocs
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Algodocs connection via
RUBE_MANAGE_CONNECTIONSwith toolkitalgodocs - 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 toolkitalgodocs - 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: "Algodocs 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 Algodocs task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["algodocs"]
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 Algodocs-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit algodocs |
| 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/algodocs-automation/SKILL.mdView on GitHub Overview
This skill orchestrates Algodocs operations using Composio's Rube MCP toolkit. It emphasizes discovering current tool schemas with RUBE_SEARCH_TOOLS before execution to avoid stale slugs and mismatched inputs.
How This Skill Works
You first discover available Algodocs tools with RUBE_SEARCH_TOOLS to obtain up-to-date slugs and input schemas. Then verify and establish a connection to Algodocs with RUBE_MANAGE_CONNECTIONS (ensuring ACTIVE status). Finally, execute the chosen tool via RUBE_MULTI_EXECUTE_TOOL, passing memory and a session_id; fetch full tool schemas with RUBE_GET_TOOL_SCHEMAS if deeper validation is needed.
When to Use It
- Automating routine Algodocs operations that should be scripted rather than done manually.
- Before running a workflow to ensure you have the current tool schemas and inputs.
- When establishing or validating an ACTIVE Algodocs connection for automation.
- Executing a discovered tool with the correct arguments using the required memory object.
- Bulk or chained operations that require multiple tool executions or batch processing.
Quick Start
- Step 1: RUBE_SEARCH_TOOLS queries: [{use_case: "Algodocs operations", known_fields: ""}]
- Step 2: RUBE_MANAGE_CONNECTIONS toolkits: ["algodocs"], session_id: "<your_session_id>"
- Step 3: RUBE_MULTI_EXECUTE_TOOL with tool_slug from search results, arguments from schema, memory: {}, session_id: "<your_session_id>"
Best Practices
- Always call RUBE_SEARCH_TOOLS first to obtain current tool slugs and input schemas.
- Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing any tools.
- Use exact field names and types as provided by the tool schemas; avoid hardcoding.
- Include memory: {} in every RUBE_MULTI_EXECUTE_TOOL call, even if empty.
- Reuse session IDs within a workflow and fetch new ones only for new tasks.
Example Use Cases
- Example 1: Discover Algodocs tools with RUBE_SEARCH_TOOLS and run a single operation using the returned tool slug and validated inputs.
- Example 2: Connect to Algodocs via RUBE_MANAGE_CONNECTIONS, then execute a sequence of tools with RUBE_MULTI_EXECUTE_TOOL in a single session.
- Example 3: Retrieve full tool schemas with RUBE_GET_TOOL_SCHEMAS to confirm data types before execution.
- Example 4: Use RUBE_REMOTE_WORKBENCH to run multiple Composio tools in bulk for a large Algodocs task.
- Example 5: Handle pagination while listing all Algodocs tools and ensure you iterate through all pages before execution.
