ClawHub

Code Debug

v0.1.0

Diagnose errors or crashes in local code, identify root causes, and provide the minimal fix with verification steps.

⭐ 0· 131·0 current·0 all-time
by@sf0799
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
Name and description match the SKILL.md: it is an instruction-only debugging helper for diagnosing and producing minimal fixes to local code. It requests no binaries, env vars, installs, or external services, which is proportional for the stated purpose.
ℹ
Instruction Scope
The instructions direct the agent to reproduce failures, inspect code, logs, and execution results, and produce minimal fixes and verification steps. That scope is appropriate for debugging, but implies the agent may read project files, logs, and run tests or code in the workspace — actions the user should be aware of because they can execute untrusted code or access sensitive files.
✓
Install Mechanism
No install spec or code files are present (instruction-only). This minimizes supply-chain risk because nothing is downloaded or written to disk by the skill itself.
✓
Credentials
The skill declares no environment variables, credentials, or config paths. There are no requests for unrelated secrets or credentials, which is appropriate for a local debugging assistant.
✓
Persistence & Privilege
The skill does not request always: true and has default invocation settings. It does not modify other skills or system-wide settings. Autonomous invocation is permitted by default (platform default) but is not combined with other high-risk factors here.
Assessment
This skill is coherent and instruction-only, but remember: for it to debug effectively it will need to read your workspace files, logs, and may run tests or code — which can execute untrusted code or touch sensitive data. Before using: (1) run it only on code you trust or inside an isolated sandbox/container, (2) back up or use version control so you can review and approve patches before applying, (3) avoid exposing secrets in the workspace while debugging, and (4) if you prefer manual review, disable autonomous invocation or require user confirmation before applying fixes.

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

latestvk973x0y4e8wv35f1wfpt9w1cv984afjh

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Comments