← all tools

cc-skill:debug-assistant

Claude Code skill · anthropic · active

0
last 30 days
0 calls
0 of 30 days active
explain like I am new to this
what it does

This skill walks you through a structured debugging process to find and fix what's broken. It asks you the right questions in the right order: what's happening, what should happen, can you reproduce it, and what changed recently. Then it helps you isolate the root cause instead of flailing at random fixes.

who it is for

Engineers and technical people who hit an error, stack trace, or unexpected behavior and need a clear path to the fix.

when it fires

When you mention debugging, error messages, stack traces, broken behavior, or phrases like 'what's wrong', 'this isn't working', 'help me fix this', or 'investigate this bug'.

say something like
  • "Debug this: my API returns a 500 error after today's deploy"
  • "Stack trace shows NullPointerException on line 42. What does that mean?"
  • "The checkout page stopped working yesterday. Where do I start?"
what you might get back
First, I need to understand the symptom. You said you're getting a 500 error after today's deploy. Can you paste the error message or logs? And can you reproduce it consistently, or does it happen randomly? Also, what specific change went out in today's deploy? Once I know those three things, we can narrow down whether it's the code change itself, a missing environment variable, or a database issue.
how to know it worked

You'll know it worked because the skill asked you for the symptom, reproduction steps, recent changes, and error logs before jumping to a fix.

is this skill working for me
never used
cloud runs
0
0 deployments
local fires
0
Claude Code (optional)
posts published
0
from drafts
attributed
$0.00
signups + revenue
Deploy this skill as a cloud automation to put it to work — runs on a schedule, dispatches output to Telegram or email, and logs every result here.

Deploy this skill

no laptop required

Run this skill on a schedule in the cloud. Pipe output to Telegram, email, or any webhook. Every run is logged here with full output, cost, and thumbs feedback.

How this performs

Cloud-automation runs, real outputs, and feedback.

No cloud runs yet for this skill.

Once you deploy it (above), every run will show up here with the actual output, exact cost, and a thumbs button so you can rate quality over time.

what this is

Claude Code skill at /Users/olanrewajukareem/.claude/skills/debug-assistant/SKILL.md. Auto-triggered by description matching when you type in Claude Code, OR embedded into agent system prompts (LeadFlow framework skills are wired this way). Auto-synced from disk every 6h via launchd.

Use this skill when debugging an error, stack trace, unexpected behavior, or production incident. Triggers on "debug this", "what's wrong", "this isn't working", "stack trace", "error message", "exception", "why is this broken", "help me fix", "inves

Local Claude Code use (optional)

Install the SKILL.md file locally so this skill is available the next time you open Claude Code on your Mac. Most users skip this and just use cloud deployments above.

Install on your machine

Save this skill to ~/.claude/skills/debug-assistant/SKILL.md so Claude Code auto-loads it whenever its description matches your prompt.

30-day activity
never used
2026-04-03today
cost model
unitincluded
capabilities
{
  "source": "global",
  "description": "Use this skill when debugging an error, stack trace, unexpected behavior, or production incident. Triggers on \"debug this\", \"what's wrong\", \"this isn't working\", \"stack trace\", \"error message\", \"exception\", \"why is this broken\", \"help me fix\", \"investigate this bug\"."
}
how it gets called
{
  "method": "embed_in_prompt",
  "skill_path": "/Users/olanrewajukareem/.claude/skills/debug-assistant/SKILL.md"
}
This tool has never been called in the last 30 days.

That means either: (a) the system has not had a task that matched its strengths, (b) a more cost-effective alternative was picked by the router, or (c) the related automation is toggled OFF on /automations. The Recommender reviews idle tools weekly and may suggest killing it.