Maestro Diagnose logo

Maestro Diagnose

Community
ReinaMacCredy
maestro-diagnose

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.

Overview

PublisherReinaMacCredy
Repositorymaestro
Skill namemaestro-diagnose
Stars
232
Forks
23
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by ReinaMacCredy on GitHub. Read the source before you install it.

Installation

Install the Maestro Diagnose AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/ReinaMacCredy/maestro.git /tmp/maestro
mkdir -p .claude/skills
cp -r /tmp/maestro/src/plugins/skills/maestro-diagnose .claude/skills/maestro-diagnose
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Maestro Diagnose in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Maestro Diagnose on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Maestro Diagnose is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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.

Frequently asked questions

What does the Maestro Diagnose AI skill do?

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.

Why use Maestro Diagnose on TypingMind?

Because you install it once and use it with any model. Maestro Diagnose is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Maestro Diagnose in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/ReinaMacCredy/maestro/tree/main/src/plugins/skills/maestro-diagnose. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Maestro Diagnose?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Maestro Diagnose?

As many as you like. As long as a model supports skills, you can use Maestro Diagnose with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Maestro Diagnose AI skill free?

Yes. It is published on GitHub by ReinaMacCredy under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇