home / skills / composiohq / awesome-claude-skills / algodocs-automation

algodocs-automation skill

safe

/algodocs-automation

This skill automates Algodocs tasks using Rube MCP, prioritizing tool discovery to adapt to current schemas and ensure reliable workflows.

npx playbooks add skill composiohq/awesome-claude-skills --skill algodocs-automation

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

2.9 KB

---
name: algodocs-automation
description: "Automate Algodocs tasks via Rube MCP (Composio). Always search tools first for current schemas."
requires:
  mcp: [rube]
---

# Algodocs Automation via Rube MCP

Automate Algodocs operations through Composio's Algodocs toolkit via Rube MCP.

**Toolkit docs**: [composio.dev/toolkits/algodocs](https://composio.dev/toolkits/algodocs)

## Prerequisites

- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Algodocs connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `algodocs`
- Always call `RUBE_SEARCH_TOOLS` first 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.

1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `algodocs`
3. If connection is not ACTIVE, follow the returned auth link to complete setup
4. 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_CONNECTIONS` shows ACTIVE status before executing tools
- **Schema compliance**: Use exact field names and types from the search results
- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, 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](https://composio.dev)*

Overview

This skill automates Algodocs tasks using Composio’s Algodocs toolkit via Rube MCP. It guides discovery of available tools, validates Algodocs connections, and executes toolkit operations reliably while honoring live tool schemas. The workflow emphasizes searching tools first and maintaining session and memory best practices.

How this skill works

First call RUBE_SEARCH_TOOLS to retrieve current tool slugs, input schemas, and recommended execution plans. Confirm or establish an Algodocs connection with RUBE_MANAGE_CONNECTIONS and ensure the status is ACTIVE. Execute one or more toolkit actions with RUBE_MULTI_EXECUTE_TOOL (including a memory object and session_id), or use RUBE_REMOTE_WORKBENCH for bulk operations. Always obey returned schemas and pagination tokens.

When to use it

When automating document workflows or Algodocs operations programmatically
Before running any toolkit action to avoid schema mismatches
When orchestrating multi-step processes that require session reuse
For bulk or batch Algodocs jobs using the remote workbench
When integrating Algodocs into larger agent-driven pipelines

Best practices

Always call RUBE_SEARCH_TOOLS first — tool schemas change frequently
Verify Algodocs connection via RUBE_MANAGE_CONNECTIONS and ensure status is ACTIVE
Include a memory object (even {}) in RUBE_MULTI_EXECUTE_TOOL calls
Reuse session_id within a workflow; generate new session_id for new workflows
Use exact field names and types from the search results to avoid validation errors
Handle pagination tokens and continue fetching until responses are complete

Example use cases

Discover Algodocs tools and run a document conversion pipeline with schema-compliant arguments
Validate and refresh an Algodocs connection before executing automated ingestion jobs
Perform bulk processing of documents via RUBE_REMOTE_WORKBENCH and run_composio_tool()
Orchestrate multi-step review and publishing workflows with session-based state
Fetch full tool schemas with RUBE_GET_TOOL_SCHEMAS for advanced integrations

FAQ

Do I need an API key to use Rube MCP?

No. Add https://rube.app/mcp as an MCP server in your client configuration; no API keys are required.

What if tool schemas change mid-workflow?

Always call RUBE_SEARCH_TOOLS at the start of a workflow and before each execution to get the current schemas; validate fields before calling execute.