similarweb-digitalrank-api-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/similarweb-digitalrank-api-automation --openclawSimilarWeb Automation via Rube MCP
Automate SimilarWeb operations through Composio's SimilarWeb toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/similarweb_digitalrank_api
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active SimilarWeb connection via
RUBE_MANAGE_CONNECTIONSwith toolkitsimilarweb_digitalrank_api - Always call
RUBE_SEARCH_TOOLSfirst 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_TOOLSresponds - Call
RUBE_MANAGE_CONNECTIONSwith toolkitsimilarweb_digitalrank_api - 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: "SimilarWeb 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 SimilarWeb task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["similarweb_digitalrank_api"]
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_CONNECTIONSshows ACTIVE status before executing tools - Schema compliance: Use exact field names and types from the search results
- Memory parameter: Always include
memoryinRUBE_MULTI_EXECUTE_TOOLcalls, 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 SimilarWeb-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit similarweb_digitalrank_api |
| 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/similarweb-digitalrank-api-automation/SKILL.mdView on GitHub Overview
This skill automates SimilarWeb operations through Composio's SimilarWeb toolkit via Rube MCP. It emphasizes always searching for current tool schemas before execution and requires an active connection to SimilarWeb via the toolkit. Prerequisites include an active Rube MCP connection and the RUBE_SEARCH_TOOLS workflow.
How This Skill Works
Flow starts by discovering available tools with RUBE_SEARCH_TOOLS, then establishing or verifying an ACTIVE connection via RUBE_MANAGE_CONNECTIONS using the similarweb_digitalrank_api toolkit. Finally, tools are executed with RUBE_MULTI_EXECUTE_TOOL using the discovered slug and schema-compliant arguments, and a memory object is included; sessions are reused within a workflow for consistency.
When to Use It
- You need to identify available SimilarWeb tasks and input schemas before building a workflow.
- You want to validate that the toolkit connection is ACTIVE before running any workflow.
- You need to execute a discovered tool with up-to-date arguments sourced from RUBE_SEARCH_TOOLS.
- You’re assembling a multi-tool workflow and need memory and session handling across steps.
- You’re debugging integration and want to fetch full tool schemas for reference.
Quick Start
- Step 1: Get your Rube MCP configured by adding https://rube.app/mcp as an MCP server in your client.
- Step 2: Run RUBE_SEARCH_TOOLS to fetch current SimilarWeb tool slugs and input schemas.
- Step 3: Run RUBE_MANAGE_CONNECTIONS to activate the toolkit similarweb_digitalrank_api, then execute a discovered tool with RUBE_MULTI_EXECUTE_TOOL using memory and a session_id.
Best Practices
- Always call RUBE_SEARCH_TOOLS before execution to get current slugs and schemas.
- Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before running tools.
- Use exact field names and types from the search results; avoid hardcoding.
- Always include memory in RUBE_MULTI_EXECUTE_TOOL calls (even if empty).
- Reuse session IDs within a workflow; generate new ones only for new runs.
Example Use Cases
- Discover SimilarWeb tasks using RUBE_SEARCH_TOOLS and run a specific operation with RUBE_MULTI_EXECUTE_TOOL.
- Connect to SimilarWeb via RUBE_MANAGE_CONNECTIONS and then execute a tool slug from search results.
- Run a bulk set of SimilarWeb tasks using RUBE_REMOTE_WORKBENCH run_composio_tool with multiple tool executions.
- Retrieve full tool schemas using RUBE_GET_TOOL_SCHEMAS to validate fields before execution.
- Debug a failed run by re-discovering tools and rechecking connection, then re-run.
