Certify
v1.0.2Certify integration. Manage data, records, and automate workflows. Use when the user wants to interact with Certify data.
⭐ 0· 97·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 describes a Certify integration and only instructs use of the Membrane CLI to create connections, list actions, run actions, and proxy API requests to Certify — all consistent with the stated purpose.
Instruction Scope
SKILL.md only directs installing/using the Membrane CLI, creating a connector connection, discovering and running actions, and sending proxied API requests through Membrane. It does not instruct reading unrelated files, accessing unrelated env vars, or sending data to third-party endpoints outside Membrane/Certify.
Install Mechanism
There is no automated install spec in the registry (instruction-only). The doc suggests installing @membranehq/cli via npm -g or using npx. This is expected for a CLI-based integration, but installing global npm packages carries the usual trust considerations (review package origin/maintainer).
Credentials
The skill does not request environment variables, credentials, or config paths. It explicitly recommends using Membrane's connection flow rather than local API keys, which is proportionate to its purpose.
Persistence & Privilege
Skill is not always-enabled and uses default autonomous invocation settings. It does not request persistent system-wide changes or access to other skills' configuration.
Assessment
This skill is coherent: it expects you to install and use the Membrane CLI to connect to Certify and run proxied actions. Before installing/using it, verify you trust the @membranehq/cli package (review the npm package and its maintainer), ensure you are comfortable authenticating via the Membrane login flow, and be aware that once connected the CLI can send arbitrary API requests to Certify through your connection — only create connections for accounts you control and check connector permissions. If you prefer not to install a global npm package, use the npx commands the doc shows. If you want stronger limits, avoid granting the agent autonomous access or review/log the actions the agent runs through Membrane.Like a lobster shell, security has layers — review code before you run it.
latestvk978g7gyz6je3r5khmw3drkm8n843s0h
License
MIT-0
Free to use, modify, and redistribute. No attribution required.