cc-skill:diagnose

Claude Code skill · anthropic · active

last 30 days

0 calls

0 of 30 days active

explain like I am new to this

what it does

Walks you through a disciplined process for finding and fixing hard bugs. It starts by building a fast, reliable way to reproduce the problem, then uses that to narrow down the cause and verify the fix works.

who it is for

Anyone dealing with a bug that won't go away or a performance problem that's hard to pin down.

when it fires

When you say something like 'diagnose this bug', 'debug why this is failing', 'something is broken', or describe a performance regression.

say something like

"Diagnose why the login endpoint is timing out"
"Debug this error: 'undefined is not a function'"
"Our API got 10x slower after the last deploy"

what you might get back

I'll help you fix this. First, let's build a way to see the bug happen reliably. Can you run this test file I've written? If it fails the same way you described, we have a feedback loop. Then we'll narrow down exactly where the problem is by testing each hypothesis, and finally verify the fix actually solves it.

how to know it worked

You'll know it worked because Claude Code will first ask you to create a reproducible test or script that shows the bug, rather than immediately offering fixes.

is this skill working for me

never used

cloud runs

0 deployments

local fires

Claude Code (optional)

posts published

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/diagnose/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.

Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing

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/diagnose/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": "Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says \"diagnose this\" / \"debug this\", reports a bug, says something is broken/throwing/failing, or describes a performance regression."
}

how it gets called

{
  "method": "embed_in_prompt",
  "skill_path": "/Users/olanrewajukareem/.claude/skills/diagnose/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.