Bitquery
v1.0.2Bitquery integration. Manage data, records, and automate workflows. Use when the user wants to interact with Bitquery data.
⭐ 0· 92·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 is described as a Bitquery integration and all runtime instructions consistently show how to interact with Bitquery via the Membrane CLI (search connectors, create connections, run actions, or proxy requests). There are no unrelated required binaries, env vars, or config paths.
Instruction Scope
SKILL.md only instructs using the Membrane CLI to discover connectors/actions and proxy requests to Bitquery; it does not ask the agent to read arbitrary files or environment variables, nor to exfiltrate data to unrelated endpoints. It requires a Membrane account and network access, which is appropriate for this workflow.
Install Mechanism
The instructions tell the user to run 'npm install -g @membranehq/cli' (global npm install). This is a public npm package install (moderate risk compared to no install); it's expected for a CLI-based skill but users should verify the package's origin and contents before installing globally. There is no registry-level install spec in the skill bundle itself.
Credentials
The skill declares no required env vars or credentials. Authentication is delegated to Membrane (browser login and connection creation). That is proportionate: Membrane handles Bitquery credentials rather than asking the user to paste API keys into the skill.
Persistence & Privilege
The skill is instruction-only, not always-enabled, and does not request persistent platform privileges or attempt to modify other skills or system-wide settings. Autonomous invocation is allowed by platform default, which is normal and not a specific concern here.
Assessment
This skill looks coherent: it teaches the agent to use the Membrane CLI to access Bitquery and does not ask for unrelated secrets. Before installing, verify the @membranehq/cli package (review npmjs.com entry and the GitHub repository), and consider installing in a non-global or sandboxed environment if you prefer to avoid global npm packages. Be aware you'll need a Membrane account and to complete a browser-based login flow; Membrane will hold Bitquery credentials on your behalf. If you want stronger assurance, inspect the Membrane CLI source code and its published package before running 'npm install -g'.Like a lobster shell, security has layers — review code before you run it.
latestvk97fw1qe9m1s4x56s30bm619a9842f60
License
MIT-0
Free to use, modify, and redistribute. No attribution required.