Conciseness

The body is lean and operational throughout — when-to-use, output layout, API, CLI, backend table, install, and common mistakes — with no explanation of concepts Claude already knows and compact load-bearing phrases like 'works offline, portable across machines, no broken refs'. Anchor 5 ('every token earns its place') fits; anchor 4 would require identifiable trimming opportunities, and none of substance exist.

Actionability

The archive() example is fully executable with a real URL, argument defaults, and result attributes, and the CLI block includes flags and exit codes. Minor gaps keep it at anchor 4 rather than 5: 'lookup(url="https://x.com/...")' uses an elided URL and the install command contains a '<path-to>' placeholder.

Workflow Clarity

This is a single-task skill with an unambiguous action (archive(url=...) or 'web-archive archive --url'), and the simple-skill exception applies. Feedback is still covered via .status/.fresh semantics, exit codes, and the 'fresh=False is a cache hit, check status' mistake entry; no destructive or batch operations exist that would cap the score.

Progressive Disclosure

A well-sectioned overview with exactly one clearly-signaled one-level reference ('See __docs/output-contract.md for the full contract — embedded-metadata format, SQLite schema, slugify rules, determinism semantics'). Anchor 4 rather than 5 because the referenced file is not part of the skill bundle (no __docs/ directory exists alongside it), so the pointer cannot be verified, and the body exceeds the under-50-lines simple case.

Specificity

Phrases like 'capturing a URL as a durable self-contained HTML', 'preserving a tweet/reddit post/article before it gets taken down', and 'claim verification against frozen content' are concrete with no vague language, but coverage has minor gaps (lookup, the SQLite index, and offline portability are unstated). Matches anchor 4 ('several specific actions; minor gaps') rather than 3, since it goes beyond 1-2 generic actions, and not 5 because the capability list is not comprehensive.

Completeness

Explicitly answers both: what ('capturing a URL as a durable self-contained HTML') and when (an explicit 'Use when...' clause listing concrete triggers: vault-ingest URL inputs, pre-takedown preservation, claim verification, 'save this page'). This matches anchor 5 exactly; it exceeds anchor 4 because the when-clause is explicit and trigger-specific rather than merely present.

Trigger Term Quality

Natural user phrases are present — 'save this page so it survives a future site change', 'preserving a tweet... before it gets taken down', 'capturing' — but common synonyms users say ('archive', 'snapshot', 'back up this link') appear only in the body, not the description. Good keyword coverage with a few natural terms missing fits anchor 4, short of anchor 5's comprehensive synonym coverage.

Distinctiveness Conflict Risk

A clear niche (durable offline HTML archival) with distinct triggers such as 'vault-ingest URL inputs' and 'claim verification against frozen content'. Scored 4 rather than 5 because the broad 'save this page' phrasing carries minor overlap risk with generic page-download or web-scraping skills.