docsbot-ai-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/docsbot-ai-automation --openclawDocsbot AI Automation via Rube MCP
Automate Docsbot AI operations through Composio's Docsbot AI toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/docsbot_ai
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Docsbot AI connection via
RUBE_MANAGE_CONNECTIONSwith toolkitdocsbot_ai - 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 toolkitdocsbot_ai - 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: "Docsbot AI 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 Docsbot AI task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["docsbot_ai"]
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 Docsbot AI-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit docsbot_ai |
| 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/docsbot-ai-automation/SKILL.mdView on GitHub Overview
Automate Docsbot AI operations via Composio's Docsbot AI toolkit using Rube MCP. The skill emphasizes discovering current tool schemas, establishing an ACTIVE Docsbot AI connection, and executing tools in a managed workflow to streamline docs tasks.
How This Skill Works
The workflow starts by discovering available tools with RUBE_SEARCH_TOOLS to fetch current schemas. Next, it verifies an ACTIVE connection via RUBE_MANAGE_CONNECTIONS for the docsbot_ai toolkit. Finally, it executes the selected tools with RUBE_MULTI_EXECUTE_TOOL, including a memory payload and a session_id to maintain context.
When to Use It
- Setting up a new Docsbot AI workflow via Rube MCP and docsbot_ai.
- Automating routine Docsbot AI tasks where tool schemas frequently change.
- Verifying an ACTIVE connection before running any Tools.
- Executing multiple Docsbot AI actions in a single session using RUBE_MULTI_EXECUTE_TOOL.
- Processing large doc batches with pagination and session reuse.
Quick Start
- Step 1: Discover Available Tools with RUBE_SEARCH_TOOLS for Docsbot AI tasks.
- Step 2: Check Connection with RUBE_MANAGE_CONNECTIONS for toolkit docsbot_ai and ensure ACTIVE.
- Step 3: Execute Tools with RUBE_MULTI_EXECUTE_TOOL using discovered tool slugs and memory, in a single session.
Best Practices
- Always call RUBE_SEARCH_TOOLS first to get current tool schemas.
- Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools.
- Use exact field names and types from the search results; avoid hardcoding slugs.
- Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({}).
- Reuse session IDs within a workflow and fetch new ones when starting a new task.
Example Use Cases
- Auto-generate a Docsbot report by discovering tools, validating the connection, and executing a set of tools in sequence.
- Batch process: iterate through documents with pagination tokens using RUBE_SEARCH_TOOLS results.
- Update docs after schema changes by re-querying tool schemas before execution.
- Onboard a new Docsbot AI workflow by setting up Rube MCP and connecting docsbot_ai.
- Bulk operation: run multiple tools in a single workflow and store the session context for continuity.
