BugPack Fix Bug
v1.0.2Fix a bug from BugPack by reading its context, locating code, applying fixes, and updating status. Use when: user asks to fix, repair, or resolve a bug. NOT...
⭐ 0· 134·1 current·1 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
medium confidencePurpose & Capability
Name/description align with the instructions: it interacts with a BugPack API on localhost to get bug context, find related files, edit code, and mark status as fixed. No unrelated credentials, binaries, or installs are requested.
Instruction Scope
The SKILL.md explicitly instructs GET/PATCH to http://localhost:3456 and to edit source files referenced by the bug. Editing the codebase is consistent with fixing a bug, but the instructions are open-ended: they do not constrain which files may be modified, do not require running tests, committing, creating a PR, or validating the fix, and grant broad discretion to read/modify the local codebase.
Install Mechanism
Instruction-only skill with no install spec and no code files — nothing is written to disk by an installer and no third-party downloads are required.
Credentials
No environment variables, credentials, or config paths are requested. Access to a local HTTP service (localhost:3456) is required by the skill and is proportionate to its purpose.
Persistence & Privilege
always is false and the skill is user-invocable; it does not request persistent or elevated platform privileges.
Assessment
This skill coherently describes fixing a bug via a local BugPack API, but it leaves important operational and safety details unspecified. Before installing or using it: ensure the BugPack service at localhost:3456 is the intended target and authenticated as appropriate; confirm the agent has explicit, limited filesystem permissions and a working directory scoped to the project repo (to avoid accidental edits elsewhere); require that fixes be validated (run tests, run linters) and committed/pushed through your normal code-review process (or explicitly disable automatic commits); and consider backing up the repository or using a branch/PR workflow. If you need stricter controls, ask for SKILL.md to specify allowed file paths, test/commit steps, and required review/approval gates.Like a lobster shell, security has layers — review code before you run it.
latestvk9780fmwz1xfnn1b5x9b936gjd834mvt
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🔧 Clawdis