$ loading_
Automate Codereadr workflows via Rube MCP using current tool schemas first.
This is not a prompt-only skill in practice; the material shows it depends on a remote Rube MCP service and executes actions via Composio/Codereadr connections, so normal cautions apply for network egress, remote tool invocation, and connection authorization. The high-star open-source GitHub source lowers supply-chain risk, but the README lacks concrete details on data scope, endpoint specifics, and license, so the overall posture is caution.
The README says no API key is needed, but it requires creating an ACTIVE `codereadr` connection via `RUBE_MANAGE_CONNECTIONS` and following an external auth link; this implies credentials are likely brokered by Rube/Composio or established via OAuth. There is no evidence of local secret storage requirements, so this is not high risk, but normal caution applies to third-party connection authorization and token misuse surface.
Contrary to the metadata claiming no remote endpoint, the README explicitly requires adding `https://rube.app/mcp` as an MCP server and references composio.dev docs; therefore it will send tool discovery queries, session information, and execution arguments to declared third-party services. This is normal egress for a remote MCP/integration tool, and the material does not show exfiltration to unknown or unrelated endpoints.
The skill does not show local shell or script execution, but it does invoke remote tool capabilities such as `RUBE_MULTI_EXECUTE_TOOL` and `RUBE_REMOTE_WORKBENCH` to perform Codereadr operations. This is remote tool orchestration rather than arbitrary local code execution; the concrete action scope depends on the schemas returned by Rube, and the material shows no request for excessive host-level permissions.
The material does not claim direct local file read/write access; the main data-access surface comes from the authorized Codereadr connection plus queries, arguments, session IDs, and possible workflow `memory` sent to Rube. Since it does not specify what data categories Codereadr access covers or how least privilege is enforced, the actual granted scope should be reviewed during connection setup.
The source is a public GitHub repository with strong community adoption (~64.7k stars), which is a meaningful positive trust signal. What is shown here is a skill description/README rather than an executable installer, reducing the direct supply-chain attack surface; remaining gaps are the missing license declaration and unknown maintenance status, so it is still wise to verify repository freshness and consistency with upstream Rube/Composio docs before production use.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "codereadr-automation" skill from askskill: 1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/codereadr-automation/SKILL.md 2. Save it as ~/.claude/skills/codereadr-automation/SKILL.md 3. Reload skills and tell me it's ready
Automate Codereadr operations through Composio's Codereadr toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/codereadr
RUBE_MANAGE_CONNECTIONS with toolkit codereadrRUBE_SEARCH_TOOLS first to get current tool schemasGet 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.
RUBE_SEARCH_TOOLS respondsRUBE_MANAGE_CONNECTIONS with toolkit codereadrAlways discover available tools before executing workflows:
RUBE_SEARCH_TOOLS
queries: [{use_case: "Codereadr operations", known_fields: ""}]
session: {generate_id: true}
This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls.
RUBE_SEARCH_TOOLS
queries: [{use_case: "your specific Codereadr task"}]
session: {id: "existing_session_id"}
RUBE_MANAGE_CONNECTIONS
toolkits: ["codereadr"]
session_id: "your_session_id"
RUBE_MULTI_EXECUTE_TOOL
tools: [{
tool_slug: "TOOL_SLUG_FROM_SEARCH",
arguments: {/* schema-compliant args from search results */}
}]
memory: {}
session_id: "your_session_id"
RUBE_SEARCH_TOOLSRUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing toolsmemory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({})| Operation | Approach |
|---|---|
| Find tools | RUBE_SEARCH_TOOLS with Codereadr-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit codereadr |
| 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 Docugenerate document generation workflows through Rube MCP for faster operations.
Automate Docsumo document extraction and processing tasks through Rube MCP.
Automate Docupost document and delivery workflows via Rube MCP with schema-first tool discovery.
Automate Doppler marketing workflows and campaign operations through Rube MCP.
Automate Doppler SecretOps secret and configuration management tasks through Rube MCP.
Automate Docnify document tasks through Rube MCP with schema-first tool discovery.
Automate Code Interpreter workflows for coding, analysis, and repeatable task execution.
Automate Codacy tasks to streamline code quality checks and governance.
Automate Composio search workflows and fetch current tool schemas via Rube MCP.
Automate Sourcegraph searches and code workflows through Rube MCP.
Automate Composio tasks via Rube MCP with tool schema lookup first.
Automate remote retrieval workflows via Rube MCP using current tool schemas first.