Hashnode

v1.0.2

Hashnode integration. Manage Users, Publications. Use when the user wants to interact with Hashnode data.

0· 125·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 claims to integrate with Hashnode and all runtime instructions and examples use the Membrane CLI to connect, list actions, run actions, or proxy requests to the Hashnode API — which is coherent with the stated purpose.
Instruction Scope
SKILL.md only instructs installing and using the Membrane CLI, creating connections, listing/running actions, and proxying requests. It does not direct the agent to read unrelated files, request unrelated environment variables, or send data to unexpected endpoints. It does require a Membrane account and network access, which is necessary for the described flow.
Install Mechanism
Install is via npm global package (npm install -g @membranehq/cli). This is a common and generally acceptable install path but carries the usual npm/global-install risks (privilege needed for global install, trust in the npm package/publisher). No arbitrary URL downloads or extracted archives are used.
Credentials
The skill declares no required environment variables or credentials. It does require a Membrane account (and the user will authenticate via browser) so there is no disproportionate request for unrelated secrets.
Persistence & Privilege
The skill is instruction-only, has always:false, and does not request persistent system privileges or modify other skills' configs. Autonomous invocation is allowed by default but not combined with other red flags here.
Assessment
This skill is coherent but depends on the Membrane service and its CLI: installing the CLI requires npm global install privileges and trusting the @membranehq npm package and Membrane account to proxy your Hashnode requests. Before installing, verify the npm package and its publisher (https://www.npmjs.com/package/@membranehq/cli and the GitHub repo), confirm you are comfortable routing requests through Membrane (they will see proxied request/response data), and ensure global npm installs are acceptable in your environment. If you prefer not to use a third-party proxy, you can call Hashnode's API directly but will need to manage API keys/authentication yourself.

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

latestvk972ddbk1gm8vey3nyw33s5a85842vb1

License

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

Comments