ClawHub

Connectwise Psa

v1.0.0

Connectwise PSA integration. Manage data, records, and automate workflows. Use when the user wants to interact with Connectwise PSA data.

⭐ 0· 51·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
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
The skill claims to integrate with Connectwise PSA and its SKILL.md consistently instructs the agent to use the Membrane CLI to list connections, run actions, and proxy API requests to Connectwise. Nothing requested (no extra env vars, no unrelated binaries) is inconsistent with that purpose.
ℹ
Instruction Scope
Instructions are scoped to installing and using the Membrane CLI, creating connections, listing/running actions, and proxying requests. Important note: proxying means data and API calls go through Membrane's service and the Membrane CLI will hold/refresh credentials — users should be aware that Connectwise data will transit Membrane.
ℹ
Install Mechanism
The skill is instruction-only (no install spec in registry) but tells users to install @membranehq/cli via 'npm install -g'. Installing a global npm package is a normal distribution method but carries standard supply-chain/privilege considerations (verify package identity and source before installing globally).
✓
Credentials
The skill declares no required env vars or credentials; instead it relies on interactive Membrane authentication. This is proportional, but means the Membrane account/CLI will store and use Connectwise credentials — evaluate Membrane's access and storage policies before granting access.
✓
Persistence & Privilege
always is false and the skill does not request elevated or persistent platform-wide privileges. It does rely on the Membrane CLI and account for runtime auth, which is expected for this integration.
Assessment
This skill appears coherent, but before installing: (1) verify the NPM package @membranehq/cli is legitimate (check the npm page and the GitHub repository), (2) understand that API requests and data will be proxied through Membrane — review their privacy/security and credential storage policies, (3) prefer least-privilege Connectwise credentials for the connection and consider testing in an isolated environment, and (4) avoid installing global packages on critical systems until you confirm the package/source is trusted.

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

latestvk977rjsecnzkzpqtepy25q0shn84eg4s

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Comments