What is Rube MCP and why is it needed for this skill?

Rube MCP serves as the control plane to discover tools, manage connections, and execute workflows for Sourcegraph tasks. This skill relies on MCP to fetch current tool schemas and coordinate tool execution.

Do I need an active Sourcegraph connection to run workflows?

Yes. Ensure RUBE_MANAGE_CONNECTIONS has toolkits: ["sourcegraph"] and that the connection status is ACTIVE before running any tools.

What about the memory parameter in executions?

Always include a memory object in RUBE_MULTI_EXECUTE_TOOL calls, even if it's empty, to satisfy the API contract and support session/state data.

sourcegraph-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Sourcegraph Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/sourcegraph

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["sourcegraph"]
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 Sourcegraph-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `sourcegraph`
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/sourcegraph-automation/SKILL.md

View on GitHub

Overview

Automate Sourcegraph operations using Composio's Sourcegraph toolkit through Rube MCP. This skill orchestrates discovery, connection management, and execution of Sourcegraph tools, always consulting current tool schemas first to avoid stale slugs or arguments.

How This Skill Works

You first discover available Sourcegraph tools with RUBE_SEARCH_TOOLS to obtain current input schemas. Then you verify and activate the Sourcegraph connection via RUBE_MANAGE_CONNECTIONS. Finally, you execute the selected tool with RUBE_MULTI_EXECUTE_TOOL, supplying the correct arguments and a memory payload, ensuring you reuse sessions where appropriate. The process always references the latest tool schemas to prevent failures from outdated slugs or fields.

When to Use It

When automating a Sourcegraph operation, ensure you fetch current tool schemas first.
When you need to confirm the Sourcegraph connection is ACTIVE before running workflows.
When discovering available tools and their input schemas prior to execution.
When performing a multi-tool workflow within a single session using RUBE_MULTI_EXECUTE_TOOL.
When conducting bulk operations or audits using Composio toolset (e.g., remote bench or schema fetch).

Quick Start

Step 1: Ensure Rube MCP is connected and RUBE_SEARCH_TOOLS responds.
Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkits: ["sourcegraph"] and activate the connection.
Step 3: Use RUBE_SEARCH_TOOLS to discover available tools, then execute a tool with RUBE_MULTI_EXECUTE_TOOL including memory and a session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current tool schemas.
Verify the Sourcegraph connection status is ACTIVE via RUBE_MANAGE_CONNECTIONS before executing tools.
Use exact field names and types from the search results; avoid hardcoding slugs or args.
Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({}).
Reuse session IDs within a workflow and manage pagination tokens when present.

Example Use Cases

Discover a Sourcegraph tool slug and its input schema, then execute it against a target repository with the required arguments.
Check the Sourcegraph connection, authenticate if needed, and run a sequence of tools in a single session.
Perform a multi-step workflow by reusing the same session_id while passing intermediate memory between tools.
Use bulk operations to run multiple tools in a loop, ensuring memory payloads are provided for each call.
Fetch the full tool schemas with RUBE_GET_TOOL_SCHEMAS to audit or refresh your automation scripts.

Frequently Asked Questions

Add this skill to your agents