Agent skill

Diagnose

by avibebuilder in avibebuilder/claude-prime

Investigate unexpected behavior and mysterious bugs. An agent skill from avibebuilder/claude-prime.

MITAuto-check passedTesting & QA

Install Diagnose

skills CLI
$ npx skills add avibebuilder/claude-prime --skill diagnose -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install avibebuilder/claude-prime diagnose --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/avibebuilder/claude-prime.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/diagnose .claude/skills/diagnose && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
diagnose
GitHub stars
120
Used in
1 other repo
Token cost
~1.2k tokens
SKILL.md length
437 words
Files
5 (incl. scripts, references)
Skills in repo
19
Repo updated
First seen
Licence
MIT

At a glance

Investigate unexpected behavior and mysterious bugs. An agent skill from avibebuilder/claude-prime.

  • Works in 5 steps: Understand the symptom → Build hypotheses → Choose the lightest evidence method → …
  • Works locally but not in staging/production
  • SKILL.md covers Process, Constraints and Bug
  • Runs JavaScript scripts from its folder

What it does

Diagnose is an agent skill from avibebuilder/claude-prime. Investigate unexpected behavior and mysterious bugs. Use when the cause of a problem is unknown and the user needs to understand WHY something is happening — symptoms like: sudden unexplained changes in metrics or behavior, works locally but not in staging/production, inconsistent or intermittent failures, correct code producing wrong results, operations succeeding but having no effect, environment-specific failures, duplicate executions, stale data, or any "why did this change?" or "why is this happening?"…

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including scripts and reference files (for example `references/runtime-debugging.md`, `scripts/__tests__/diagnose-server.test.js` and `scripts/diagnose-server.js`).

It sits in Testing & QA, covering Failing and flaky tests and Root cause analysis. The repository describes itself as: You've heard Claude Code can do amazing things. Skills, hooks, agents, memory systems — but who has time to figure all that out? Claude Prime sets it up for you in one command. The licence is MIT.

When your agent uses it

  • Works locally but not in staging/production
  • Intermittent failures
  • Correct code producing wrong results
  • Operations succeeding but having no effect

Example prompts

  • “why did this change?”
  • “why is this happening?”
  • “/diagnose”

Requirements

  • Node.js

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Understand the symptom
  2. Build hypotheses
  3. Choose the lightest evidence method
  4. Gather evidence and iterate
  5. Report the diagnosis

What it can do on your machine

Read from SKILL.md and the folder at commit 80bcfa4. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 3 files in scripts/ (JavaScript), which the agent can run.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Diagnose loads about 1.2k tokens when it runs, and up to ~2.3k if it reads all its reference files. Until then it costs about 205 tokens; SKILL.md has 437 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~205
When it runs · the whole SKILL.md, loaded when a task matches
~1.2k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~2.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from avibebuilder/claude-prime at commit 80bcfa4, republished under its MIT licence (© avibebuilder). 437 words, ~1,174 tokens.

Download SKILL.mdSave it as .claude/skills/diagnose/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.
name
diagnose
description
Investigate unexpected behavior and mysterious bugs. Use when the cause of a problem is unknown and the user needs to understand WHY something is happening — symptoms like: sudden unexplained changes in metrics or behavior, works locally but not in staging/production, inconsistent or intermittent failures, correct code producing wrong results, operations succeeding but having no effect, environment-specific failures, duplicate executions, stale data, or any "why did this change?" or "why is this happening?" situation. Covers infrastructure anomalies (cache hit rates dropping, latency spikes, queue behavior shifts) as well as code bugs. The key signal is confusion about root cause, not a request to implement a known fix. Do NOT use for feature requests, known fixes, planning, or documentation tasks.
argument-hint
bug-description

Think harder.

Process

Check conversation context and skip completed steps.

1. Understand the symptom
  • Read the bug report, errors, logs, and surrounding code carefully
  • Clarify reproduction steps, expected behavior, and environment when they are unclear
  • Separate confirmed facts from working assumptions. List them explicitly:
    • Fact (confirmed): the server returns 200
    • Assumption (unconfirmed): the client receives the full HTML body Misidentifying an assumption as a fact is the most common source of wasted investigation.
2. Build hypotheses
  • Form 2-4 plausible root-cause hypotheses that are mechanistically distinct — different failure layers (e.g., server render vs. client hydration vs. network layer), not variations of the same idea

  • Rank them by likelihood

  • For each hypothesis, state both sides:

    • Confirm if: [what observation would prove this is the cause]
    • Eliminate if: [what observation would rule this out]

    A hypothesis you can't falsify in both directions is too vague to test.

3. Choose the lightest evidence method

Start with the cheapest source of truth that can kill hypotheses:

  • existing logs, traces, stack traces, metrics, and error output
  • static code inspection around the suspected path
  • config, environment, deploy, cache, queue, and permissions state that could explain the symptom
  • targeted reproduction in the relevant environment

Only add new instrumentation when existing evidence is insufficient.

  • If you need runtime probes, read diagnose/references/runtime-debugging.md
  • Use #region agent log / #endregion markers for any instrumentation you add
  • Tag each log point with the relevant hypothesisId
  • Log only the minimum fields needed to discriminate between hypotheses; never log secrets, tokens, passwords, cookies, or full sensitive payloads
  • If runtime probes require starting the local debug server, ask the user before launching it
  • For browser/UI bugs, combine with the agent-browser skill when reproduction or inspection needs it
Show full SKILL.md (157 more words)Show less
4. Gather evidence and iterate
  • Use existing logs, traces, failing tests, or artifacts before asking for a fresh reproduction
  • When reproduction is needed, ask the user to trigger the bug — tie each request to the hypothesis it tests
  • Correlate each finding with the hypothesis it supports or eliminates; narrow based on evidence, not confidence
  • If ambiguity remains, refine hypotheses and add narrower probes — but stop and report when another round is unlikely to produce new discriminating evidence
5. Report the diagnosis

Output structured diagnosis:

## Diagnosis: [Issue Title]

### Symptoms
- [What was observed]

### Evidence
- [Finding] — `file:line` or runtime source — hypothesis X
- ...

### Root Cause
[Confirmed or most likely cause, with evidence]

### Hypotheses Tested
| # | Hypothesis | Confirm if | Eliminate if | Result |
|---|-----------|-----------|-------------|--------|
| A | ... | [what observation would prove this] | [what observation would rule this out] | Confirmed/Eliminated/Inconclusive |

### Recommended Next Steps
- [What to do next — usually hand off to `/fix` with this diagnosis]

### Active Instrumentation
- [List files with `#region agent log` blocks still in place, or `None`]

Constraints

  • NO fixing — investigation and diagnosis only. "Recommended Next Steps" hands off to /fix with the diagnosis; it does not prescribe specific parameter values, code snippets, or step-by-step implementation instructions.
  • Evidence over assumptions — if the code looks wrong but runtime evidence says otherwise, trust the runtime
  • If you add #region agent log blocks, leave them in place for /fix to verify the repair and call them out in the final report

Bug

<bug>$ARGUMENTS</bug>

© avibebuilder, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 4 other files (scripts, references) in .claude/skills/diagnose of avibebuilder/claude-prime.

  • SKILL.md
  • references/runtime-debugging.md
  • scripts/__tests__/diagnose-server.test.js
  • scripts/diagnose-server.js
  • scripts/package.json

Open the folder on GitHubat commit 80bcfa4

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in avibebuilder/claude-prime, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Diagnose next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Diagnose compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Diagnose this skillavibebuilder/claude-prime1201 repos~1.2kAutomated safety check: PassMIT
Pester Failure AnalysisPowerShell/PowerShell56k—~5.1kAutomated safety check: PassMIT
Diagnose a Red Rundifferent-ai/openwork24k—~779Automated safety check: PassCustom licence
Eval Triage And Improvementmicrosoft/eval-guide138—~5.9kAutomated safety check: PassMIT
cmux Package Test Bisectmanaflow-ai/cmux28k—~1.5kAutomated safety check: PassCustom licence
Map Debugazalio/map-framework157—~4.6kAutomated safety check: PassMIT

Similar skills

  • Pester Failure Analysis

    PowerShell/PowerShell

    Investigates failing Pester tests in PowerShell CI jobs by following a six-step workflow from pull request status to documented fix recommendations.

    56k GitHub stars~5.1k tokensUpdated today
    Testing & QAAuto-check passed
  • Diagnose a Red Run

    different-ai/openwork

    Classifies a failing test, typecheck or CI job before any code changes, by recording the failure and running a clean control to show whether it was already broken.

    24k GitHub stars~779 tokensUpdated today
    Testing & QAAuto-check passed
  • Eval Triage And Improvement

    microsoft/eval-guide

    Official

    A skill your agent uses when the user's Copilot Studio agent evaluations have come back and they need to interpret scores, diagnose root causes of underperforming test cases, find remediation steps…

    138 GitHub stars~5.9k tokensUpdated 3 mo ago
    Testing & QAAuto-check passed
  • cmux Package Test Bisect

    manaflow-ai/cmux

    Finds which commit broke a failing Swift package suite in the cmux repo by bisecting on CI, then judges per test whether it went stale or the code regressed.

    28k GitHub stars~1.5k tokensUpdated today
    Testing & QAAuto-check passed
  • Map Debug

    azalio/map-framework

    Structured MAP debugging via decomposer, actor, and monitor agents.

    157 GitHub stars~4.6k tokensUpdated today
    Testing & QAAuto-check passed
  • Map Debug

    azalio/map-framework

    Structured MAP debugging via task-decomposer, actor, and monitor agents.

    157 GitHub stars~4.6k tokensUpdated today
    Testing & QAAuto-check passed

More from avibebuilder/claude-prime

All 19 skills in this repo
  • Frontend Design

    avibebuilder/claude-prime

    Builds distinctive, production-grade UIs that avoid generic AI aesthetics.

    120 GitHub stars~2.1k tokensUpdated 4 mo ago
    Auto-check passed
  • Media Processor

    avibebuilder/claude-prime

    Specialized visual and multimedia processing tools. An agent skill from avibebuilder/claude-prime.

    120 GitHub stars~1.2k tokensUpdated 4 mo ago
    Auto-check: notes
  • Skill Creator

    avibebuilder/claude-prime

    A skill your agent uses when the user wants to work on a Claude Code skill file (SKILL.md): writing one from scratch, testing whether an existing one works well, running evals or benchmarks…

    120 GitHub stars~8.2k tokensUpdated 4 mo ago
    Auto-check passed
  • Self Evolve

    avibebuilder/claude-prime

    The single config quality skill. An agent skill from avibebuilder/claude-prime.

    120 GitHub stars~1.9k tokensUpdated 4 mo ago
    Auto-check passed
  • Cook

    avibebuilder/claude-prime

    Implement, build, create, or add any feature, endpoint, page, component, or functionality.

    120 GitHub stars~970 tokensUpdated 4 mo ago
    Auto-check passed
  • Prime Sync

    avibebuilder/claude-prime

    Syncs Claude config between prime repo and target projects. An agent skill from avibebuilder/claude-prime.

    120 GitHub stars~1.2k tokensUpdated 4 mo ago
    Auto-check passed

Questions about Diagnose

What does Diagnose do?

Investigate unexpected behavior and mysterious bugs. An agent skill from avibebuilder/claude-prime. Diagnose is an agent skill from avibebuilder/claude-prime. Investigate unexpected behavior and mysterious bugs.

When should I use Diagnose?

Diagnose fits situations like: works locally but not in staging/production; intermittent failures; correct code producing wrong results; operations succeeding but having no effect.

How do I install Diagnose in Claude Code?

Run `npx skills add avibebuilder/claude-prime --skill diagnose -a claude-code`. Or copy the skill folder (.claude/skills/diagnose in avibebuilder/claude-prime) into .claude/skills/diagnose in your project. Claude Code loads it when a task matches its description.

How do I install Diagnose in Codex?

Run `npx skills add avibebuilder/claude-prime --skill diagnose -a codex`. Or copy the skill folder (.claude/skills/diagnose in avibebuilder/claude-prime) into .agents/skills/diagnose in your project. Codex loads it when a task matches its description.

Can I use Diagnose in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add avibebuilder/claude-prime --skill diagnose -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/diagnose, .gemini/skills/diagnose, .github/skills/diagnose and .opencode/skills/diagnose in your project.

What does Diagnose need to run?

Going by SKILL.md and its folder, Diagnose needs JavaScript for the scripts in its folder. Our summary lists: Node.js.

Does Diagnose access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Diagnose safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Diagnose use?

Diagnose is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Diagnose use?

About 1.2k tokens (SKILL.md is roughly 4.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.1k tokens, read only when the agent opens those files.

What are the alternatives to Diagnose?

Skills that share tags, products or a category with Diagnose: Pester Failure Analysis (PowerShell/PowerShell, 56k stars), Diagnose a Red Run (different-ai/openwork, 24k stars), Eval Triage And Improvement (microsoft/eval-guide, 138 stars) and cmux Package Test Bisect (manaflow-ai/cmux, 28k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Diagnose?

avibebuilder (a GitHub organization) maintains it in avibebuilder/claude-prime, which has 120 GitHub stars. The repository holds 19 skills in this directory. The repository was last updated on May 16, 2026.

Source: avibebuilder/claude-prime on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.