Asknicely
v1.0.2AskNicely integration. Manage data, records, and automate workflows. Use when the user wants to interact with AskNicely data.
⭐ 0· 54·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.md describes AskNicely operations and instructs use of the Membrane CLI to connect, list actions, run actions, and proxy API requests. Required capabilities (network access, Membrane account) match the described integration.
Instruction Scope
Instructions are narrowly scoped to installing and using the Membrane CLI, creating connections, listing/running actions, and proxying requests to AskNicely. There are no instructions to read unrelated local files, environment variables, or to exfiltrate data outside the Membrane flow.
Install Mechanism
The skill is instruction-only (no install spec) but tells users to run `npm install -g @membranehq/cli`. Installing a global npm package is a normal way to get the CLI but does pull code from the npm registry—users should verify the package identity and trustworthiness before installing.
Credentials
The skill declares no required environment variables or credentials and explicitly advises creating a connection via Membrane rather than sharing API keys. The credential model (browser login to Membrane, server-side auth management) is proportional to the integration described.
Persistence & Privilege
The skill does not request always:true or other elevated platform privileges. Runtime behavior relies on the Membrane CLI and the user's Membrane account; the skill itself is instruction-only and does not modify other skills or system-wide agent settings.
Assessment
This skill is internally consistent: it tells the agent to use the Membrane CLI to manage AskNicely data and does not request API keys or unrelated system access. Before installing/using it: 1) verify the npm package name and publisher (@membranehq/cli) and that you trust Membrane as a service; 2) be aware the CLI will run locally (global npm install) and may store local tokens/credentials—review its docs if you need to control where credentials are stored; 3) pay attention to potentially destructive actions exposed in the action list (e.g., bulk-delete-contacts-gdpr, delete-contact-gdpr) and avoid running them without explicit user authorization; and 4) if you need higher assurance, inspect the @membranehq/cli source/release pages or run it in an isolated environment before granting it access to production data.Like a lobster shell, security has layers — review code before you run it.
latestvk97ats2et14wzj16j67qsvnrns8437p3
License
MIT-0
Free to use, modify, and redistribute. No attribution required.