Percy

v1.0.0

Percy integration. Manage data, records, and automate workflows. Use when the user wants to interact with Percy data.

0· 56·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
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The SKILL.md describes interacting with Percy via the Membrane CLI (listing actions, creating connections, proxying Percy API requests). That maps cleanly to the skill name/description. The compatibility section correctly calls out the need for network access and a Membrane account.
Instruction Scope
Runtime instructions are limited to installing/using the Membrane CLI, authenticating via browser, creating connections, listing and running actions, and proxying API requests. The instructions do not request unrelated files, environment variables, or system-wide data beyond what is needed for CLI usage and authentication.
Install Mechanism
There is no formal install spec in the registry metadata, but the SKILL.md instructs users to run `npm install -g @membranehq/cli` (or use npx). Installing a global npm package executes code from the npm registry (moderate risk); this is expected for a CLI-based integration but you should verify the package and publisher before installing.
Credentials
The skill declares no required env vars or credentials and explicitly recommends using Membrane connections rather than asking for user API keys. This is proportionate. Note that Membrane (a third-party service) will handle auth and will see proxied requests to Percy, which is expected for this integration.
Persistence & Privilege
The skill does not request always-on presence, does not modify other skills or global agent settings, and relies on standard CLI operations. Autonomous invocation is allowed (the platform default) and is not combined with other concerning privileges.
Assessment
This skill is coherent: it uses the Membrane CLI to talk to Percy and asks you to authenticate in-browser. Before installing, verify the @membranehq/cli package (author, version, and npm/GitHub repo) and the getmembrane.com / repository links. If you prefer to avoid a global install, use npx where supported. Remember that Membrane will act as a proxy and will see requests to Percy (it manages credentials server-side), so only use this skill if you trust the Membrane service and the CLI package maintainer.

Like a lobster shell, security has layers — review code before you run it.

latestvk97emd8qrn4wy9s2wzhm9105c1849kxt

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments