Conciseness

The body is sectioned and lean, never explaining what a TODO is or basic concepts Claude already knows, with only minor lists (search-target variants, example next steps) that could be trimmed; it is not 5 because a few enumerated examples are slightly obvious.

Actionability

Concrete, specific guidance is given throughout — required search targets, fields to capture (file path, line, excerpt, subsystem, next step, priority), report structure, and pass criteria — which is actionable for an instruction-only skill; it is not 5 because no executable command (e.g. a grep/ripgrep invocation) is provided, leaving a minor gap.

Workflow Clarity

The five-step procedure is clearly sequenced and dedup is called out, but this batch repo-wide scan has no explicit validate→fix→retry checkpoint, so the batch-operation cap holds it at 3; the Pass Criteria section provides final verification but not the per-step feedback loop needed for 4.

Progressive Disclosure

No bundle files exist and the single-file body is well-organized into clear sections with no inlined content that belongs elsewhere; it is not 5 because the skill exceeds ~50 lines and lacks any one-level-deep reference signaling, so the simple-skill 5 exception does not fully apply.

Specificity

Quotes "Search the entire codebase for TODO markers" and "create a markdown document with proposed next steps for each" name the domain plus two concrete actions, matching the anchor for 1-2 concrete actions without being comprehensive; it does not reach 4 because only two actions are listed and nothing about dedup/categorization is surfaced.

Completeness

The description gives a clear "what" (search for TODO markers and produce a markdown report) but no "Use when..." trigger clause, so per the missing-trigger-guidance cap it stays at 3; it is not 2 because the "what" is concrete, and not 4 because "when" is entirely absent rather than weakly implied.

Trigger Term Quality

"TODO markers", "codebase", "markdown document", and "next steps" are relevant keywords, but common user phrasings like "TODO comments", "FIXME", "backlog", or "technical debt" are absent, leaving synonyms and variations missing as at anchor 3; it is above 2 because multiple relevant terms appear.

Distinctiveness Conflict Risk

Auditing inline TODO markers into a planning markdown report is a fairly distinct niche with low overlap risk, fitting "mostly distinct; minor overlap risk"; it is not 5 because the phrasing is generic enough to brush against general code-search skills.