Content
96%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.
An unusually dense, high-quality body: executable commands, concrete flag semantics with tradeoffs and failure modes, measured sizing data, and a sequenced two-tier workflow with explicit verification steps. The only structural improvement available is progressive disclosure — offloading the Swift parser-limitation catalog and full sizing tables into a reference file would keep the always-loaded overview tighter.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Nearly every line carries non-inferable operational data — measured token counts per mode, validated parser accuracy ("100% top-level symbol agreement" on 1,850 files), per-flag tradeoffs and cautions ("silently drops files whose only exports are consts"). It explains nothing Claude already knows and assumes competence, so every token earns its place rather than merely being efficient with minor trimmable spots. | 5 / 5 |
Actionability | Fully executable guidance: the exact run command `node <this-skill-dir>/map.ts <repoRoot> [flags]`, every flag concretely defined with worked examples ("--include src/channels/turn maps exactly that subtree"), sizing tables for choosing flags, and the selftest command. Copy-paste ready commands cover the common cases including Swift-only and no-TypeScript environments. | 5 / 5 |
Workflow Clarity | The Workflow guidance section sequences a clear two-tier process (dense whole-repo recon map, then exports/--members per-subsystem for the decision) with explicit validation checkpoints: "verify every dense-tier finding against typed signatures or source before acting", "spot-verify file paths and claims with grep before acting", and run selftest after editing map.ts. This matches the anchor for clear sequence with explicit validation steps; the destructive-operation cap does not apply to this read-only tool. | 5 / 5 |
Progressive Disclosure | Well-organized single-file skill with clear section headers and zero nested or buried references (none of the referenced companion files exist as bundle files in this skill's directory). It falls short of the top anchor because the body runs past the simple-skill range and inlines deep-dive material — the Swift parser edge-case catalog and eleven sizing data points — that could be offloaded to a one-level-deep reference file to keep the always-loaded SKILL.md leaner. It is above the level-3 anchor since structure and placement are otherwise appropriate. | 4 / 5 |
Total | 19 / 20 Passed |