Getswift
v1.0.2Getswift integration. Manage Organizations, Projects, Users, Goals, Filters. Use when the user wants to interact with Getswift data.
⭐ 0· 83·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 describes using Membrane to connect to Getswift, list actions, run actions and proxy requests. There are no unrelated credential requests or unrelated binaries required.
Instruction Scope
Instructions stay within the integration scope: they tell the agent to install/use the Membrane CLI, run login/connect/action/request commands, and do not instruct reading local files, unrelated env vars, or exfiltrating data. The proxy feature allows arbitrary Getswift API calls via Membrane, which is expected for an integration skill.
Install Mechanism
This is instruction-only (no install spec). SKILL.md instructs installing @membranehq/cli via npm (a normal, low-risk registry install). Because the skill lacks an automated install spec, users must run the npm command themselves; this is expected but worth noting.
Credentials
The skill declares no required env vars or local credentials. It delegates auth to Membrane (server-side), which is proportionate to the stated design. The main trust decision is whether to allow Membrane to hold the Getswift credentials.
Persistence & Privilege
always is false and the skill is user-invocable; disable-model-invocation is false (normal). There is no request to modify other skills or system-wide configs. Note: because the agent may invoke the skill autonomously (platform default), it could run Membrane commands if given permission — this is expected behavior, not a red flag by itself.
Assessment
This skill is internally consistent: it uses the Membrane CLI to manage Getswift connections and auth rather than asking you for API keys. Before using it: (1) confirm you trust Membrane/getmembrane.com and the @membranehq/cli package (review their docs, privacy and security posture); (2) install the CLI yourself (npm install -g @membranehq/cli) in a trusted environment; (3) be aware that creating a connection grants Membrane server-side access to your Getswift account (use least-privilege accounts if possible); (4) monitor and revoke connections you no longer need. If you need stronger assurance, verify the referenced GitHub repository and Membrane's OAuth/connector details before proceeding.Like a lobster shell, security has layers — review code before you run it.
latestvk97dv0yw19k7g4g9p97qm6kyg5842k3h
License
MIT-0
Free to use, modify, and redistribute. No attribution required.