Conciseness

The body is dense and assumes Claude's competence — it never explains what Jest, skip pragmas, or test fixtures are; every section carries non-obvious repo knowledge ('lazy conditions read the resolved config, never `process.env`', 'a pragma on a skipped test errors as ambiguous'). It is not a 5 because of repetition: the off-state cost calculus appears in directive item 3 and again nearly verbatim in 'Is the off-state run worth its cost?', and the working example 'test/e2e/app-dir/use-offline/' is cited three times. It is not a 3 because there is no padding and no explanation of concepts Claude already knows.

Actionability

Guidance is fully executable: a concrete next.config.js axis-keying example, the pragma form '// @gate concurrentRouterQueue', copy-paste verification commands with env vars ('NEXT_SKIP_ISOLATE=1 pnpm test-start-webpack test/e2e/app-dir/<suite>/<suite>.test.ts', '__NEXT_TEST_AXIS=A …', 'pnpm test-unit test/unit/gate/'), and named working examples to copy from. Specific examples cover the common cases (behavior flag, new API, impossible-to-run), matching the anchor for copy-paste-ready commands.

Workflow Clarity

The decision workflow is clearly sequenced by question type (items 1–5 under 'Choosing the directive'), and the verification section provides explicit validation checkpoints with expected outcomes per state ('expect normal passes, no warnings', 'expect `⚠ gated test failed as expected (@gate …)`', 'expect `○ skipped` at collection, no fixture boot') plus a unit-test command. The Pitfalls section supplies error-recovery guidance (hard errors, cascade failures, stalling bodies). This matches the anchor for clear sequence with explicit validation steps and feedback for recovery.

Progressive Disclosure

A single clearly-signaled, one-level-deep reference leads the document ('Full reference: test/lib/gate/README.md') and sections are well-organized with headers and a scannable anti-pattern table. It is not a 5 because the skill keeps all ~180 lines inline with no bundle files — the Pitfalls section and the detailed test-axis pattern are reference-grade material that could be split out; it is not a 3 because the one reference that does exist is prominently signaled and nothing is buried.

Specificity

The description lists multiple concrete actions — 'How to use the `@gate` / `@force-gate` test directives instead of `it.skip`', 'converting `if (isNextDev) return` guards', 'adding a condition to test/lib/gate/conditions.ts', 'keying a fixture's experimental flag on a __NEXT_TEST_AXIS letter' — plus an explicit coverage list ('directive choice, condition tiers, the test-axis fixture pattern, pitfalls, and verification commands'). This matches the anchor for multiple specific concrete actions with comprehensive coverage; a 4 would require minor gaps, but every core capability of the skill is named.

Completeness

The 'what' is explicit up front ('How to use the `@gate` / `@force-gate` test directives instead of `it.skip` or fake-green skip patterns') and the 'when' is explicit with four concrete trigger clauses ('Use when a test is known-failing under some test-matrix dimension…, when converting…, when adding a condition…, or when keying a fixture's experimental flag…'). This clearly matches the anchor for explicitly answering both what and when with concrete trigger phrases; a 4 would require a less specific 'when'.

Trigger Term Quality

Natural trigger terms are comprehensive and include synonyms: 'it.skip', 'fake-green skip patterns', 'known-failing', 'describe.skip', 'dev mode', 'a bundler', 'experimental flag like cacheComponents', plus exact file/env tokens ('test/lib/gate/conditions.ts', '__NEXT_TEST_AXIS'). These are precisely the phrases a contributor in this repo would say when they need the skill, matching the anchor for comprehensive coverage including synonyms and specific identifiers.

Distinctiveness Conflict Risk

The niche is unambiguous: repo-specific tokens ('test/lib/gate/conditions.ts', '__NEXT_TEST_AXIS', '`if (isNextDev) return` guards', 'cacheComponents') pin the skill to this codebase's test-gating system, and the directive names '@gate' / '@force-gate' are unique triggers. Minimal conflict risk with any other skill; it would not fire for a wrong skill.