Servicem8
v1.0.2ServiceM8 integration. Manage Organizations, Users, Goals, Filters. Use when the user wants to interact with ServiceM8 data.
⭐ 0· 151·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
OpenClaw
Benign
high confidencePurpose & Capability
The name/description state a ServiceM8 integration and the SKILL.md exclusively documents using the Membrane CLI to connect to ServiceM8, list actions, run actions, and proxy API requests. No unrelated credentials, binaries, or config paths are requested.
Instruction Scope
Runtime instructions stay within the stated purpose: install and use @membranehq/cli, perform browser-based login, create connections, list/run actions, and proxy ServiceM8 API calls via Membrane. The instructions do not tell the agent to read arbitrary local files, harvest environment variables, or exfiltrate data to unexpected endpoints. Note: proxy capability allows arbitrary requests to the ServiceM8 API through Membrane (expected for an integration).
Install Mechanism
This is an instruction-only skill (no install spec recorded) but SKILL.md instructs installing a global npm package (`npm install -g @membranehq/cli`). Installing an npm package globally is a common but non-trivial action — it modifies the host environment and pulls code from the public registry. This is expected for a CLI-driven integration but carries the usual supply-chain considerations.
Credentials
The skill declares no required env vars or credentials. SKILL.md explicitly directs using Membrane-managed connections and not asking users for ServiceM8 API keys. Requiring a Membrane account and browser-based auth is proportional to the integration.
Persistence & Privilege
The skill is not force-enabled (always: false) and does not request system-wide config changes or credentials of other skills. Autonomous invocation is allowed (platform default); combined with the connector/proxy functionality this lets the agent call the user's connected ServiceM8 account via Membrane — this is expected for an integration.
Assessment
This skill appears coherent: it uses the Membrane CLI to manage ServiceM8 connections and intentionally avoids asking for raw API keys. Before installing, verify you trust Membrane/@membranehq and the npm package being installed (global npm installs change your environment). When authenticating, confirm you authorize only the intended ServiceM8 account/connector and review actions the agent runs (proxy calls can issue arbitrary API requests to your connected account). If you operate in a shared or sensitive environment, prefer manual review of commands rather than allowing fully autonomous execution.Like a lobster shell, security has layers — review code before you run it.
latestvk97adna8nysxd0bh6ekdjqcsy984203d
License
MIT-0
Free to use, modify, and redistribute. No attribution required.