Apple Crash Log .NET Symbolication
dotnet/skills
Resolves .NET runtime frames in Apple .ips crash logs to function names, source files and line numbers using dSYM symbols, atos and the Microsoft symbol server.
Run the Maestro debugging workflow for investigation-heavy tasks
Install Debug Workflow
$ npx skills add josstei/maestro-orchestrate --skill debug-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install josstei/maestro-orchestrate debug-workflow --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/josstei/maestro-orchestrate.git skills-src && mkdir -p .claude/skills && cp -r skills-src/claude/skills/debug-workflow .claude/skills/debug-workflow && 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 "debug-workflow" agent skill from https://github.com/josstei/maestro-orchestrate/tree/main/claude/skills/debug-workflow into .claude/skills/debug-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debug-workflow", 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/josstei/maestro-orchestrate/tree/main/claude/skills/debug-workflowType 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 josstei/maestro-orchestrate --skill debug-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install josstei/maestro-orchestrate debug-workflow --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/josstei/maestro-orchestrate.git skills-src && mkdir -p .agents/skills && cp -r skills-src/claude/skills/debug-workflow .agents/skills/debug-workflow && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "debug-workflow" agent skill from https://github.com/josstei/maestro-orchestrate/tree/main/claude/skills/debug-workflow into .agents/skills/debug-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debug-workflow", 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 josstei/maestro-orchestrate --skill debug-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install josstei/maestro-orchestrate debug-workflow --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/josstei/maestro-orchestrate.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/claude/skills/debug-workflow .cursor/skills/debug-workflow && 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 "debug-workflow" agent skill from https://github.com/josstei/maestro-orchestrate/tree/main/claude/skills/debug-workflow into .cursor/skills/debug-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debug-workflow", 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/josstei/maestro-orchestrate.git --path claude/skills/debug-workflow--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 josstei/maestro-orchestrate --skill debug-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install josstei/maestro-orchestrate debug-workflow --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/josstei/maestro-orchestrate.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/claude/skills/debug-workflow .gemini/skills/debug-workflow && 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 "debug-workflow" agent skill from https://github.com/josstei/maestro-orchestrate/tree/main/claude/skills/debug-workflow into .gemini/skills/debug-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debug-workflow", 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 josstei/maestro-orchestrate debug-workflowInstalls 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 josstei/maestro-orchestrate --skill debug-workflow -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/josstei/maestro-orchestrate.git skills-src && mkdir -p .github/skills && cp -r skills-src/claude/skills/debug-workflow .github/skills/debug-workflow && 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 "debug-workflow" agent skill from https://github.com/josstei/maestro-orchestrate/tree/main/claude/skills/debug-workflow into .github/skills/debug-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debug-workflow", 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 josstei/maestro-orchestrate --skill debug-workflow -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install josstei/maestro-orchestrate debug-workflow --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/josstei/maestro-orchestrate.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/claude/skills/debug-workflow .opencode/skills/debug-workflow && 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 "debug-workflow" agent skill from https://github.com/josstei/maestro-orchestrate/tree/main/claude/skills/debug-workflow into .opencode/skills/debug-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debug-workflow", 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
debug-workflow- GitHub stars
- 465
- Token cost
- ~238 tokens
- SKILL.md length
- 112 words
- Files
- 1
- Skills in repo
- 17
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Run the Maestro debugging workflow for investigation-heavy tasks
- Works in 5 steps: Establish the failing behavior, repro… → Form concrete hypotheses (2-3 likely… → Gather evidence from code, logs, tests,… → …
- Tasks that involve Mobile testing and debugging
- SKILL.md covers Protocol, Workflow and Constraints
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Debug Workflow is an agent skill from josstei/maestro-orchestrate. Run the Maestro debugging workflow for investigation-heavy tasks
Its SKILL.md is about 240 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 Debugging. The repository describes itself as: Multi-agent orchestration platform for Gemini CLI, Claude Code, Codex, and Qwen Code — 39 specialists, parallel subagents, persistent sessions, and built-in code review…. The licence is Apache-2.0.
When your agent uses it
- Tasks that involve Mobile testing and debugging
- Tasks that involve Debugging
Example prompts
- “/debug-workflow”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Establish the failing behavior, repro path, and expected behavior
- Form concrete hypotheses (2-3 likely root causes)
- Gather evidence from code, logs, tests, and runtime behavior before proposing fixes
- Isolate the most likely root cause and trace the execution path from trigger to failure
- Verify the conclusion explains all symptoms and present the recommended fix with specific code location
What it can do on your machine
Read from SKILL.md and the folder at commit 4f5d434. 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
Debug Workflow loads about 238 tokens when it runs. Until then it costs about 20 tokens; SKILL.md has 112 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 josstei/maestro-orchestrate at commit 4f5d434, republished under its Apache-2.0 licence (© josstei). 112 words, ~238 tokens.
Download SKILL.mdSave it as
.claude/skills/debug-workflow/SKILL.md (or your agent's skills folder).- name
- debug-workflow
- description
- Run the Maestro debugging workflow for investigation-heavy tasks
Maestro Debug Workflow
Call get_skill_content with resources: ["architecture"].
Protocol
Before delegating, call get_skill_content with resources: ["delegation"] and follow the returned methodology.
Workflow
- Establish the failing behavior, repro path, and expected behavior
- Form concrete hypotheses (2-3 likely root causes)
- Gather evidence from code, logs, tests, and runtime behavior before proposing fixes
- Isolate the most likely root cause and trace the execution path from trigger to failure
- Verify the conclusion explains all symptoms and present the recommended fix with specific code location
Constraints
- Prefer evidence over speculation
- Make uncertainty explicit when the issue cannot be reproduced
- Return root cause, affected files, confidence level, and the smallest defensible next action
© josstei, Apache-2.0. 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 claude/skills/debug-workflow of josstei/maestro-orchestrate.
Open the folder on GitHubat commit 4f5d434
Compare with similar skills
Debug Workflow 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 |
|---|---|---|---|---|---|---|
| Debug Workflow this skilljosstei/maestro-orchestrate | 465 | — | ~238 | Automated safety check: Pass | Apache-2.0 | |
| Apple Crash Log .NET Symbolicationdotnet/skills | 5.6k | 1 repos | ~2.4k | Automated safety check: Pass | MIT | |
| Slay the Amethyst Feedback DiagnosisModinMobileSTS/SlayTheAmethystModded | 400 | — | ~2.6k | Automated safety check: Pass | Custom licence | |
| Android Debuggingrcosteira79/android-skills | 150 | — | ~2.6k | Automated safety check: Pass | MIT | |
| Mobile App Debuggingsecondsky/claude-skills | 227 | — | ~513 | Automated safety check: Pass | MIT | |
| Maui AI DebuggingRedth/Maui.Gtk | 101 | — | ~4.1k | Automated safety check: Pass | MIT |
Similar skills
- Official
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.
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.
Mobile App Debugging
secondsky/claude-skills
Mobile app debugging for iOS, Android, cross-platform frameworks.
Maui AI Debugging
Redth/Maui.Gtk
End-to-end workflow for building, deploying, inspecting, and debugging .NET MAUI and MAUI Blazor Hybrid apps as an AI agent.
Magicnet Device Debugging
LIghtJUNction/MagicNet
Debug and verify MagicNet on a real Android root device. An agent skill from LIghtJUNction/MagicNet.
More from josstei/maestro-orchestrate
All 17 skills in this repoCode Review
josstei/maestro-orchestrate
Standalone code review methodology for structured, severity-classified code assessment
Execution
josstei/maestro-orchestrate
Phase execution methodology for orchestration workflows with error handling and completion protocols
Implementation Planning
josstei/maestro-orchestrate
Generates detailed implementation plans from finalized designs
Session Management
josstei/maestro-orchestrate
Manages orchestration session state, tracking, and resumption
Validation
josstei/maestro-orchestrate
Cross-cutting validation methodology for verifying phase outputs and project integrity
Delegation
josstei/maestro-orchestrate
Agent delegation best practices for constructing effective subagent prompts with proper scoping
Related
Categories
Questions about Debug Workflow
What does Debug Workflow do?
Run the Maestro debugging workflow for investigation-heavy tasks. Debug Workflow is an agent skill from josstei/maestro-orchestrate.
When should I use Debug Workflow?
Debug Workflow fits situations like: tasks that involve Mobile testing and debugging; tasks that involve Debugging.
How do I install Debug Workflow in Claude Code?
Run `npx skills add josstei/maestro-orchestrate --skill debug-workflow -a claude-code`. Or copy the skill folder (claude/skills/debug-workflow in josstei/maestro-orchestrate) into .claude/skills/debug-workflow in your project. Claude Code loads it when a task matches its description.
How do I install Debug Workflow in Codex?
Run `npx skills add josstei/maestro-orchestrate --skill debug-workflow -a codex`. Or copy the skill folder (claude/skills/debug-workflow in josstei/maestro-orchestrate) into .agents/skills/debug-workflow in your project. Codex loads it when a task matches its description.
Can I use Debug Workflow 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 josstei/maestro-orchestrate --skill debug-workflow -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/debug-workflow, .gemini/skills/debug-workflow, .github/skills/debug-workflow and .opencode/skills/debug-workflow in your project.
What does Debug Workflow need to run?
SKILL.md names no scripts, command-line tools or credentials: Debug Workflow is instructions for the agent only.
Does Debug Workflow 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 Debug Workflow 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 Debug Workflow use?
Debug Workflow is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Debug Workflow use?
About 238 tokens (SKILL.md is roughly 952 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 Debug Workflow?
Skills that share tags, products or a category with Debug Workflow: Apple Crash Log .NET Symbolication (dotnet/skills, 5.6k stars), Slay the Amethyst Feedback Diagnosis (ModinMobileSTS/SlayTheAmethystModded, 400 stars), Android Debugging (rcosteira79/android-skills, 150 stars) and Mobile App Debugging (secondsky/claude-skills, 227 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Debug Workflow?
josstei (a GitHub user) maintains it in josstei/maestro-orchestrate, which has 465 GitHub stars. The repository holds 17 skills in this directory. The repository was last updated on October 6, 2026.
Source: josstei/maestro-orchestrate on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.