Conciseness

The body avoids concept-tutoring but carries clear redundancy: "The rule" restates the opening blockquote, the "Defaults: NO cover, NO TOC" section repeats inline script comments, and the "Contract"/"Output Format" sections admit they exist only "for the conformance test". Time-sensitive version text ("for v0.25.1 gstack is a soft prereq") also pads without a deprecated-section frame. This matches anchor 3 — mostly efficient but includes unnecessary material that could be tightened — rather than 4, where only minor trimming would be needed.

Actionability

The invocation script is executable end-to-end (binary check, gbrain get, dual-source raw fetch, awk frontmatter strip, guarded render) and "Common patterns" gives concrete flag examples. Two gaps keep it from 5: emoji sanitization is claimed ("Skipping emoji sanitization... show up as boxes") but no command or step implements it, and the first common pattern `brain-pdf <slug>` is a pseudo-command with no defined entry point.

Workflow Clarity

The RESOLVE → STRIP → RENDER → DELIVER sequence is mirrored by a fully commented script with explicit validation guards (`[ -x "$P" ]`, `gbrain get` existence check, `[ -s "$CLEAN" ]` empty-output check), and "When it fails" provides error-specific recovery (resolve the real slug after a title search; install gstack rather than hand-rolling a PDF). This matches anchor 5's explicit validation plus feedback loops; the operation is non-destructive, so no batch cap applies.

Progressive Disclosure

A single well-sectioned file for a single-purpose skill, with external conventions (quality.md, agent-operator-protocol.md) and related skills linked one level deep and clearly signaled — no bundle files exist to split into. It falls short of anchor 5 because at ~180 lines the boilerplate "Contract" and "Output Format" sections and duplicated rule/defaults text are organization gaps; the under-50-line simple-skill exception does not apply.

Specificity

The description lists four concrete actions — "Generate a publication-quality PDF from any brain page via the gstack make-pdf binary", "Strips YAML frontmatter, sanitizes emoji, applies running headers and page numbers" — which comprehensively covers the skill's purpose with no gaps. It is not a 4 because there is no meaningful missing action within the skill's stated scope.

Completeness

The "what" is clear and multi-action, but the description contains no "Use when..." clause or equivalent explicit trigger guidance — usage is only weakly implied by "from any brain page". Per the judging guideline, a missing use-when clause caps completeness at 3; the description matches anchor 3 exactly.

Trigger Term Quality

Natural keywords "PDF" and "brain page" appear and users would plausibly say them, but common variations like "convert", "export", and the ".pdf" extension are absent from the description itself (they exist only in the separate triggers field, which this evaluation does not credit). It fits anchor 4 (good coverage, a few natural terms missing) rather than 5, which requires synonyms and file extensions in the evaluated text.

Distinctiveness Conflict Risk

"PDF from any brain page via the gstack make-pdf binary" carves a clear niche with distinct tooling (gstack, gbrain), so it is unlikely to trigger for the wrong skill. Adjacent skills (e.g., HTML publishing) target different output formats, keeping conflict risk minimal — matching anchor 5.