Coveralls
v1.0.0Coveralls integration. Manage data, records, and automate workflows. Use when the user wants to interact with Coveralls data.
⭐ 0· 50·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
The name/description (Coveralls integration) match the instructions (using Membrane to connect to Coveralls). All requested actions (connect, list actions, run actions, proxy requests) are relevant to interacting with Coveralls.
Instruction Scope
SKILL.md only instructs installing and using the @membranehq/cli and browser-based auth flows. It does not ask the agent to read unrelated files, access unrelated environment variables, or send data to unexpected endpoints.
Install Mechanism
This is an instruction-only skill that recommends installing @membranehq/cli via npm (npm install -g). That's a common approach but carries the usual risk of running third-party code at install-time — the install is from the npm registry (not an arbitrary URL), which is expected but merits verifying the package and publisher.
Credentials
No environment variables, credentials, or config paths are requested by the skill. It requires a Membrane account (server-side auth) which explains why no API keys are requested locally — this is proportionate to the described workflow.
Persistence & Privilege
The skill does not request always:true, does not modify other skills, and does not require persistent system-level privileges. Normal autonomous invocation is allowed (platform default) and is not in itself a concern here.
Assessment
This skill is coherent: it tells you to install and use the Membrane CLI to connect to Coveralls and does not ask for unrelated secrets. Before installing, verify you trust the @membranehq/cli npm package and publisher (review the package page and repository), and review the connector's OAuth scopes when you create the connection. Installing global npm packages runs third‑party code with your user privileges, so consider installing in a controlled environment (container or VM) if you are unsure. Also confirm the Membrane tenant/service is acceptable for your data/privacy requirements.Like a lobster shell, security has layers — review code before you run it.
latestvk97fcejctfzkwyr4n2f0pwr1c1849b2j
License
MIT-0
Free to use, modify, and redistribute. No attribution required.