ClawHub

Asure Software

v1.0.2

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

⭐ 0· 51·0 current·0 all-time
byMembrane Dev@membranedev
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Pending
View report →
OpenClawOpenClaw
Benign
medium confidence
ℹ
Purpose & Capability
The SKILL.md consistently describes an Asure Software integration that runs through the Membrane CLI. However the registry metadata lists no required binaries or credentials while the runtime instructions clearly require network access, a Membrane account, and the Membrane CLI — a small documentation/inventory mismatch.
✓
Instruction Scope
Instructions stay within the stated purpose: install and use the Membrane CLI, create a connector, list/run actions, or proxy API calls to Asure via Membrane. The skill explicitly advises not to collect API keys locally and does not instruct reading unrelated files or environment variables.
ℹ
Install Mechanism
This is an instruction-only skill (no install spec). It tells users to run `npm install -g @membranehq/cli`. Global npm installs execute package install scripts and fetch code from the public npm registry — a normal but higher-trust install step; the package namespace appears consistent with the service but you should verify the upstream package and repository before running.
✓
Credentials
No environment variables or credentials are declared or requested by the skill. Authentication is delegated to Membrane (browser login or headless flow). This is proportionate to the integration's purpose.
✓
Persistence & Privilege
Skill is not always-enabled and does not request any elevated platform privileges. It does not modify other skills or system-wide settings in the instructions.
Assessment
This skill appears to do what it says: it uses Membrane as a proxy/connector to access Asure Software. Before using it: 1) confirm you trust the @membranehq/cli npm package and its upstream repository (global npm installs run code on install). 2) Understand that data and credentials are managed through Membrane’s service — Asure API calls will be proxied through Membrane, so review Membrane’s privacy/security and data residency policies. 3) Be aware the registry metadata omitted the Membrane CLI and account requirement — ensure the runtime environment can install/run the CLI and open a browser for login (or follow the headless flow). If any of these are unacceptable, do not install or run the CLI until you verify the provider and permissions.

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

latestvk97c47ncbmmfaynzt1nffvtkgx843cm4

License

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

Comments