Runs a strict scientific debug procedure requiring reproduction scripts and proven causality before fixes.
Install
mkdir -p .claude/skills/debug-manusco && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/17213" && unzip -o skill.zip -d .claude/skills/debug-manusco && rm skill.zipInstalls to .claude/skills/debug-manusco
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Root-cause a bug via the Scientific Method. Reproduction script required, no fix without a proven cause.Key capabilities
- →Execute the Resonance debug procedure
- →Follow the Definition of Done for debugging
- →Adhere to the scientific method for root-causing bugs
- →Require a reproduction script before attempting a fix
- →Ensure a proven cause before implementing a fix
How it works
The skill routes to a core debugging procedure that mandates a scientific approach, requiring a reproduction script and a proven cause before any fix is attempted.
Inputs & outputs
When to use debug
- →Root-causing complex bugs
- →Scientific bug investigation
- →Validating issue fixes
About this skill
/debug
Run the Resonance debug procedure.
Read .agents/skills/engineering/debugger/SKILL.md in full and execute it exactly, following its Definition of Done. That skill is the procedure; this file only routes the /debug command to it.
When not to use it
- →When a quick fix is preferred over root-cause analysis
- →When a reproduction script cannot be provided
Limitations
- →A reproduction script is required
- →No fix is allowed without a proven cause
- →The process is strictly defined by the debugger skill
How it compares
This workflow enforces a rigorous, scientific method for debugging, prioritizing root-cause identification over immediate fixes, unlike trial-and-error debugging.
Compared to similar skills
debug side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| debug (this skill) | 0 | 1mo | No flags | Intermediate |
| godot | 1,044 | 5mo | Review | Intermediate |
| python-testing-patterns | 77 | 3mo | Review | Intermediate |
| error-handling-patterns | 35 | 3mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by manusco
View all by manusco →You might also like
godot
bfollington
This skill should be used when working on Godot Engine projects. It provides specialized knowledge of Godot's file formats (.gd, .tscn, .tres), architecture patterns (component-based, signal-driven, resource-based), common pitfalls, validation tools, code templates, and CLI workflows. The `godot` command is available for running the game, validating scripts, importing resources, and exporting builds. Use this skill for tasks involving Godot game development, debugging scene/resource files, implementing game systems, or creating new Godot components.
python-testing-patterns
wshobson
Implement comprehensive testing strategies with pytest, fixtures, mocking, and test-driven development. Use when writing Python tests, setting up test suites, or implementing testing best practices.
error-handling-patterns
wshobson
Master error handling patterns across languages including exceptions, Result types, error propagation, and graceful degradation to build resilient applications. Use when implementing error handling, designing APIs, or improving application reliability.
chrome-devtools
mrgoonie
Browser automation, debugging, and performance analysis using Puppeteer CLI scripts. Use for automating browsers, taking screenshots, analyzing performance, monitoring network traffic, web scraping, form automation, and JavaScript debugging.
unreal-engine-cpp-pro
sickn33
Expert guide for Unreal Engine 5.x C++ development, covering UObject hygiene, performance patterns, and best practices.
python-performance-optimization
wshobson
Profile and optimize Python code using cProfile, memory profilers, and performance best practices. Use when debugging slow Python code, optimizing bottlenecks, or improving application performance.