Hokodo

v1.0.2

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

0· 95·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 name/description (Hokodo integration) aligns with the instructions: all runtime steps talk to Hokodo via Membrane. Required capabilities (network, Membrane account, Membrane CLI) are appropriate for this purpose.
Instruction Scope
SKILL.md confines the agent to using the Membrane CLI and Membrane proxy to interact with Hokodo APIs. It does not instruct reading unrelated local files, harvesting environment variables, or posting data to third-party endpoints beyond the Membrane/Hokodo flow.
Install Mechanism
There is no install spec in the registry (instruction-only), but SKILL.md recommends installing @membranehq/cli globally via npm. Installing a global npm CLI is a reasonable, moderate-risk action for this integration—verify the package and publisher before installing; consider using npx to avoid global installs.
Credentials
The skill declares no required env vars, credentials, or config paths. The guidance explicitly tells agents not to ask users for API keys and to let Membrane manage auth, which is proportionate for a connector-based integration.
Persistence & Privilege
The skill is not always-on and does not request persistent system privileges or modify other skills. As an instruction-only skill, it does not install code itself or alter agent configuration.
Assessment
This skill appears to do what it says: use the Membrane CLI to connect to Hokodo. Before proceeding: verify the @membranehq/cli npm package and publisher (or use npx/@membranehq/cli@latest instead of a global install), confirm the Membrane homepage/repository you trust, and avoid sharing Hokodo API keys directly (use the Membrane connection flow). If you need higher assurance, inspect the Membrane CLI source on GitHub and confirm the connector IDs and endpoints it will call.

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

latestvk970n1x19qabtm46grg3wj3gn18438xc

License

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

Comments