Content
88%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A highly actionable, well-sequenced debugging guide with copy-paste commands, a validated status-first workflow, and genuinely non-obvious domain knowledge (UTC filename dates, profile resolution, UC_LOG_DIR escape hatch). The only deductions are minor: a few trimmable passages, a stray unclosed ```text fence at the end of the file, and no progressive-disclosure split despite ~200 lines of inline reference material.
Suggestions
Remove the stray unclosed ```text code fence at the very end of the body (after the 'Things to avoid' list) — it is a formatting artifact that may render trailing content as code.
Consider moving the jq cookbook and subsystem target/span cheat-sheet into a one-level-deep references file (e.g. references/query-cookbook.md) to keep SKILL.md a lean overview while preserving the detail on demand.
Trim the opening paragraph, which largely restates the frontmatter description, and tighten the pre-split-layout warning to its load-bearing fact (old single-file path is wrong for this skill).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and assumes competence (no explaining what JSONL or tracing is; aphorisms like "logs are observability, not state" carry real guidance), but there are minor instances that could be trimmed: the opening paragraph restates the frontmatter description, and the pre-split-layout warning paragraph runs long. This sits between the 4 anchor ('efficient, minor over-explanation') and the 5 anchor ('every token earns its place'), noticeably above the midpoint. | 4 / 5 |
Actionability | Fully executable throughout: exact invocation path (`.agents/skills/local-log-debug/uc-logs.sh <command>`), a command table with defaults (`--lines N` default 50, `--profile` default `dev`), copy-paste jq filters, and real target/span strings seeded from actual logs. Covers the common cases (status, grep, query, merge) exactly as the top anchor requires. | 5 / 5 |
Workflow Clarity | The 'Recommended workflow' is a clearly sequenced 5-step process with explicit validation checkpoints: run `status` first, judge per-role freshness, and "stop and confirm the profile before drawing conclusions. Don't silently analyze stale logs" — a real error-recovery feedback loop. The read-only nature of the task means the destructive/batch cap does not apply. | 5 / 5 |
Progressive Disclosure | Well-organized single-file structure with clear section headers, decision tables, and a script as the single entry point — but everything is inline in one ~200-line file, including reference-grade material (the jq cookbook and the subsystem cheat-sheet) that could live in a one-level-deep reference file. This matches the 4 anchor ('good structure, most content appropriately placed, minor organization gaps') rather than the 5 anchor's explicit split into referenced files; it is well above the 3 anchor since nothing is buried or nested. | 4 / 5 |
Total | 18 / 20 Passed |