debug Skill
Structured debugging session — reproduce, isolate, diagnose, and fix. Trigger with an error message or stack trace, "this works in staging but not prod", "something broke after the deploy", or when behavior diverges from expected and the cause isn't obvious. Published by anthropics in knowledge-work-plugins.
Decision snapshot
Is this a fit?
Testing, Deployment, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
Permission behavior not yet detected.
Copy skill directory
22 days ago · Apache-2.0 license
No specific cautions were detected. Review the source and requested permissions before installing.
What is debug Skill?
Structured debugging session — reproduce, isolate, diagnose, and fix. Trigger with an error message or stack trace, "this works in staging but not prod", "something broke after the deploy", or when behavior diverges from expected and the cause isn't obvious. Published by anthropics in knowledge-work-plugins. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Testing
- Deployment
- Testing use cases
- Deployment use cases
Declared skill metadata
- Source file: engineering/skills/debug/SKILL.md
These fields retain source and confidence evidence from the indexed SKILL.md.
Compatibility and setup
- Install or run with Copy skill directory
When to use debug Skill
- Use it for testing.
- Use it for deployment.
Built with
Editorial notes
Source
- Creator: anthropics
- Repository: anthropics/knowledge-work-plugins
- Skill file: engineering/skills/debug/SKILL.md
What it does
Structured debugging session — reproduce, isolate, diagnose, and fix. Trigger with an error message or stack trace, "this works in staging but not prod", "something broke after the deploy", or when behavior diverges from expected and the cause isn't obvious.
Skill instructions
/debug If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md. Run a structured debugging session to find and fix issues systematically. Usage /debug $ARGUMENTS How It Works ┌─────────────────────────────────────────────────────────────────┐ │ DEBUG │ ├─────────────────────────────────────────────────────────────────┤ │ Step 1: REPRODUCE │ │ ✓ Understand the expected vs. actual behavior │ │ ✓ Identify exact reproduction steps │ │ ✓ Determine scope (when did it start? who is affected?) │ │ │ │ Step 2: ISOLATE │ │ ✓ Narrow down the component, service, or code path │ │ ✓ Check recent changes (deploys, config changes, dependencies) │ │ ✓ Review logs and error messages │ │ │ │ Step 3: DIAGNOSE │ │ ✓ Form hypotheses and test them │ │ ✓ Trace the code path │ │ ✓ Identify root cause (not just symptoms) │ │ │ │ Step 4: FIX │ │ ✓ Propose a fix with explanation │ │ ✓ Consider side effects and edge cases │ │ ✓ Suggest tests to prevent regression │ └───────
Verified compatibility and discovery
Frequently asked questions
What is debug?
debug is a open-source AI agent skill with Copy skill directory. Structured debugging session — reproduce, isolate, diagnose, and fix. Trigger with an error message or stack trace, "this works in staging but not prod", "something broke after the deploy", or when behavior.
Who is debug best for?
debug is best for reusing agent instructions, scripts, and references, testing workflows, deployment workflows.
How do I install debug?
Install or run debug using Copy skill directory. Check debug for the latest setup command.
Is debug actively maintained?
debug may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
Maintain this resource?
Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.
