Fogbugz
v1.0.2FogBugz integration. Manage Persons, Organizations, Leads, Deals, Projects, Pipelines and more. Use when the user wants to interact with FogBugz data.
⭐ 0· 102·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 SKILL.md consistently describes using Membrane to talk to FogBugz, which matches the skill name and description. Minor mismatch: registry metadata lists no required binaries, but the runtime instructions explicitly require installing the @membranehq/cli (npm) to run 'membrane' commands.
Instruction Scope
Instructions focus on installing the Membrane CLI, logging in, creating/listing connections, running actions, and proxying FogBugz API calls through Membrane. They do not instruct the agent to read unrelated local files or request unrelated credentials.
Install Mechanism
No formal install spec in registry (instruction-only), but SKILL.md recommends installing @membranehq/cli via 'npm install -g'. Using an npm package is expected for a CLI; this is moderate-risk only because npm packages execute arbitrary code at install time—verify the package source before installing.
Credentials
The skill declares no required environment variables and explicitly advises letting Membrane handle credentials instead of asking for API keys. This is proportionate for a connector that delegates auth to Membrane.
Persistence & Privilege
always is false and the skill is user-invocable. It does not request system-wide config changes or access to other skills' credentials. Autonomous invocation is allowed (platform default) but not a novel privilege of this skill.
Assessment
This skill appears coherent: it uses the Membrane CLI to interact with FogBugz and does not ask for unrelated credentials. Before installing, verify the @membranehq/cli npm package and the Membrane service (homepage/repo) are legitimate, and prefer installing in controlled environments (avoid running global installs on sensitive hosts). Be aware that Membrane proxy commands can issue arbitrary API requests on your behalf—use a least-privilege Membrane account and review what permissions the FogBugz connection will grant. Finally, note the registry metadata did not declare the required 'membrane' binary even though the SKILL.md requires it; you should ensure the runtime environment can run the Membrane CLI before relying on this skill.Like a lobster shell, security has layers — review code before you run it.
latestvk9782x400j361yje3gt6vy4gah843eeb
License
MIT-0
Free to use, modify, and redistribute. No attribution required.