Getblock

v1.0.2

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

0· 84·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
VirusTotalVirusTotal
Pending
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The skill name/description (GetBlock integration) match the instructions (use Membrane CLI to connect to GetBlock APIs). It does not request unrelated cloud credentials or system paths. The SKILL.md references Membrane (the proxy) rather than asking for direct GetBlock API keys, which is coherent for a platform-based integration.
Instruction Scope
All instructions are limited to installing/using the Membrane CLI, creating connections, listing actions, running actions, and proxying requests to GetBlock. The skill does not instruct reading arbitrary local files or environment variables. Note: the SKILL.md tells users to install a global npm CLI and to perform browser-based authentication; that is expected but you should be aware it enables the CLI to make arbitrary proxied API calls on your behalf.
Install Mechanism
There is no formal install spec in the registry (instruction-only), but the docs instruct running `npm install -g @membranehq/cli` or using `npx`. Installing a global npm package is a normal but moderately-privileged action (downloads code from the npm registry). This is not inherently malicious, but users should verify the CLI package source before installing.
Credentials
The skill declares no required environment variables or credentials; SKILL.md explicitly says Membrane manages auth and you should not provide API keys. Requesting only a Membrane account and network/browser access is proportionate to the stated purpose.
Persistence & Privilege
The skill is instruction-only, does not request persistent 'always' inclusion, and does not modify other skills or system-wide config. It relies on the user installing/using a CLI and authorizing a connection via browser, which is normal for this integration pattern.
Assessment
This skill is coherent: it instructs use of the Membrane CLI to proxy requests to GetBlock rather than collecting raw API keys locally. Before installing: (1) verify you trust the @membranehq/cli package and its npm author (the SKILL.md asks you to install it globally); (2) understand that authorizing a connection opens a session where the Membrane service can make API calls on your behalf — avoid sending unrelated sensitive data through the proxy; (3) prefer using npx or a pinned package version if you want to avoid globally installing packages; and (4) confirm the Membrane homepage/repository links and package integrity if you require higher assurance. If you need, ask for the skill's provenance or a signed package URL before installing.

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

latestvk978pcnfnz70yxewks15x313yd8438n4

License

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

Comments