Printavo
v1.0.2Printavo integration. Manage Organizations, Leads, Projects, Users, Goals, Filters. Use when the user wants to interact with Printavo 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
Name/description (Printavo integration) match the instructions: the SKILL.md tells the agent to use the Membrane CLI to create a connection, list/run actions, and proxy requests to the Printavo API. No unrelated services, env vars, or surprising binaries are requested.
Instruction Scope
Instructions are limited to installing/using the Membrane CLI (login, connect, action list/run, request proxy). They do not direct reading local files or unrelated env vars. Important to note: using 'membrane request' will send request data to Membrane's service (i.e., Membrane will see proxied API requests and responses).
Install Mechanism
There is no automated install spec in the registry; the SKILL.md recommends installing @membranehq/cli via 'npm install -g'. This is a normal, expected mechanism but requires trusting the npm package source and performing a global install on the host environment.
Credentials
The skill declares no required env vars or secrets and explicitly instructs not to ask for Printavo API keys (Membrane handles auth). The only credential implication is that Printavo access will be mediated by Membrane's service—this is proportionate to the stated purpose but requires trusting Membrane with the data and credentials.
Persistence & Privilege
Skill is user-invocable, not always-enabled, and contains no instructions to change other skills or system-wide configs. It does not request persistent elevated privileges.
Assessment
This is an instruction-only skill that tells the agent to install and use the Membrane CLI to connect to Printavo and proxy API requests. Before installing or using it: (1) Confirm you trust Membrane (getmembrane.com/@membranehq) because proxied requests and credentials will go through their service; (2) install the official @membranehq/cli package from npm (check publisher and package page) rather than a third-party copy; (3) be aware that running the CLI will open browser auth flows or print headless URLs/codes you must complete; and (4) only allow autonomous runs if you are comfortable the agent can execute membrane commands that access your Printavo data. If you need tighter control, avoid global installs and review the CLI invocation outputs before running actions that modify production data.Like a lobster shell, security has layers — review code before you run it.
latestvk97anfmfdmfjrhacyz7zvdb2r9842naw
License
MIT-0
Free to use, modify, and redistribute. No attribution required.