Conciseness

The prose is terse and imperative throughout ("Write numbered steps. Each step has a done-when."), but the closing MUST/MUST NOT block (lines 88-100) repeats rules already stated in Shape and Fixed-step Skill ("Do not use em dashes" vs "MUST NOT use em dashes", "No second-person identity" vs "MUST NOT assign a second-person identity"), which violates the skill's own 'Keep each rule in one home' principle. This is 'mostly efficient but could be tightened', not 4, because the duplication is a noticeable block (~13 of 101 lines) rather than a minor trim.

Actionability

The body gives concrete paths (~/.dora/harness/<slug>/handoff.md, .env), a literal handoff.md format block, and numbered steps with checkable done-whens; as an instruction-only skill the guidance is executable. It stops short of 5 because some instructions assume external context from grilling-for-routine ('Read the grill answers. Use the gate.' never defines the gate here) and the example prompt block covers only the poll/skip/apply shape.

Workflow Clarity

The Steps section is a clear 5-step sequence where every step carries an explicit, checkable done-when, step 4 is a dedicated validation pass ("no second-person identity, no em dashes, every step has a done-when"), and step 5 defines the handoff back to grilling-for-routine. This matches 'clear sequence with explicit validation steps; checklists for complex processes'.

Progressive Disclosure

Sections are well-labeled and the skill is ~100 lines with no bundle files, but detail that its own rule says belongs 'in a later file' (the Run handoff mechanics, the handoff.md format block, the dora session/wire tooling notes in the opening) is inlined in SKILL.md. This fits 'some structure but content that should be separate is inline', not 4, since no references exist at all to offload that detail.

Specificity

The description names 1-2 concrete actions ("writing the unattended night prompt", "freezing a deterministic step into a Fixed-step Skill") but does not comprehensively cover what the skill produces (no mention of handoff.md, skip steps, or the Fixed-step Skill's helper-file rules). It sits at the 'names domain and 1-2 concrete actions' anchor, below 4 because coverage of capabilities is thin and above 2 because the actions named are genuinely concrete.

Completeness

The 'when' is explicit and strong (three distinct "Use when..." clauses), and a 'what' is present but only embedded inside the trigger clauses rather than stated as a capability summary. This fits anchor 4 ('both what and when; when could be more explicit' — here inverted: the what could be more explicit), not 5 because the what-side is partial, and not 3 because the what is more than weakly implied.

Trigger Term Quality

Keywords like "night prompt", "routine", "Fixed-step Skill", and "done-when" are relevant within this workflow, but they are internal jargon with no common variations or synonyms offered (e.g., no mention of 'unattended run', 'overnight pass', or 'prompt.md'). This matches 'some relevant keywords but missing common variations', not 4 ('good coverage, a few natural terms missing') because a user outside this ecosystem would not naturally say most of these phrases.

Distinctiveness Conflict Risk

The description carves a clear niche anchored to its companion skill ("after grilling-for-routine", "Fixed-step Skill", "done-when") that no generic writing skill would match. It fits 'clear niche with distinct triggers; minimal conflict risk'.