OpenClaw Debugging Assistant

Debugging assistant. Analyzes error logs, suggests breakpoints, traces execution flow, and helps identify root causes of issues.

This skill looks like what it says (a debugging helper) but there are red flags you should check before running it on important data or a production host: - Inconsistency: SKILL.md mentions helper modules (error_analyzer.py, tracer.py) that are not included in the package. Ask the author or check a full source tree before trusting behavior. - Inspect scripts/main.py fully: search for network/socket/HTTP libraries (requests, urllib, socket), subprocess/os.system calls, or code that reads unexpected paths (~/, /etc/, ~/.ssh, cloud SDK configs). If you see such calls, treat them as high risk. - The script attempts to import a 'c-support' library from a sibling directory outside the package; ensure there is no malicious code in that path on your system, or run the skill in a sandbox/container without that directory present. - Run the script in an isolated environment (container, VM) first and avoid passing it sensitive files. If you must run on real code, audit the source or run static grep for risky APIs (requests, socket, subprocess, open with absolute paths) before use. If you want, provide the full contents of scripts/main.py (untruncated) and I can do a deeper, line-by-line check for network I/O, subprocess execution, or data-exfiltration behaviors.

Type: OpenClaw Skill Name: oc-debugging Version: 1.1.0 The skill bundle provides a debugging assistant that performs static analysis on Python and C/C++ source files and error logs. The core logic in `scripts/main.py` uses the `ast` module and regular expressions to identify function definitions, memory allocations, and error patterns to provide debugging suggestions. There is no evidence of data exfiltration, unauthorized command execution, or malicious prompt injection; the tool operates locally on files provided via command-line arguments and does not make network requests.