Do I need API keys to use Codacy automation via Rube MCP?

No API keys are needed — add the MCP endpoint and follow setup steps.

Why must I call RUBE_SEARCH_TOOLS before executing tools?

Tool schemas can change; searching ensures you have current slugs and required arguments.

What if the connection status is not ACTIVE?

Follow the auth link returned during RUBE_MANAGE_CONNECTIONS to complete setup and recheck status before running workflows.

codacy-automation

Scanned

npx machina-cli add skill ComposioHQ/awesome-claude-skills/codacy-automation --openclaw

Files (1)

SKILL.md

2.8 KB

Codacy Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/codacy

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
Active Codacy connection via RUBE_MANAGE_CONNECTIONS with toolkit codacy
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 codacy
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: "Codacy 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 Codacy task"}]
session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["codacy"]
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 Codacy-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `codacy`
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/codacy-automation/SKILL.mdView on GitHub

Overview

Automate Codacy operations through Composio's Codacy toolkit via Rube MCP. This workflow emphasizes discovering current tool schemas with RUBE_SEARCH_TOOLS before executing tasks and requires an active Codacy connection.

How This Skill Works

Connect to Rube MCP and verify tool schemas with RUBE_SEARCH_TOOLS. Manage the Codacy connection using RUBE_MANAGE_CONNECTIONS, then execute discovered tools with RUBE_MULTI_EXECUTE_TOOL, always including memory and reusing session IDs when appropriate.

When to Use It

You need to automate Codacy tasks end-to-end without manual tool configuration.
Tool schemas change and you must fetch the latest available tools before running a workflow.
You want to verify the Codacy connection is ACTIVE before execution.
You are performing bulk Codacy operations across multiple tasks or repositories.
You need to reuse a session_id within a workflow to maintain context and state

Quick Start

Step 1: Add Rube MCP endpoint (https://rube.app/mcp) and verify RUBE_SEARCH_TOOLS is available.
Step 2: Use RUBE_MANAGE_CONNECTIONS with toolkits: ["codacy"] and confirm ACTIVE status.
Step 3: Run RUBE_MULTI_EXECUTE_TOOL with a discovered tool_slug and proper memory, reusing session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS first to obtain current tool slugs and schemas.
Check that RUBE_MANAGE_CONNECTIONS reports ACTIVE before executing tools.
Use exact field names and types from the tool schemas; avoid hardcoding.
Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
Reuse session IDs within a workflow and generate new ones for new runs.

Example Use Cases

Discover Codacy operations, connect, and run a quality-check tool across a repository.
Automate a series of Codacy tasks by first querying available tools, then executing selected ones with a saved session.
Bulk run lint and code-quality checks on multiple repos using discovered tool slugs.
Rerun a failed Codacy task by reusing the existing session_id and tool slug.
Validate tool schemas prior to execution to ensure compatibility with current Codacy workflows.

Frequently Asked Questions

Add this skill to your agents