Detects Jahro in Unity projects and guides installation, API key configuration, and feature overview. Use when the user mentions Jahro setup, installation, getting started, debug console, or asks what Jahro can do. Also triggers when no Jahro references are found in a Unity project and the user asks about debugging.
95
92%
Does it follow best practices?
Impact
100%
1.56xAverage 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 a well-crafted skill description that excels across all dimensions. It clearly specifies concrete actions (detection, installation guidance, configuration), provides comprehensive trigger terms including edge cases, and occupies a distinct niche (Jahro in Unity). The explicit 'Use when...' clause with multiple natural trigger scenarios makes it easy for Claude to select appropriately.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple concrete actions: 'Detects Jahro in Unity projects', 'guides installation', 'API key configuration', and 'feature overview'. These are specific, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('Detects Jahro...guides installation, API key configuration, and feature overview') AND when ('Use when the user mentions Jahro setup, installation...'). Includes explicit 'Use when...' clause with multiple trigger scenarios. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'Jahro setup', 'installation', 'getting started', 'debug console', 'what Jahro can do', 'debugging'. Good coverage of variations including the edge case of missing Jahro references. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche: Jahro plugin for Unity projects. The combination of 'Jahro', 'Unity', and specific setup/debugging context makes it highly distinctive and unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured setup and orientation skill with excellent actionability and progressive disclosure. The detection workflow is particularly strong with clear decision logic. The main weakness is some verbosity in explanatory sections that could be trimmed, particularly the 'Quick answers' section which partially duplicates earlier content.
Suggestions
Remove the 'Quick answers' section or consolidate it with earlier content to avoid repetition (e.g., console opening is explained twice)
Trim explanatory text like 'The API key connects the Unity project to the Jahro web console for snapshot uploads and team collaboration' - Claude can infer this from context
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient but includes some unnecessary explanations (e.g., explaining what an API key does, explaining that Debug.Log calls appear in the console). Some sections like 'Quick answers' repeat information already covered elsewhere. | 2 / 3 |
Actionability | Provides concrete, executable guidance throughout: specific menu paths (Tools → Jahro Settings), exact Git URLs for installation, specific keyboard shortcuts, and clear detection steps with actionable outcomes in a decision table. | 3 / 3 |
Workflow Clarity | Clear multi-step workflows for detection (3 checks with decision table), installation (numbered steps), and API key configuration (4 sequential steps). The detection workflow includes explicit validation logic with clear actions for each outcome. | 3 / 3 |
Progressive Disclosure | Excellent structure with clear overview sections and well-signaled references to specialized skills (jahro-commands, jahro-watcher, etc.) and reference files (api-reference.md, common-patterns.md). Navigation tables make it easy to find the right next step. | 3 / 3 |
Total | 11 / 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.
300b45d
Table of Contents
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.