Builtwith
v1.0.2BuiltWith integration. Manage data, records, and automate workflows. Use when the user wants to interact with BuiltWith data.
⭐ 0· 100·0 current·0 all-time
byVlad Ursul@gora050
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The skill name/description (BuiltWith integration) matches the instructions: it tells the agent to use the Membrane CLI to connect to BuiltWith, list/run actions, and proxy API requests. There are no unrelated environment variables, binaries, or install steps requested.
Instruction Scope
SKILL.md confines runtime behavior to installing/using the Membrane CLI, performing login flows, creating connections, listing and running actions, and optionally proxying to BuiltWith endpoints. It does not instruct reading of unrelated system files, environment variables, or writing configuration outside the normal Membrane CLI flow. The proxy facility can send arbitrary requests to BuiltWith via Membrane—this is expected for an integration but worth noting.
Install Mechanism
The only install step is an npm global install of @membranehq/cli. This is a public-registry install (moderate risk compared with no install). It's proportionate to the skill's needs but you should verify the CLI package source, maintainers, and version before installing global npm packages.
Credentials
The skill declares no required environment variables or credentials and explicitly delegates auth to Membrane. Requiring a Membrane account (and browser-based login) is proportional to the described behavior. No unrelated secrets or config paths are requested.
Persistence & Privilege
always is false and the skill does not request elevated or persistent platform privileges. It can be invoked autonomously (the platform default), which is expected for skills; this is not combined with other red flags.
Assessment
This skill appears to do what it says: use Membrane to call BuiltWith. Things to consider before installing: (1) npm install -g will add a global CLI—verify @membranehq/cli's reputation and version. (2) The Membrane service will handle your BuiltWith auth and proxy requests—ensure you trust Membrane's privacy/security posture since proxy requests may return site data. (3) In headless or automated environments, the login flow requires careful handling of the printed URL/code. If you need to avoid installing a global CLI, ask whether an alternative (server-side integration or existing Membrane account) is available.Like a lobster shell, security has layers — review code before you run it.
latestvk97enwxj4vejjmfd7fhnjgke6d843k66
License
MIT-0
Free to use, modify, and redistribute. No attribution required.