OpenGUI Installer for DSH
Core-Mate/OpenGUI
Installs and verifies the latest stable OpenGUI release in a DeepSeek Harness web profile on macOS without disturbing existing plugins or settings.
A skill your agent uses when the user wants to find problems, audit workflow quality, or get a comprehensive health check on their AI workflow.
Install Diagnose
$ npx skills add sharpdeveye/maestro --skill diagnose -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install sharpdeveye/maestro diagnose --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/sharpdeveye/maestro.git skills-src && mkdir -p .claude/skills && cp -r skills-src/source/skills/diagnose .claude/skills/diagnose && rm -rf skills-srcUse ~/.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/
Install the "diagnose" agent skill from https://github.com/sharpdeveye/maestro/tree/main/source/skills/diagnose into .claude/skills/diagnose/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "diagnose", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/sharpdeveye/maestro/tree/main/source/skills/diagnoseType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add sharpdeveye/maestro --skill diagnose -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install sharpdeveye/maestro diagnose --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sharpdeveye/maestro.git skills-src && mkdir -p .agents/skills && cp -r skills-src/source/skills/diagnose .agents/skills/diagnose && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "diagnose" agent skill from https://github.com/sharpdeveye/maestro/tree/main/source/skills/diagnose into .agents/skills/diagnose/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "diagnose", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add sharpdeveye/maestro --skill diagnose -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install sharpdeveye/maestro diagnose --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sharpdeveye/maestro.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/source/skills/diagnose .cursor/skills/diagnose && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "diagnose" agent skill from https://github.com/sharpdeveye/maestro/tree/main/source/skills/diagnose into .cursor/skills/diagnose/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "diagnose", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/sharpdeveye/maestro.git --path source/skills/diagnose--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add sharpdeveye/maestro --skill diagnose -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install sharpdeveye/maestro diagnose --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sharpdeveye/maestro.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/source/skills/diagnose .gemini/skills/diagnose && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "diagnose" agent skill from https://github.com/sharpdeveye/maestro/tree/main/source/skills/diagnose into .gemini/skills/diagnose/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "diagnose", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install sharpdeveye/maestro diagnoseInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add sharpdeveye/maestro --skill diagnose -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/sharpdeveye/maestro.git skills-src && mkdir -p .github/skills && cp -r skills-src/source/skills/diagnose .github/skills/diagnose && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "diagnose" agent skill from https://github.com/sharpdeveye/maestro/tree/main/source/skills/diagnose into .github/skills/diagnose/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "diagnose", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add sharpdeveye/maestro --skill diagnose -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install sharpdeveye/maestro diagnose --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sharpdeveye/maestro.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/source/skills/diagnose .opencode/skills/diagnose && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "diagnose" agent skill from https://github.com/sharpdeveye/maestro/tree/main/source/skills/diagnose into .opencode/skills/diagnose/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "diagnose", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
diagnose- GitHub stars
- 592
- Token cost
- ~1.5k tokens
- SKILL.md length
- 578 words
- Files
- 1
- Skills in repo
- 25
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when the user wants to find problems, audit workflow quality, or get a comprehensive health check on their AI workflow.
- The user wants to find problems
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Audit workflow quality
- Get a comprehensive health check on their AI workflow
What it does
Diagnose is an agent skill from sharpdeveye/maestro. Use when the user wants to find problems, audit workflow quality, or get a comprehensive health check on their AI workflow.
Its SKILL.md is about 1.5k 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 Agent Workflows. The repository describes itself as: Workflow fluency for AI coding agents. 1 core skill · 25 commands · 7 domain references · memory layer · audit trail — works across Cursor, Claude Code, Gemini CLI, Copilot, and… The licence is MIT.
When your agent uses it
- The user wants to find problems
- Audit workflow quality
- Get a comprehensive health check on their AI workflow
Example prompts
- “/diagnose”
What it can do on your machine
Read from SKILL.md and the folder at commit 00f9115. 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
No scripts in the folder and no shell commands in SKILL.md.
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.5k tokens when it runs. Until then it costs about 33 tokens; SKILL.md has 578 words of instructions outside code blocks.
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 sharpdeveye/maestro at commit 00f9115, republished under its MIT licence (© sharpdeveye). 578 words, ~1,458 tokens.
Download SKILL.mdSave it as
.claude/skills/diagnose/SKILL.md (or your agent's skills folder).- name
- diagnose
- description
- Use when the user wants to find problems, audit workflow quality, or get a comprehensive health check on their AI workflow.
- argument-hint
- [target area]
- category
- analysis
- version
- 2.0.0
- user-invocable
- true
MANDATORY PREPARATION
Invoke /agent-workflow — it contains workflow principles, anti-patterns, and the Context Gathering Protocol. Follow the protocol before proceeding — if no workflow context exists yet, you MUST run /teach-maestro first.
Perform a systematic diagnostic scan across 5 dimensions. For each dimension, score 1-5 and provide specific findings.
Dimension 1: Prompt Quality (1-5)
Evaluate:
- Structure (4-zone pattern: role, context, instructions, output)
- Output schema definition (explicit vs. implicit)
- Instruction clarity (specific vs. vague)
- Edge case handling (addressed vs. ignored)
- Anti-patterns present (wall of text, contradictions, implicit format)
Dimension 2: Context Efficiency (1-5)
Evaluate:
- Context budget allocation (planned vs. ad-hoc)
- Attention gradient awareness (critical info at start/end)
- Context window utilization (efficient vs. wasteful)
- State management (explicit vs. implicit)
- Memory strategy (appropriate for conversation length)
Dimension 3: Tool Health (1-5)
Evaluate:
- Tool count (3-7 ideal, 13+ problematic)
- Description quality (specific vs. vague)
- Error handling (graceful vs. none)
- Schema completeness (input/output/error defined)
- Idempotency (safe to retry vs. side-effect prone)
- Scope attribution: Distinguish between project-configured tools (e.g., custom scripts, project MCP servers) and agent-level tools (e.g., built-in IDE tools, global MCP servers). Only flag tool overhead for tools the project can actually control
Dimension 4: Architecture Fitness (1-5)
Evaluate:
- Topology appropriateness (single vs. multi-agent justified)
- Agent boundaries (clear vs. overlapping)
- Handoff protocols (structured vs. ad-hoc)
- Observability (decisions logged vs. black box)
- Cost awareness (budgeted vs. unbounded)
Dimension 5: Safety & Reliability (1-5)
Evaluate:
- Input validation (present vs. absent)
- Output filtering (PII, content policy) — scope contextually: data flowing between a user's own frontend and backend (e.g., authenticated sessions, internal APIs) is lower risk than data exposed to external services or third-party APIs
- Cost controls (ceilings set vs. unbounded)
- Error recovery (fallbacks vs. crash)
- Evaluation strategy (golden tests vs. "it seems to work")
Diagnostic Report Format
╔══════════════════════════════════════╗
║ MAESTRO DIAGNOSTIC ║
╠══════════════════════════════════════╣
║ Prompt Quality ████░ 4/5 ║
║ Context Efficiency ███░░ 3/5 ║
║ Tool Health ██░░░ 2/5 ║
║ Architecture ████░ 4/5 ║
║ Safety & Reliability ██░░░ 2/5 ║
╠══════════════════════════════════════╣
║ Overall Score: 15/25 ║
╚══════════════════════════════════════╝
CRITICAL FINDINGS:
1. [Most severe issue — immediate action needed]
2. [Second most severe]
3. [Third]
RECOMMENDED ACTIONS:
1. Run /fortify to add error handling (addresses Tool Health + Safety)
2. Run /streamline to reduce tool count (addresses Tool Health)
3. Run /refine for prompt structure improvements (addresses Prompt Quality)Show full SKILL.md (291 more words)Show less
Maestro Command Mapping
Every recommended action MUST reference the specific Maestro command that addresses it. Use this mapping:
| Dimension Gap | Maestro Command | When to Recommend |
|---|---|---|
| Prompt structure, clarity, output schema | /refine | Score ≤ 4 on Prompt Quality |
| Context budget, attention gradient, memory | /streamline | Score ≤ 3 on Context Efficiency |
| Tool errors, missing tools, redundant tools | /fortify | Score ≤ 3 on Tool Health |
| Tool count reduction, unused tools | /streamline | Tool count > 7 or unused tools found |
| Safety gaps, error recovery, validation | /fortify | Score ≤ 3 on Safety & Reliability |
| Test coverage, golden tests, evaluation | /guard | No automated tests or evaluation strategy |
| Architecture boundaries, observability | /calibrate | Score ≤ 3 on Architecture Fitness |
Do NOT give generic manual actions (e.g., "Add Vitest", "Create a rollback script") without also specifying which Maestro command the user should run to implement it. The recommended action format is:
Run
/<command>to [specific action] (addresses [Dimension] #[gap number])
Scoring Guide
| Score | Meaning | Maestro Action |
|---|---|---|
| 5 | Production-excellent | No action needed |
| 4 | Good with minor gaps | /refine for polish |
| 3 | Functional but risky | /fortify or /streamline for targeted fix |
| 2 | Significant issues | /fortify + /guard — immediate attention |
| 1 | Broken or missing | /onboard-agent — rebuild required |
Diagnostic Checklist
- All 5 dimensions scored with specific evidence
- Critical findings listed in priority order
- Each finding includes specific file/component location
- Recommended actions reference specific Maestro commands (see Command Mapping above)
- Overall score calculated and report generated
Recommended Next Step
After diagnosis, run the command mapped to your lowest-scoring dimension. For a general improvement sequence: /fortify → /streamline → /refine.
NEVER:
- Give all 5s unless the workflow is genuinely production-excellent
- Skip dimensions — score all 5 even if some seem fine
- Diagnose without reading the actual workflow code/config
- Recommend changes without specific findings to support them
- Give generic manual actions without mapping them to a Maestro command
© sharpdeveye, 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 source/skills/diagnose of sharpdeveye/maestro.
Open the folder on GitHubat commit 00f9115
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Diagnose this skillsharpdeveye/maestro | 592 | — | ~1.5k | Automated safety check: Pass | MIT | |
| OpenGUI Installer for DSHCore-Mate/OpenGUI | 1.8k | — | ~1.1k | Automated safety check: Pass | Custom licence | |
| Docs Gardeningmhmzdev/the-holy-quran-app | 889 | — | ~1.1k | Automated safety check: Pass | MIT | |
| Carnetjfarcand/mirroir-mcp | 245 | — | ~2.8k | Automated safety check: Pass | Apache-2.0 | |
| Team Swarmcatlog22/maestro-flow | 564 | — | ~2k | Automated safety check: Notes | None | |
| Planmhmzdev/the-holy-quran-app | 889 | — | ~957 | Automated safety check: Pass | MIT |
Similar skills
Docs Gardening
mhmzdev/the-holy-quran-app
Audit and maintain The Holy Qur'an app's knowledge base (AGENTS.md, .agents/rules/, docs/ OKF bundle) for staleness, broken cross-links, drift from code, and OKF structural issues.
Carnet
jfarcand/mirroir-mcp
Work the private register (mirroir-carnet) from a session — claim an issue before touching it so peers see who holds it and which session, release or close it when done, file new issues in the one…
Team Swarm
catlog22/maestro-flow
Swarm intelligence team skill — ACO-driven multi-agent exploration with hybrid LLM coordinator + Python optimization controller.
Plan
mhmzdev/the-holy-quran-app
Turn an idea or brainstorm into an actionable execution plan for The Holy Qur'an app with phases, file changes, and machine-checkable success criteria.
Iphone Use
leeguooooo/iphone-use
A skill your agent uses when a task needs a real iPhone — operating iOS apps that have no API (Apple Health, banking, IM apps), exporting on-phone data, tapping/typing/scrolling on the phone, or…
More from sharpdeveye/maestro
All 25 skills in this repoAccelerate
sharpdeveye/maestro
A skill your agent uses when the workflow is too slow, too expensive, or both and needs latency, cost, or token usage optimization.
Chain
sharpdeveye/maestro
A skill your agent uses when the workflow needs multi-step processing with sequential, parallel, or conditional tool compositions and proper data flow.
Compose
sharpdeveye/maestro
A skill your agent uses when a single agent demonstrably cannot handle the task and multi-agent coordination is justified.
Extract Pattern
sharpdeveye/maestro
A skill your agent uses when the user wants to create templates, extract reusable patterns, document solutions, or build a pattern library from working workflows.
Fortify
sharpdeveye/maestro
A skill your agent uses when the workflow lacks error handling, has been failing in production, or needs retry logic, fallback strategies, and circuit breakers.
Guard
sharpdeveye/maestro
A skill your agent uses when deploying to production, handling sensitive data, or the workflow needs safety constraints, input validation, and security boundaries.
Related
Categories
Questions about Diagnose
What does Diagnose do?
A skill your agent uses when the user wants to find problems, audit workflow quality, or get a comprehensive health check on their AI workflow. Diagnose is an agent skill from sharpdeveye/maestro. Use when the user wants to find problems, audit workflow quality, or get a comprehensive health check on their AI workflow.
When should I use Diagnose?
Diagnose fits situations like: the user wants to find problems; audit workflow quality; get a comprehensive health check on their AI workflow.
How do I install Diagnose in Claude Code?
Run `npx skills add sharpdeveye/maestro --skill diagnose -a claude-code`. Or copy the skill folder (source/skills/diagnose in sharpdeveye/maestro) 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 sharpdeveye/maestro --skill diagnose -a codex`. Or copy the skill folder (source/skills/diagnose in sharpdeveye/maestro) 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 sharpdeveye/maestro --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?
SKILL.md names no scripts, command-line tools or credentials: Diagnose is instructions for the agent only.
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. Review the folder before installing.
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.5k tokens (SKILL.md is roughly 5.8k 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 Diagnose?
Skills that share tags, products or a category with Diagnose: OpenGUI Installer for DSH (Core-Mate/OpenGUI, 1.8k stars), Docs Gardening (mhmzdev/the-holy-quran-app, 889 stars), Carnet (jfarcand/mirroir-mcp, 245 stars) and Team Swarm (catlog22/maestro-flow, 564 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Diagnose?
sharpdeveye (a GitHub user) maintains it in sharpdeveye/maestro, which has 592 GitHub stars. The repository holds 25 skills in this directory. The repository was last updated on April 29, 2026.
Source: sharpdeveye/maestro on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.