Automate Builtwith tasks via Rube MCP (Composio). Always search tools first for current schemas.
cd ~/.claude/skills
git clone https://github.com/ComposioHQ/awesome-claude-skills.git awesome-claude-skills mkdir -p ~/.claude/skills/builtwith-automation
curl -fsSL https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/HEAD/composio-skills/builtwith-automation/SKILL.md \
-o ~/.claude/skills/builtwith-automation/SKILL.md Automate Builtwith operations through Composio’s Builtwith toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/builtwith
RUBE_MANAGE_CONNECTIONS with toolkit builtwithRUBE_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 builtwithAlways discover available tools before executing workflows:
RUBE_SEARCH_TOOLS
queries: [{use_case: "Builtwith 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 Builtwith task"}]
session: {id: "existing_session_id"}
RUBE_MANAGE_CONNECTIONS
toolkits: ["builtwith"]
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 Builtwith-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit builtwith |
| 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
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback
Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions