Agent skill

Maestro Diagnose

by ReinaMacCredy in ReinaMacCredy/maestro

Diagnosis-only investigation of a failure with unknown cause - reproduce, localize, reduce, deliver root cause with evidence.

MITAuto-check passedMobile

Install Maestro Diagnose

skills CLI
$ npx skills add ReinaMacCredy/maestro --skill maestro-diagnose -a claude-code

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

GitHub CLI
$ gh skill install ReinaMacCredy/maestro maestro-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/ReinaMacCredy/maestro.git skills-src && mkdir -p .claude/skills && cp -r skills-src/src/plugins/skills/maestro-diagnose .claude/skills/maestro-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
maestro-diagnose
GitHub stars
233
Token cost
~592 tokens
SKILL.md length
293 words
Files
1
Skills in repo
11
Repo updated
First seen
Licence
MIT

At a glance

Diagnosis-only investigation of a failure with unknown cause - reproduce, localize, reduce, deliver root cause with evidence.

  • Works in 4 steps: Reproduce. Capture the exact failing… → Localize. Bisect the surface: which… → Reduce. Shrink to the smallest input or… → …
  • Vietnamese phrasings such as root cause là ở đâu
  • Calls git
  • Nguyên nhân là gì

What it does

Maestro Diagnose is an agent skill from ReinaMacCredy/maestro. Diagnosis-only investigation of a failure with unknown cause - reproduce, localize, reduce, deliver root cause with evidence. Read-only; an explicit fix request routes by target and tier instead, never here. Also triggers on Vietnamese phrasings such as root cause là ở đâu, nguyên nhân là gì, tại sao nó không.

Its SKILL.md is about 590 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Mobile, covering Mobile testing and debugging and Root cause analysis. The repository describes itself as: Local-first coordination for human and agent work: durable work, decisions, dispatches, evidence, and prompt-first methods, powered by TypeScript and Bun. The licence is MIT.

When your agent uses it

  • Vietnamese phrasings such as root cause là ở đâu
  • Nguyên nhân là gì
  • Tại sao nó không

Example prompts

  • “/maestro-diagnose”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Reproduce. Capture the exact failing command or input and its output.
  2. Localize. Bisect the surface: which layer, module, commit, or input
  3. Reduce. Shrink to the smallest input or state that still fails.
  4. Deliver. Root cause plus its evidence chain, the reduced reproduction,

What it can do on your machine

Read from SKILL.md and the folder at commit 2412403. 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

    Shell commands in SKILL.md call:

    • git

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

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    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

Maestro Diagnose loads about 592 tokens when it runs. Until then it costs about 82 tokens; SKILL.md has 293 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~82
When it runs · the whole SKILL.md, loaded when a task matches
~592

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); files beside SKILL.md are not scanned.

SKILL.md

The full file from ReinaMacCredy/maestro at commit 2412403, republished under its MIT licence (© ReinaMacCredy). 293 words, ~592 tokens.

Download SKILL.mdSave it as .claude/skills/maestro-diagnose/SKILL.md (or your agent's skills folder).
name
maestro-diagnose
description
Diagnosis-only investigation of a failure with unknown cause - reproduce, localize, reduce, deliver root cause with evidence. Read-only; an explicit fix request routes by target and tier instead, never here. Also triggers on Vietnamese phrasings such as root cause là ở đâu, nguyên nhân là gì, tại sao nó không.
review-date
2026-11-28
<!-- maestro-skill-version: dev -->

maestro-diagnose

Find the cause; change nothing. Any tier may use it.

  1. Reproduce. Capture the exact failing command or input and its output. No reproduction: say so and stop; do not guess from symptoms.
  2. Localize. Bisect the surface: which layer, module, commit, or input feature flips the behavior. Prefer evidence (logs, minimal harnesses, git bisect) over reading and speculating.
  3. Reduce. Shrink to the smallest input or state that still fails.
  4. Deliver. Root cause plus its evidence chain, the reduced reproduction, and the smallest fix direction. With a work item: maestro work note <id> carries the one-line cause and the reproduction command; in a bundle, also the NOTES.md Current State. Otherwise the conversation.

Discipline

  • Every probe follows a written hypothesis, "I believe X causes this because Y", then the minimal test that can falsify it. No hypothesis, no probe.
  • Recall first: maestro search "<symptom>" and maestro attention. A prior failed: note on the same mechanism is evidence about which hypotheses are already refuted.
  • Three refuted hypotheses in a row: stop treating this as a local bug. Question the architecture; a structural cause or an unsettled design decision is maestro-design work, not a fourth probe.
  • Red flags that mean return to step 1: proposing a fix before the cause is known, changing several things at once, "probably X" without a check.

Diagnosis is read-only toward production code: instrumentation and harnesses live outside production paths or are reverted before delivery.

An explicit fix request routes by target and tier (maestro-bundle tier rule): a quickfix or Light fix proceeds directly with the diagnosis as its first step; Full-tier scope is maestro-work inside the bundle, with the diagnosis as its first phase; a prototype fix belongs to maestro-explore. Never downgrade a requested fix to analysis.

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

Files

Just SKILL.md in src/plugins/skills/maestro-diagnose of ReinaMacCredy/maestro.

Open the folder on GitHubat commit 2412403

Compare with similar skills

Maestro 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.

Maestro Diagnose compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Maestro Diagnose this skillReinaMacCredy/maestro233—~592Automated safety check: PassMIT
Slay the Amethyst Feedback DiagnosisModinMobileSTS/SlayTheAmethystModded406—~2.6kAutomated safety check: PassCustom licence
Android Debuggingrcosteira79/android-skills153—~2.6kAutomated safety check: PassMIT
Uipath InsightsUiPath/skills167—~6.4kAutomated safety check: NotesMIT
Phone HarnessShawnPana/phone-harness3.2k—~7.7kAutomated safety check: PassMIT
Maa Issue Log AnalysisMaaAssistantArknights/MaaAssistantArknights24k—~4kAutomated safety check: PassAGPL-3.0

Similar skills

  • Slay the Amethyst Feedback Diagnosis

    ModinMobileSTS/SlayTheAmethystModded

    Reads Slay the Amethyst diagnostics bundles to decide whether a problem comes from the launcher, a mod or the device, citing exact files and lines.

    406 GitHub stars~2.6k tokensUpdated 3 days ago
    MobileAuto-check passed
  • Android Debugging

    rcosteira79/android-skills

    Android and KMP debugging techniques for crashes, ANRs, memory leaks, R8 traces, Gradle failures and Compose recomposition, built on finding the root cause first.

    153 GitHub stars~2.6k tokensUpdated 22 days ago
    MobileAuto-check passed
  • Uipath Insights

    UiPath/skills

    UiPath Insights monitoring via uip insights: job metrics, failure analysis, and process performance; queue totals, SLA risk, timelines, and failure drill-down; machine availability, fault ranking…

    167 GitHub stars~6.4k tokensUpdated yesterday
    DevelopmentAuto-check: notes
  • Phone Harness

    ShawnPana/phone-harness

    Control the user's phone - an iPhone through the Mac's iPhone Mirroring window, an Android over adb, a rented cloud Android, or a cloud iPhone over HTTPS: open apps, tap, type, swipe, read the screen.

    3.2k GitHub stars~7.7k tokensUpdated today
    MobileAuto-check passed
  • Maa Issue Log Analysis

    MaaAssistantArknights/MaaAssistantArknights

    分析 MaaAssistantArknights 上游仓库公开 Issue(https://github.com/MaaAssistantArknights/MaaAssistantArknights/issues/...

    24k GitHub stars~4k tokensUpdated today
    MobileAuto-check passed
  • Mobile QA

    tloncorp/tlon-apps

    Run a mobile QA checklist on a physical Android device over adb for tlon-apps, then triage what fails into fixes.

    107 GitHub stars~2.4k tokensUpdated yesterday
    MobileAuto-check passed

More from ReinaMacCredy/maestro

All 11 skills in this repo
  • Maestro Improve

    ReinaMacCredy/maestro

    Turn filed lessons into the smallest doctrine edit. An agent skill from ReinaMacCredy/maestro.

    233 GitHub stars~1.9k tokensUpdated 13 days ago
    Auto-check passed
  • Maestro Council

    ReinaMacCredy/maestro

    Lead-only council for a hard-to-reverse fork - a neutral brief, sealed independent seats, one premise verifier on unanimity, bounded verifiers, one cross-examination round, a draft-verdict audit…

    233 GitHub stars~2.9k tokensUpdated 13 days ago
    Auto-check passed
  • Maestro Design

    ReinaMacCredy/maestro

    Resolve material unknowns blocking the next authorized slice, using research, grilling, prototypes, models, or wayfinding.

    233 GitHub stars~2.1k tokensUpdated 13 days ago
    Auto-check passed
  • Maestro Graph

    ReinaMacCredy/maestro

    Drive a pre-known multi-agent path as a maestro graph - run it by name or from a file you just wrote, pull each agent node with graph next, spawn it as a sub-agent under its maestro-<profile…

    233 GitHub stars~2.1k tokensUpdated 13 days ago
    Auto-check passed
  • Maestro Verify

    ReinaMacCredy/maestro

    Verify and close - cross-check coverage, run the VERIFY table, deliver the verdict, harvest durable lessons into decisions, close the bundle, and never claim remote state from local evidence.

    233 GitHub stars~1.9k tokensUpdated 13 days ago
    Auto-check passed
  • Maestro Work

    ReinaMacCredy/maestro

    Implement or fix one authorized unit with minimal edits and sufficient evidence.

    233 GitHub stars~2.6k tokensUpdated 13 days ago
    Auto-check passed

Categories

Questions about Maestro Diagnose

What does Maestro Diagnose do?

Diagnosis-only investigation of a failure with unknown cause - reproduce, localize, reduce, deliver root cause with evidence. Maestro Diagnose is an agent skill from ReinaMacCredy/maestro. Diagnosis-only investigation of a failure with unknown cause - reproduce, localize, reduce, deliver root cause with evidence.

When should I use Maestro Diagnose?

Maestro Diagnose fits situations like: vietnamese phrasings such as root cause là ở đâu; nguyên nhân là gì; Tại sao nó không.

How do I install Maestro Diagnose in Claude Code?

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

How do I install Maestro Diagnose in Codex?

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

Can I use Maestro 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 ReinaMacCredy/maestro --skill maestro-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/maestro-diagnose, .gemini/skills/maestro-diagnose, .github/skills/maestro-diagnose and .opencode/skills/maestro-diagnose in your project.

What does Maestro Diagnose need to run?

Going by SKILL.md and its folder, Maestro Diagnose needs the command-line tools its instructions call (git).

Does Maestro Diagnose access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Maestro 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. Review the folder before installing.

What licence does Maestro Diagnose use?

Maestro 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 Maestro Diagnose use?

About 592 tokens (SKILL.md is roughly 2.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Maestro Diagnose?

Skills that share tags, products or a category with Maestro Diagnose: Slay the Amethyst Feedback Diagnosis (ModinMobileSTS/SlayTheAmethystModded, 406 stars), Android Debugging (rcosteira79/android-skills, 153 stars), Uipath Insights (UiPath/skills, 167 stars) and Phone Harness (ShawnPana/phone-harness, 3.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Maestro Diagnose?

ReinaMacCredy (a GitHub user) maintains it in ReinaMacCredy/maestro, which has 233 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on September 28, 2026.

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