Lean and efficient with no concept explanation or padding — 'Thin wrapper over the shared engine in orch-pipeline' and tightly scoped sections; every line earns its place, matching the score-3 lean anchor rather than the score-2 'could be tightened'.

Concrete, specific guidance for an instruction-only skill: phase mask '0 → 1 → 2 → 4 → 5 → 6 (skip 3 Scaffold)', 'write new failing tests … then implement to green', and 'Add security-reviewer if the feature touches a security trigger'; per the code-vs-instruction scoring note, absence of code is not penalized when guidance is this actionable, so it is not score-2.

Clear sequence with explicit validation checkpoints — 'Stop at Gate 1 (plan approval) and Gate 2 (pre-commit)' and the size-classify-then-collapse flow — matching the score-3 anchor of explicit checkpoints and feedback gating, not score-2 whose checkpoints are only implicit.

Under 50 lines with no bundle files needed; well-organized sections (When to Use, Operation settings, How It Works, Example) and a single clearly-signaled one-level reference to ../orch-pipeline/SKILL.md, matching the simple-skill scoring note that allows a 3 with well-organized sections.

Lists multiple concrete actions — 'research, plan, TDD implementation, review, and gated commit — by delegating each phase to the matching ECC agent' — matching the score-3 anchor of several specific concrete actions rather than the single-domain score-2 example.

Explicitly answers both what ('Orchestrate building a brand-new feature end to end — research, plan, TDD implementation, review, and gated commit') and when ('Use when adding a capability that does not exist yet'), matching the score-3 anchor with an explicit trigger clause; not score-2 because the 'when' is explicit, not implied.

Natural phrasings users would say appear directly: 'building a brand-new feature', 'adding a capability that does not exist yet', giving good coverage; it is not the score-2 'some keywords but missing common variations' since both 'building a feature' and 'adding a capability' are present.

Clear niche — net-new capabilities ('does not exist yet') with distinct triggers unlikely to conflict with fix/change skills; the 'brand-new feature' framing separates it from adjacent skills, matching the score-3 clear-niche anchor.