jahro-snapshots
Guides snapshot mode selection, capture workflows, QA sharing, and team setup for Jahro Snapshots. Use when the user mentions snapshots, bug capture, sharing logs, streaming, recording, QA workflow, team collaboration, or wants to share debugging sessions with their team.
87
83%
Does it follow best practices?
Impact
93%
4.04xAverage score across 3 eval scenarios
Passed
No known issues
Quality
Discovery
89%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 with strong trigger term coverage and explicit 'Use when' guidance. The main weakness is that the capability descriptions are somewhat abstract (e.g., 'capture workflows') rather than listing concrete actions. The product-specific naming (Jahro Snapshots) provides excellent distinctiveness.
Suggestions
Make capabilities more concrete by specifying exact actions, e.g., 'record bug reproduction sessions, export debug logs, configure streaming settings' instead of 'capture workflows'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Jahro Snapshots) and lists several actions (snapshot mode selection, capture workflows, QA sharing, team setup), but the actions are somewhat abstract rather than concrete operations like 'record bug sessions' or 'export logs to teammates'. | 2 / 3 |
Completeness | Clearly answers both what (guides snapshot mode selection, capture workflows, QA sharing, team setup) AND when (explicit 'Use when...' clause with comprehensive trigger scenarios including snapshots, bug capture, sharing logs, etc.). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'snapshots', 'bug capture', 'sharing logs', 'streaming', 'recording', 'QA workflow', 'team collaboration', 'debugging sessions'. These are varied and cover multiple ways users might phrase their needs. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with the specific product name 'Jahro Snapshots' and domain-specific triggers like 'QA sharing', 'streaming', and 'debugging sessions'. Unlikely to conflict with generic documentation or collaboration skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
77%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 skill with excellent actionability and workflow clarity. The QA capture workflow and mode selection guides are particularly strong with concrete steps and decision tables. The main weakness is that it's somewhat verbose for a skill file and could benefit from splitting detailed reference content (like team roles, session statuses) into separate files.
Suggestions
Consider moving the detailed 'Team Setup' section to a separate TEAM-SETUP.md file and linking to it, keeping only a brief mention in the main skill
Trim the 'What Snapshots Capture' section - Claude can infer most of this from the workflow descriptions
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some explanatory text that could be trimmed. Tables are well-used for density, but sections like 'What Snapshots Capture' and 'Web Console' add context Claude could infer from the workflow descriptions. | 2 / 3 |
Actionability | Provides concrete, step-by-step workflows with specific UI paths (Tools → Jahro Settings → Snapshots Settings), exact gestures (triple-tap), and clear decision tables. The QA Capture Workflow is copy-paste ready for testers. | 3 / 3 |
Workflow Clarity | Multi-step processes are clearly sequenced with numbered steps. The QA workflow includes explicit checkpoints (Start → Reproduce → Screenshot → Stop → Share). Session statuses table provides clear state machine with next actions. Verification section at the end provides a feedback loop. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections and tables, but it's somewhat monolithic. The 'Web Console' section acknowledges external docs exist but doesn't link to them. References to jahro-troubleshooting skill at the end is good, but more content could be split into separate files (e.g., team setup, mode selection details). | 2 / 3 |
Total | 10 / 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.