jahro-migration
Analyzes existing debug systems (IMGUI menus, custom loggers, cheat frameworks, performance HUDs) and generates incremental migration plans to Jahro equivalents. Use when the user wants to replace a custom debug UI, migrate from an existing console or cheat system, switch to Jahro, or has OnGUI debug code they want to modernize.
91
88%
Does it follow best practices?
Impact
98%
1.15xAverage 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 uses third person voice correctly, provides specific concrete actions, includes comprehensive trigger terms that developers would naturally use, and has an explicit 'Use when' clause with multiple relevant scenarios. The focus on Jahro migration creates a clear, distinctive niche.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Analyzes existing debug systems', 'generates incremental migration plans'. Also enumerates specific system types: IMGUI menus, custom loggers, cheat frameworks, performance HUDs. | 3 / 3 |
Completeness | Clearly answers both what (analyzes debug systems, generates migration plans to Jahro) AND when (explicit 'Use when' clause with multiple trigger scenarios: replace custom debug UI, migrate from existing console, switch to Jahro, modernize OnGUI code). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'debug UI', 'migrate', 'console', 'cheat system', 'Jahro', 'OnGUI debug code', 'modernize'. These are terms developers would naturally use when seeking this functionality. | 3 / 3 |
Distinctiveness Conflict Risk | Very clear niche targeting Jahro migration specifically. The combination of 'Jahro', 'IMGUI', 'OnGUI', and 'debug systems migration' creates a distinct trigger profile unlikely to conflict with general Unity or debugging skills. | 3 / 3 |
Total | 12 / 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 strong migration skill with excellent actionability - the before/after code examples are complete and immediately usable. The workflow is clear with proper verification steps. Main weakness is the length and some redundancy in the pattern explanations; the content could be more concise and better split across files for progressive disclosure.
Suggestions
Consider extracting the detailed migration patterns (IMGUI, Logger, Cheat System, Performance HUD) into a separate PATTERNS.md file, keeping only a summary table with links in the main skill
Remove redundant explanations that appear in multiple patterns (e.g., 'No RegisterObject needed since everything is static' appears implicitly multiple times)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some redundancy - the migration patterns repeat similar information (e.g., explaining RegisterObject/static methods multiple times), and some explanatory text could be tightened. The decision guide table is well-structured but the patterns section has overlapping content. | 2 / 3 |
Actionability | Excellent actionability with complete, executable before/after code examples for each migration pattern. The code is copy-paste ready with proper imports, and covers multiple scenarios (static vs instance methods, parameterized commands, dynamic registration). | 3 / 3 |
Workflow Clarity | Clear 6-step migration workflow with explicit verification checkpoints. The incremental migration section provides a safe step-by-step approach, and the verification section at the end gives concrete validation steps (Enter Play Mode → press ~ → confirm commands appear). | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections and tables, but it's a long monolithic file (~200 lines of patterns) that could benefit from splitting detailed patterns into separate files. The reference to jahro-troubleshooting skill at the end is good, but the main content could be better structured with overview + linked 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.