Blockstack

v1.0.2

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

0· 67·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
Pending
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description match the instructions: the SKILL.md tells the agent to use the Membrane CLI to manage Blockstack connections, actions, and proxy requests. No unrelated credentials, binaries, or config paths are requested.
Instruction Scope
Instructions stay within the Blockstack integration scope (install Membrane CLI, login, create connections, list/run actions, proxy requests). The SKILL.md explicitly defers auth to Membrane (it will open a browser for auth or provide a headless flow). This delegates credential handling and request proxying to Membrane's service — a design choice that is coherent but requires trust in that third party.
Install Mechanism
The skill is instruction-only (no automatic install), but instructs the user to run `npm install -g @membranehq/cli` or use `npx`. Asking users to install an official npm CLI is proportionate; however, installing global npm packages has typical supply-chain/trust considerations (verify package identity/source).
Credentials
The skill does not request any environment variables, primary credentials, or config paths. It requires a Membrane account and network access, which are appropriate given the described proxy-based architecture.
Persistence & Privilege
always is false and the skill is user-invocable; it does not request persistent or elevated platform privileges nor does it modify other skills. As an instruction-only skill, it does not write code or persist artifacts itself.
Assessment
This skill only provides instructions for using the Membrane CLI to reach Blockstack — it does not itself run code or ask for local secrets. Before using it, verify you trust Membrane (https://getmembrane.com) because the CLI proxies requests and holds the connection credentials; review Membrane's privacy/security docs and the @membranehq/cli package source. Prefer using npx or a scoped install if you don't want a global npm package. If you need stricter isolation, create a limited/test Membrane account and confirm which data will be proxied/stored before connecting production Blockstack data.

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

latestvk97307y84rq6cap1382gnyejcx84340j

License

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

Comments