Apicurio Registry
v1.0.0Apicurio Registry integration. Manage data, records, and automate workflows. Use when the user wants to interact with Apicurio Registry data.
⭐ 0· 14·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 name/description (Apicurio Registry integration) matches the runtime instructions: all actions are framed around using the Membrane CLI to connect to and proxy requests to Apicurio Registry. Required network access and a Membrane account are consistent with this purpose.
Instruction Scope
SKILL.md confines the agent to installing and using the Membrane CLI, creating connections, listing/running actions, and proxying API calls. It does not instruct reading arbitrary local files, harvesting unrelated env vars, or sending data to unknown endpoints beyond what Membrane proxies to Apicurio Registry.
Install Mechanism
The guide recommends installing @membranehq/cli via npm (-g). That is a common distribution method but does perform a global npm install (writes a binary to the system PATH). This is expected for a CLI-focused skill but the user should verify the npm package and publisher before installing.
Credentials
The skill declares no required env vars or local credentials; authentication is delegated to Membrane (browser login / server-side token management). No unrelated credentials or config paths are requested.
Persistence & Privilege
always:false (not force-included). disable-model-invocation is default false (normal). The skill does not request system-wide config changes or access to other skills' credentials.
Assessment
This skill appears self-consistent, but before installing: 1) Verify the npm package (@membranehq/cli) and its publisher (npm page, GitHub repo) to ensure you're installing the official CLI. Global npm installs add a binary to your system PATH and may require elevated privileges. 2) Understand that Membrane will broker authentication and proxy API requests — any data sent through the proxy is visible to Membrane's service, so avoid sending secrets unless you trust their privacy/security practices. 3) If you need stronger assurance, review the Membrane project's repo and privacy/security docs and consider testing the CLI in an isolated environment first.Like a lobster shell, security has layers — review code before you run it.
latestvk974knfmn1h5118fdv2kpgg2th84c14q
License
MIT-0
Free to use, modify, and redistribute. No attribution required.