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

SKILL

serpdog-automation

Name: serpdog-automation
Author: Composio

Automate Serpdog search tasks via Rube MCP for scalable result retrieval.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

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

Summary

This skill itself is an open-source prompt wrapper with relatively strong source credibility, and it does not directly require local secrets or local code execution. The main consideration is its reliance on external Rube MCP and Serpdog connections, where real data egress and account authorization occur on remote services, so it is better rated as low-to-moderate concern rather than high risk.

CredentialsCaution

The material says there are no local keys, but the README explicitly requires an active `serpdog` connection via `RUBE_MANAGE_CONNECTIONS` and instructs the user to complete an auth link. So the skill itself does not collect an API key directly, but the underlying service still involves third-party account authorization and normal token misuse exposure.

Network egressCaution

The README instructs users to add the remote MCP endpoint `https://rube.app/mcp` and to discover, connect, and execute Serpdog operations through Composio/Rube. This means task inputs, session IDs, tool arguments, and potentially query content are sent to external services. The material does not define stricter data-flow boundaries, so outbound content and third-party handling should be reviewed.

Code executionLow risk

Based on the provided material, this is a prompt/workflow description rather than an executable installer. It does not declare local process spawning, shell execution, dependency installation, or direct system-level actions; it mainly guides the model to use existing MCP tools instead of directly gaining local code execution.

Data accessCaution

The material does not show direct read/write access to the local filesystem, clipboard, or databases, but it does call connected Serpdog tools through Rube MCP and passes `session_id`, `memory`, and tool arguments in session context. Therefore, the data-access surface is mainly the remote connected data and operation scope, not local data.

Supply chainCaution

On the positive side, the skill entry comes from a GitHub open-source repository with very high community stars, which improves auditability. However, the license is unspecified, maintenance is unknown, and actual operation depends on external Rube/Composio services and their toolchain, so the README alone does not cover the full implementation and some supply-chain caution remains warranted.

Recommendations

Before connecting to `https://rube.app/mcp`, review Rube/Composio privacy terms, data retention, and the scope of Serpdog authorization.
Use a least-privilege Serpdog account or test environment, and avoid sending highly sensitive queries or production data through this workflow.
Inspect the actual tool schemas and parameters returned by `RUBE_SEARCH_TOOLS` before execution to ensure the operation scope matches expectations.
Prefer enabling this skill only in a controlled client and keep logs of external MCP calls for auditability.

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 "serpdog-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/serpdog-automation/SKILL.md
2. Save it as ~/.claude/skills/serpdog-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// docs

Serpdog Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/serpdog

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["serpdog"]
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 Serpdog-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `serpdog`
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 Composio search workflows and fetch current tool schemas via Rube MCP.

ComposioGet→

$ loading_