Wappalyzer
v1.0.0Wappalyzer integration. Manage data, records, and automate workflows. Use when the user wants to interact with Wappalyzer data.
⭐ 0· 60·0 current·0 all-time
byMembrane Dev@membranedev
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The skill declares a Wappalyzer integration and only requires the Membrane CLI and a Membrane account to create a Wappalyzer connection and run proxied requests. All requested capabilities (network access, Membrane account, CLI usage) align with the stated purpose.
Instruction Scope
SKILL.md limits runtime actions to installing/using the Membrane CLI, logging in, creating/listing connections, listing/running actions, and using Membrane's request proxy. It does not instruct reading unrelated files, requesting unrelated environment variables, or transmitting data to unexpected external endpoints beyond Membrane/Wappalyzer.
Install Mechanism
This is an instruction-only skill (no install spec). It tells the user/agent to install @membranehq/cli via npm (and suggests npx for one-off commands). While coherent for this integration, global npm installs or npx pull code from registries and should be obtained from the official package and verified; there is no automated installer baked into the skill itself.
Credentials
The skill declares no required environment variables or credentials. It relies on Membrane to manage authentication server-side, which is consistent with the SKILL.md guidance to avoid local API keys.
Persistence & Privilege
The skill is not always-enabled and does not request system-level config paths or persistent privileges. It does not instruct modifying other skills or system-wide settings. Autonomous invocation is permitted by platform default but not combined with other concerning privileges here.
Assessment
This skill appears to do what it says: use Membrane to interact with Wappalyzer. Before installing or running commands, verify you're using the official Membrane package (check the publisher and package name on npm and the project homepage), and prefer npx for one-off exploration if you don't want a global install. Be aware that installing global npm CLIs runs third-party code on your machine—only proceed if you trust @membranehq/cli. When you create a connection, confirm the connector is the official Wappalyzer connector and review what permissions the connection requests. The skill itself does not request unrelated credentials or system access.Like a lobster shell, security has layers — review code before you run it.
latestvk97fv9kfk27vcehsxm7wepnmvd8492n3
License
MIT-0
Free to use, modify, and redistribute. No attribution required.