Partnerstack
v1.0.2PartnerStack integration. Manage Organizations, Leads, Projects, Users, Goals, Filters. Use when the user wants to interact with PartnerStack data.
⭐ 0· 111·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 match the instructions: the SKILL.md instructs use of Membrane to interact with PartnerStack. It does not ask for unrelated cloud credentials or system access.
Instruction Scope
Instructions are limited to installing/using the Membrane CLI, authenticating via browser (or headless flow), listing/creating connections, running actions, or proxying requests to PartnerStack. No unrelated files, system paths, or other credentials are requested.
Install Mechanism
The skill is instruction-only (no install spec), but SKILL.md tells the user to run `npm install -g @membranehq/cli` or use npx. Installing a global npm package is a normal but higher-impact step than an instruction-only skill—verify the package source before installing and prefer npx if you want to avoid a global install.
Credentials
The skill declares no required environment variables or credentials and explicitly instructs not to ask users for PartnerStack API keys, relying on Membrane-managed connections instead—this is proportionate to the stated purpose.
Persistence & Privilege
always:false and no special persistence or modifications to other skills/configs are requested. The skill relies on the agent having network access and permission to call the Membrane CLI when invoked.
Assessment
This skill appears coherent and limited to using the Membrane CLI to access PartnerStack. Before installing or following its instructions: 1) Verify the @membranehq/cli package on npm/GitHub to ensure you're installing the legitimate package; prefer using npx for one-off commands if you want to avoid a global install. 2) Confirm you are comfortable granting Membrane (a third-party service) the ability to manage PartnerStack credentials and proxy API calls on your behalf. 3) Ensure the agent has network access only when you intend it, since the skill depends on networked CLI calls. No PartnerStack API keys are requested by the skill itself.Like a lobster shell, security has layers — review code before you run it.
latestvk97f9x57xsdw0cq8h9s7pqfmh5842z6k
License
MIT-0
Free to use, modify, and redistribute. No attribution required.