$ ~/registry/skill/composiohq-composio-skills-algodocs-automation

SKILL

algodocs-automation

Name: algodocs-automation
Author: Composio

Automate Algodocs document and data tasks via Rube MCP with schema lookup first.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

Prompt only, no code
Open source
Community-trusted· 64.7k

Summary

This skill is primarily an open-source prompt-style instruction set and does not directly require local secrets or local code execution, so overall risk is low. However, it is designed to operate Algodocs through Rube MCP, which introduces network interactions and third-party account authorization that warrant attention to data egress and granted permissions.

CredentialsCaution

The material says 'No API keys needed,' but it requires an active Algodocs connection via `RUBE_MANAGE_CONNECTIONS` and completing an auth link, which implies third-party account tokens are involved. While the skill does not directly ask the user to enter secrets into the skill itself, there is still the usual authorization risk of credentials being managed through Rube/Composio.

Network egressCaution

The README explicitly requires adding the remote MCP endpoint `https://rube.app/mcp` and using Composio/Rube to search tools, manage connections, and execute Algodocs operations. This means task arguments, session IDs, connection state, and potentially business data may be sent to the stated third-party service, but no unrelated or covert exfiltration endpoint is evident in the material.

Code executionLow risk

The system checks mark it as prompt-only. The document mainly describes a call flow and does not provide scripts, install commands, or shell instructions to run locally, nor does it request extra system-level privileges.

Data accessCaution

The skill is intended to 'Automate Algodocs operations' and executes dynamically discovered tools via `RUBE_MULTI_EXECUTE_TOOL`. The exact data scope depends on the Algodocs tool schemas and the user's authorized connection. No local file read/write is shown, but the scope of remote business data access is not fully transparent in this document, so least-privilege authorization is advisable.

Supply chainLow risk

The source is an open GitHub repository with high community adoption (64.7k stars), both strong risk-reducing signals. The provided material is reviewable documentation text and does not show an obfuscated installer, closed-source binary, or obvious malicious/injection content. The missing license and unknown maintenance state are worth noting but are not sufficient on their own to raise it to high risk.

Recommendations

Only add `https://rube.app/mcp` after deciding you trust Rube/Composio, and review its privacy and data-handling practices.
Use a least-privilege Algodocs account/connection and avoid granting access beyond what the automation task requires.
Inspect the actual schemas returned by `RUBE_SEARCH_TOOLS` before execution to ensure no unnecessary sensitive fields are sent.
Regularly review and revoke Algodocs/Rube authorizations and sessions that are no longer needed.

Audited by: gpt-5.4 · 2026-06-17

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "algodocs-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/algodocs-automation/SKILL.md
2. Save it as ~/.claude/skills/algodocs-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// docs

Algodocs 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_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.

Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
Call RUBE_MANAGE_CONNECTIONS with toolkit algodocs
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_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

Automate Docsbot AI tasks via Rube MCP using current tool schemas first.

ComposioGet→

$ loading_