1Kosmos Blockid
v1.0.01Kosmos BlockID integration. Manage data, records, and automate workflows. Use when the user wants to interact with 1Kosmos BlockID data.
⭐ 0· 30·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 name and description match the instructions: it uses Membrane to interact with 1Kosmos BlockID. Asking users to install the Membrane CLI and create a connection is appropriate for this integration.
Instruction Scope
SKILL.md contains explicit CLI commands (npm install -g @membranehq/cli, membrane login, membrane connect, action run, proxy requests). These commands are within scope for a connector skill. Note: the instructions rely on interactive browser-based auth (or headless URL/code flow) and on Membrane proxying requests to the 1Kosmos API, which means network calls and auth flows are central to operation.
Install Mechanism
There is no formal install spec bundled with the skill (it's instruction-only), but the runtime instructions ask the user to install a global npm package. Installing a global npm CLI is a normal step for this type of integration but does have the usual trust implications (verify package owner and source).
Credentials
The skill declares no required environment variables, no config paths, and no primary credential. All auth/credentials are delegated to Membrane via its connection flow, which matches the stated advice in the documentation.
Persistence & Privilege
The skill is not forced-always, and it does not request system-wide config changes or persistent privileges in the SKILL.md. Autonomous model invocation is allowed (platform default) but not combined with other red flags.
Assessment
This skill is coherent, but take these practical precautions before installing or using it:
- Verify the Membrane CLI package and its publisher (@membranehq) on npm and the referenced GitHub repo/homepage (getmembrane.com / github.com/membranedev) to ensure authenticity.
- Installing a global npm package modifies your environment—consider installing in a scoped environment (nvm, container, or VM) if you have concerns.
- The Membrane service will handle authentication and proxy requests to 1Kosmos; by creating a connection you grant Membrane access to your 1Kosmos resources—review Membrane's privacy and security policies and ensure you trust that service.
- During first-time setup the flow opens a browser or prints a URL/code for headless completion—be cautious about pasting codes from unknown prompts.
- Inspect command output (connection IDs, action schemas) before running actions to avoid accidentally executing unwanted operations; do not provide unrelated secrets or credentials to this skill.
If you need higher assurance, ask the skill author for a formal install spec or a signed/verified package link and check the upstream repository for the published CLI package and release notes.Like a lobster shell, security has layers — review code before you run it.
latestvk976t01jmpfayrpy30rkdwhrb1846kay
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
