Certifier
v1.0.2Certifier integration. Manage data, records, and automate workflows. Use when the user wants to interact with Certifier data.
⭐ 0· 123·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 name/description say 'Certifier' integration and the SKILL.md instructs use of the Membrane CLI to connect to Certifier, list/run actions, and proxy API requests. The required capabilities (network and a Membrane account) match the stated purpose. No unrelated credentials, binaries, or config paths are requested.
Instruction Scope
Instructions are narrowly scoped to installing and using @membranehq/cli (login, connect, action list/run, request proxy). They do not direct reading arbitrary local files or unrelated environment variables. Note: the proxy functionality can be used to call arbitrary Certifier endpoints (expected for an integration) and the CLI performs auth flows that will store tokens locally.
Install Mechanism
This is an instruction-only skill (no install spec). The docs advise installing the Membrane CLI via npm (a standard public registry). There are no downloads from untrusted URLs or archive extraction steps in the package metadata.
Credentials
The skill declares no required env vars or credentials; authentication is delegated to the Membrane CLI which runs browser-based or headless login flows. That is proportionate to the stated purpose. Be aware the CLI will store tokens locally as part of normal operation.
Persistence & Privilege
The skill does not request always:true and does not modify other skills or system agent settings. Model invocation is allowed (platform default), meaning the agent could run the Membrane CLI if invoked — this is expected but worth noting in user guidance.
Assessment
This skill is coherent: it relies on the official Membrane CLI to access Certifier and asks for no unrelated secrets. Before installing, verify you trust the Membrane npm package (@membranehq/cli) and that you want to grant the CLI (and any agent using this skill) the ability to act on your Certifier account (it can list, create, issue, send, or delete credentials via Membrane). Note the registry lists the skill source as unknown even though the SKILL.md references Membrane repositories and getmembrane.com — if provenance matters, confirm the publisher. If you plan to allow autonomous agent actions, restrict the Membrane account to least privilege and consider testing in a non-production tenant first.Like a lobster shell, security has layers — review code before you run it.
latestvk9751d4shfgqc4gz23brgc0sds842kvm
License
MIT-0
Free to use, modify, and redistribute. No attribution required.