vocello-device-diagnostics
Skill388 starsChanged 21 days agoMITView on GitHub
Inspect or debug the paired physical iPhone through the repository headless device driver and retained diagnostics.
In this repository8 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- website/CLAUDE.mdCLAUDE.md
- vocello-benchmarkSkill
- vocello-debugSkill
- 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/ios-device-testing.md and docs/reference/native-engineering.md.
- Very specific: line 15
Use a quiet committed checkpoint for measured bench/lang-bench/memory/profile lanes, after joining workers.
≈ “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
Physical-device diagnostics
Arguments: $ARGUMENTS
Read docs/reference/ios-device-testing.md and docs/reference/native-engineering.md. Use
scripts/ios_device.sh help to select its current verb; begin with doctor or device-state when
the environment is uncertain. Prefer retained logs/crashes first. Run only the relevant
scripts/ios_device.sh <verb> <options>; this driver is headless, not a native UI driver.
Use a quiet committed checkpoint for measured bench/lang-bench/memory/profile lanes, after joining
workers. No new models/downloads, distribution-candidate install/launch or external publication
without specific authorization. Candidate acceptance uses the documented preinstalled-candidate route.
Print only privacy-safe summaries; retain raw artifacts untracked. Classify the result and crash
delta accurately. Never retry silently or replace failed evidence. MobileBuildMCP runs only its
discovery and coverage workflows (its device and debugging workflows stay off); repository scripts own
the final evidence.
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.

