Conciseness

The body is lean and efficient: a three-row knob table, a compact decision tree, and four short bash examples replace prose, with no explanation of concepts Claude already knows and every token earning its place.

Actionability

Fully executable, copy-paste-ready commands (e.g. `xberg extract paper.pdf --content-format markdown`, the batch-plus-jq pipeline, the metadata-only invocation) and concrete flag pairs in the decision tree cover the common cases.

Workflow Clarity

This is a simple single-decision skill and the decision tree makes the one action unambiguous (consumer → flag pair), meeting the simple-skill exception. Extraction is read-only, so the destructive/batch validation cap does not apply, and the body even flags that `maximum` token-reduction is lossy and should be verified.

Progressive Disclosure

A clear overview with detail appropriately deferred: the full flag set and configuration keys are pushed to well-signaled, one-level-deep references (`references/cli-reference.md`, `references/configuration.md`), keeping the SKILL.md body a navigable decision guide. No bundle files exist beyond the cited paths to check.

Specificity

The description names the domain ("choosing an output format for extracted documents") and one concrete action ("Maps consumer (LLM, parser, archive) to the right `--format` / `--content-format` pair"), matching the 1-2 concrete actions anchor. It is more concrete than the generic level-2 anchor but does not list several specific actions required for a 4.

Completeness

It explicitly answers both: the "what" ("Maps consumer (LLM, parser, archive) to the right `--format` / `--content-format` pair") and the "when" ("Use when choosing an output format for extracted documents") with a concrete trigger phrase, exactly matching the anchor-5 pattern.

Trigger Term Quality

Good natural keyword coverage — "output format", "plain text", "markdown", "djot", "HTML", "JSON", "DocTags", "LLM", "parser", "archive" — terms a user would naturally say. A few natural variations (e.g. "which format", "convert to markdown") are missing, so it falls short of the comprehensive-synonym anchor at 5.

Distinctiveness Conflict Risk

A clear niche (extraction output-format selection tied to specific CLI flags) makes it mostly distinct with only minor overlap risk against generic format-conversion or markdown-rendering skills, fitting the anchor-4 example rather than the minimal-conflict anchor 5.