OpenClaw Debugger
v1.0.0Debugging assistant. Analyzes error logs, suggests breakpoints, traces execution flow, and helps identify root causes of issues.
⭐ 0· 57·0 current·0 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 (debugging assistant) matches the provided code and SKILL.md: the code analyzes traceback text, suggests breakpoints by scanning source files, and performs basic AST-based tracing. No unrelated binaries, cloud APIs, or extra credentials are requested.
Instruction Scope
SKILL.md instructs the agent to run scripts/main.py with user-supplied error text or source files. The runtime instructions and code operate on local files and input provided by the user (error logs, source files), which is expected for a debugger. However, the README references additional modules (error_analyzer.py, tracer.py) that are not present in the package, and the included scripts/main.py appears truncated in the provided listing — this incomplete packaging should be resolved before use.
Install Mechanism
No install spec is present (instruction-only + a code file). That is low-risk — nothing is downloaded or written to disk by an installer step beyond the files already bundled.
Credentials
The skill declares no required environment variables, credentials, or config paths. The code shown does not access environment secrets or external credential stores. It does read user-supplied files (error logs, source files), which is expected for this functionality.
Persistence & Privilege
The skill is not marked always:true, does not request persistent presence, and doesn't attempt to modify other skill configurations. It only runs as an invoked script and therefore has a limited privilege profile.
Assessment
This skill appears to be a straightforward local debugging helper: it reads error text and source files and prints suggestions. Before installing/running: 1) confirm you received the full source (SKILL.md mentions error_analyzer.py and tracer.py, but only scripts/main.py is bundled and the main.py listing appears truncated) — ask the publisher for the complete package. 2) Inspect the full main.py and any referenced modules for network calls or hidden behavior (current file shows no networking, but missing files could). 3) Run the code in a sandbox or isolated environment if you plan to feed it real logs or source files, especially if those files contain secrets. 4) If you will run it regularly, request a signed/verified release or source repository so you can track updates. If you want, I can point out the exact places in main.py to double-check or help compare the packaged files to the SKILL.md expectations.Like a lobster shell, security has layers — review code before you run it.
latestvk975gz2r1kj0rkg22t3nqe2201841rm7
License
MIT-0
Free to use, modify, and redistribute. No attribution required.