Bugherd

v1.0.2

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

0· 93·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
high confidence
Purpose & Capability
The name/description claim a BugHerd integration and the SKILL.md consistently instructs the agent to use Membrane to connect to BugHerd. Required capabilities (network access, a Membrane account, and the Membrane CLI) are coherent with that purpose.
Instruction Scope
Runtime instructions stay within scope: they describe installing and using the Membrane CLI, logging in, creating connections, listing/running actions, and proxying to the BugHerd API. The doc explicitly advises against requesting raw API keys from users and does not instruct reading unrelated files or secrets.
Install Mechanism
The skill is instruction-only and has no platform install spec, but it tells users to run 'npm install -g @membranehq/cli'. Installing a global npm CLI is an expected, moderate-risk step for this integration; users should review the @membranehq/cli package before installing.
Credentials
No environment variables or credentials are declared or requested by the skill; the instructions rely on Membrane-managed authentication, which is proportionate for a connector-based integration.
Persistence & Privilege
The skill does not request always:true, does not modify other skills or system-wide settings, and is user-invocable only. It does not ask for elevated or persistent platform privileges.
Assessment
This skill is a thin integration guide that relies on the Membrane CLI to talk to BugHerd. Before installing/running anything: (1) verify the @membranehq/cli package on npm and the Membrane site (getmembrane.com) so you understand what the CLI will install; (2) be aware that 'npm install -g' writes executables to your system (may require elevated privileges); (3) the skill intentionally avoids asking for BugHerd API keys — it expects you to authenticate via Membrane in your browser; and (4) if you use an automated or headless environment, follow the documented headless-login flow rather than pasting secrets. If you don’t trust Membrane or the CLI package, don’t install it.

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

latestvk97bf4v46py2v0rq798hxz6was843dpy

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments