jahro-logging
Reviews and improves Debug.Log usage in Unity C# projects following structured logging principles: context tags, severity contracts, boundary-based placement, and criticality tiers. Detects common antipatterns (naked Debug.Log, logging in Update, stringly-typed errors), adds missing logs at system/state/error/external boundaries, and scaffolds project-wide logging infrastructure (LogTag constants, formatting helpers, conventions). Use when the user mentions logging, Debug.Log, log messages, debugging, or asks to improve observability in Unity code.
89
88%
Does it follow best practices?
Impact
88%
1.41xAverage 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 clearly communicates specific capabilities (antipattern detection, boundary-based log placement, infrastructure scaffolding), uses natural trigger terms users would employ, and includes an explicit 'Use when...' clause. The description is well-scoped to a distinct niche (Unity C# logging) with enough detail to differentiate it from general debugging or code review skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: reviews Debug.Log usage, detects common antipatterns (with examples like naked Debug.Log, logging in Update, stringly-typed errors), adds missing logs at boundaries, and scaffolds project-wide logging infrastructure (with specific examples like LogTag constants, formatting helpers). | 3 / 3 |
Completeness | Clearly answers both 'what' (reviews/improves Debug.Log usage, detects antipatterns, adds missing logs, scaffolds infrastructure) and 'when' with an explicit 'Use when...' clause listing trigger scenarios like mentioning logging, Debug.Log, debugging, or observability in Unity code. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'logging', 'Debug.Log', 'log messages', 'debugging', 'observability', 'Unity'. Also includes domain-specific terms like 'antipatterns', 'Update', and 'C# projects' that help with precise matching. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: Unity C# Debug.Log specifically, with structured logging principles. The combination of Unity, C#, Debug.Log, and specific antipattern detection makes it very unlikely to conflict with general code review or other logging 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 highly actionable and well-structured skill with excellent executable code examples and clear multi-step workflows. Its main weakness is verbosity — the content is roughly 2-3x longer than necessary due to repeated information across sections (severity mapping appears three times, format template is restated multiple times) and sections that could be split into reference files. The Jahro integration section is well-handled as optional, and the antipattern detection table is a strong practical reference.
Suggestions
Deduplicate repeated content: the severity contract, format template, and conventions appear in multiple sections. Define once in Passive Rules and reference from workflows instead of restating.
Split the detailed antipatterns table, Log helper class, and game-specific logging domains into separate reference files (e.g., ANTIPATTERNS.md, LOG_HELPER.md) and link from the main skill to reduce token footprint.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but overly long (~300+ lines). Several sections repeat information (severity contract appears in passive rules, log format reference, AND conventions summary). The antipatterns table duplicates fix examples shown inline. Some explanations like 'The em dash separates the human-readable action from machine-parseable key-value data' are unnecessary for Claude. However, it avoids explaining basic concepts like what Unity is or how Debug.Log works. | 2 / 3 |
Actionability | Excellent actionability throughout. Every rule includes concrete, executable C# code examples. The LogTag constants class and Log helper are complete, copy-paste ready implementations. Antipattern fixes show clear before/after code. The structured format template is specific and unambiguous. | 3 / 3 |
Workflow Clarity | Both active workflows (Review & Improve, Setup Infrastructure) have clearly numbered sequential steps with explicit verification steps at the end. The review workflow includes a logical progression: ask setup → scan antipatterns → classify tier → identify gaps → generate code → verify. Each step has clear instructions and example prompts. | 3 / 3 |
Progressive Disclosure | The skill is entirely self-contained in one large file with no references to external detail files. The cross-references to other skills (jahro-commands, jahro-watcher, etc.) are good, but the main content could benefit from splitting the detailed antipatterns table, the full Log helper class, and the game-specific logging domains into separate reference files. The inline conventions summary in the Setup workflow duplicates the passive rules section. | 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.