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

SKILL

builtwith-automation

Name: builtwith-automation
Author: Composio

Automate BuiltWith tech-stack lookups for research, prospecting, and competitive analysis.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

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

Summary

This skill is essentially a prompt/template, open-source, and widely adopted, so the overall risk is relatively low. The main caution is that its README explicitly depends on remote Rube MCP and a Builtwith connection, which introduces third-party network interaction and account authorization.

CredentialsCaution

The material says there are 'no API keys,' but it requires an ACTIVE `builtwith` connection via `RUBE_MANAGE_CONNECTIONS` and completing auth through a returned link. This implies Builtwith authorization tokens may be delegated to or brokered by Rube/Composio, which creates a normal third-party credential handling risk.

Network egressCaution

The README explicitly requires adding the remote MCP endpoint `https://rube.app/mcp` and using Composio/Builtwith tools for operations. Therefore, user input, tool arguments, session IDs, and query content may be sent to third-party services as part of the workflow. No clearly unrelated or suspicious endpoint is stated, but normal outbound data flow exists.

Code executionLow risk

Based on the provided material, this is a prompt-only skill description and does not include local executable code, install scripts, or steps that require spawning local processes. The mentioned `RUBE_MULTI_EXECUTE_TOOL` and `RUBE_REMOTE_WORKBENCH` are remote tool invocation patterns, not direct local code-execution capability granted by the skill itself.

Data accessCaution

There is no indication that it reads/writes the local filesystem or requests excessive system privileges. However, through the remote MCP it can access data and operations associated with the connected Builtwith account, and it passes `memory`, session information, and task parameters, so there is a normal remote business-data access surface.

Supply chainLow risk

The source is an open-source GitHub repository with strong community adoption (64.7k stars), which materially lowers supply-chain risk. The material does not show closed-source binaries, obfuscated install commands, or obvious injection content. The missing license declaration and unknown maintenance status are worth noting, but they are not sufficient on their own to raise this to high risk.

Recommendations

Only add `https://rube.app/mcp` in a trusted client, and confirm your organization permits sending task data to Rube/Composio and Builtwith.
Use a least-privilege Builtwith account when authorizing the connection, and regularly review/revoke third-party tokens.
Avoid placing unnecessary sensitive information in tool arguments, session fields, or memory.
Before adoption, verify recent maintenance of the repository, the provenance of the skill content, and the privacy/data-handling terms of Composio and Builtwith.

Audited by: gpt-5.4 · 2026-06-16

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "builtwith-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/builtwith-automation/SKILL.md
2. Save it as ~/.claude/skills/builtwith-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// docs

Builtwith Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/builtwith

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["builtwith"]
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 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

Automate IP2WHOIS lookups and related data retrieval through Rube MCP.

ComposioGet→

$ loading_