vocello-debug
Skill388 starsChanged 21 days agoMITView on GitHub
Triage a Vocello failure from retained evidence and use focused native, runtime or tooling diagnostics without losing the original failure.
In this repository8 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- website/CLAUDE.mdCLAUDE.md
- vocello-benchmarkSkill
- vocello-device-diagnosticsSkill
- vocello-ios-validationSkill
- vocello-macos-uiSkill
- vocello-release-readinessSkill
- vocello-ui-autonomySkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 11
Read docs/reference/testing-runbook.md and the relevant docs/reference/native-engineering.md or tooling-and-evidence.md sections.
- Very specific: line 21
Use verified Axiom xcsym for symbolication and xcprof for existing traces as appropriate.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Evidence-first debugging
Arguments: $ARGUMENTS
Read docs/reference/testing-runbook.md and the relevant docs/reference/native-engineering.md or
tooling-and-evidence.md sections. Begin with scripts/dev.sh triage <run-directory> --json when
artifacts exist. Inspect the deciding ledger/test, first raw-log failure, crash delta and attachments.
Classify product failure, infrastructure failure, interruption or incomplete evidence before action.
Load applicable Axiom build/concurrency/performance guidance, swift-mlx/swift-mlx-lm skills for runtime
issues and Sosumi/Context7 for authoritative API research. Hand a finished native run to the read-only
vocello-xcresult-triage agent when a second reading helps. Detect optional MobileBuildMCP/LLDB
capabilities in this session; do not assume a device/LLDB route exists. Keep native serialization;
XCUITest is the only automated UI evidence, and computer use may reproduce a report between lanes
(/vocello-ui-autonomy).
Use verified Axiom xcsym for symbolication and xcprof for existing traces as appropriate; locate
helpers under the Claude plugin cache (scripts/dev.sh doctor --json lists them), check executability
and non-mutating help before use. Never xcui or simulator agents.
Repository raw logs, exit statuses, optimization settings and artifact contracts remain authoritative;
retain script-only fallbacks. Reproduce with the smallest deterministic test or justified new lane ID.
Preserve the original failure. No blanket cache clearing, automatic retry or unsupported PASS claim.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

