Conciseness

The body is lean and efficient throughout — terse bullet fragments, imperative guidance, one shell command, and zero explanation of concepts Claude already knows (e.g., what a lexer is). Every token earns its place, matching the 5 anchor.

Actionability

Concrete, executable guidance dominates: `just gen-grammar <lang>`, the `expect`/`eat`/`.ok()`/`.or_add_diagnostic(...)` API choices, `quick_test`, `ok/` and `error/` fixture directories, and `&str` lexer tests. It stops short of the 5 anchor because no complete example snippet (e.g., a parse-rule or recovery call) is shown — the guidance is specific naming, not copy-paste code.

Workflow Clarity

The 6-step workflow is clearly sequenced and test-first ("Add or adjust focused ok/ and error/ fixtures before changing recovery behavior") with an end-of-loop validation step ("Run the language parser's focused tests and inspect snapshots") plus a dedicated Review Checklist. The 5 anchor's explicit fix-and-re-run feedback loop after a failing test is only implicit, keeping this at 4.

Progressive Disclosure

The body is a clear overview that delegates depth to the canonical repo guide ("Use crates/biome_parser/CONTRIBUTING.md as the canonical parser guide") and one-level-deep, clearly labeled references (References section, `xtask/codegen/*.ungram`, parser crate paths). Sections are well-organized with no nested or buried references, matching the 5 anchor's clear-overview, well-signaled structure.

Specificity

The description enumerates concrete capabilities (".ungram grammars, lexers, token sources, parse rules, separated lists, error recovery, and parser fixtures") with comprehensive domain coverage, but relies on a single uniform verb pair ("implementing or modifying") plus an inclusion list rather than the multiple distinct concrete actions of the 5 anchor.

Completeness

It explicitly answers both what ("implementing or modifying Biome parser behavior, including .ungram grammars, lexers, token sources, parse rules, separated lists, error recovery, and parser fixtures") and when ("Use this skill when…"), with a concrete negative boundary ("Do not use merely for consuming an existing AST/CST"). This matches the 5 anchor's explicit what-and-when with concrete trigger phrases.

Trigger Term Quality

Good natural keyword coverage — "parser", "grammar", "lexer", "error recovery", "fixtures", and the ".ungram" extension — that a Biome contributor would actually say. A few natural synonyms ("syntax tree", "diagnostics", "parse errors") are missing, so it falls short of the comprehensive-synonym 5 anchor.

Distinctiveness Conflict Risk

A clear niche (Biome parser internals) with distinct technical triggers and an explicit exclusion clause for mere AST/CST consumption, minimizing overlap with generic parser or code skills.