jahro-troubleshooting
Diagnoses common Jahro issues using decision trees: commands not appearing, watcher not updating, console not opening, snapshots failing, launch button missing. Use when the user reports something not working, missing, broken, or unexpected with Jahro, or when generated Jahro code doesn't behave as expected.
98
100%
Does it follow best practices?
Impact
92%
1.91xAverage score across 3 eval scenarios
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that follows best practices. It uses third person voice, lists specific diagnostic scenarios, includes natural trigger terms users would actually say when experiencing problems, and clearly defines both capabilities and usage conditions. The Jahro-specific terminology makes it highly distinctive.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete issues: 'commands not appearing, watcher not updating, console not opening, snapshots failing, launch button missing' - these are precise, actionable diagnostic scenarios. | 3 / 3 |
Completeness | Clearly answers both what ('Diagnoses common Jahro issues using decision trees' with specific issue list) and when ('Use when the user reports something not working, missing, broken, or unexpected with Jahro'). | 3 / 3 |
Trigger Term Quality | Includes natural user language: 'not working', 'missing', 'broken', 'unexpected', 'doesn't behave as expected' - these are exactly how users describe problems. Also includes specific feature names users would mention. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive - specifically scoped to 'Jahro' product troubleshooting with named features (watcher, console, snapshots, launch button). Unlikely to conflict with other skills due to product-specific terminology. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an exemplary troubleshooting skill that uses decision trees effectively to guide Claude through diagnostic workflows. The content is concise, actionable with real code snippets, includes explicit verification steps after each fix, and is well-organized for quick issue identification. The verify-after-fix loop ensures Claude doesn't stop at the first attempted solution.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, using decision trees to present diagnostic logic without explaining concepts Claude already knows. No unnecessary padding or explanations of what Jahro is or how Unity works. | 3 / 3 |
Actionability | Provides concrete, executable code snippets (RegisterObject pattern, null-safe property getters, debug logging), specific menu paths (Tools → Jahro Settings), and exact steps to verify fixes. Copy-paste ready. | 3 / 3 |
Workflow Clarity | Excellent multi-step diagnostic workflows with clear decision trees, explicit validation checkpoints ('VERIFY' step after every fix), and feedback loops ('If still broken, continue down the tree'). The verify-after-fix loop is explicitly documented. | 3 / 3 |
Progressive Disclosure | Well-organized with clear sections per issue type, decision trees that allow quick navigation to relevant fixes, and an optional 'Source Code Tracing' section for advanced debugging. Content is appropriately structured without unnecessary nesting. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- jahro-console/unity-agent-skills
- Commit
300b45d
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.