Conciseness

No space is wasted explaining concepts Claude already knows — it goes straight to setup and command examples. However, content is duplicated: every command appears both as a bash example and again as a row in the "Operations Reference" table, and the env vars in the Setup section are restated in the "Environment Variables" table. This fits the 4 anchor ("efficient; minor instances... that could be trimmed") rather than 3, since the redundancy is deliberate cross-referencing, not padded explanation.

Actionability

Every one of the nine commands has a copy-paste-ready bash invocation with variants (e.g., `python3 scripts/outline.py read <document-id> --json`), and the commands verified against the actual argparse surface of scripts/outline.py. Minor gaps: Setup step 1 says `cp .env.example .env` and Requirements says `pip install -r requirements.txt`, but neither requirements.txt nor .env.example ships in the bundle, so those instructions fail as written. This is the 4 anchor ("mostly executable... minor gaps"), not 5.

Workflow Clarity

The Workflow section gives a clear sequence (auth-info → list-collections → search/list-documents → read → create/update) with one up-front validation checkpoint ("Run `auth-info` to verify connection"). But the write steps — `update --text` overwrites document content and `update --publish`/`--unpublish` change document state — have no post-write verification (e.g., re-reading the document to confirm the change). Per the rubric's cap for mutating operations without validation, this sits at the 3 anchor ("sequence present but checkpoints missing or implicit"), not 4.

Progressive Disclosure

The body is well-sectioned (Requirements, Setup, Usage, JSON Output, Operations Reference, Environment Variables, Troubleshooting, Exit Codes, Workflow) and its only bundle reference, `scripts/outline.py`, is a real file — no dead or nested references. At ~140 lines it inlines the complete CLI reference where a small operations reference file could carry the tables, keeping it at the 4 anchor ("good structure; most content appropriately placed; minor organization gaps") rather than 5.

Specificity

"Search, read, and manage Outline wiki documents" plus the enumerated list — "(1) searching wiki for documentation, (2) reading wiki pages or articles, (3) listing wiki collections or documents, (4) creating or updating wiki content, (5) exporting documents as markdown" — names multiple concrete actions (search, read, list, create, update, export-as-markdown) with comprehensive coverage of the tool's surface. Fits the 5 anchor ("multiple specific concrete actions; comprehensive coverage") rather than 4, since no meaningful capability is left unnamed.

Completeness

Both halves are explicit: the "what" opens the description ("Search, read, and manage Outline wiki documents") and the "when" is a concrete enumerated "Use when: (1)...(5)" clause. This matches the 5 anchor ("clearly and explicitly answers both what AND when with concrete trigger phrases") and exceeds the 4 anchor, where the "when" is present but less specific.

Trigger Term Quality

Natural user phrasings are present: "searching wiki for documentation", "reading wiki pages or articles", "wiki collections", "creating or updating wiki content", "exporting documents as markdown". A few natural synonyms are missing — e.g., "knowledge base" or "Outline docs" — so it sits between the 4 anchor ("good keyword coverage; a few natural terms missing") and the 5 anchor, landing at 4.

Distinctiveness Conflict Risk

The product is named consistently ("Outline wiki", "Outline wiki instance") and the triggers are Outline-specific ("wiki collections", "exporting documents as markdown", "self-hosted or cloud"), giving it a clear niche with minimal overlap against generic document or web-reading skills. Not 4, since even closely related skills (generic doc tools) would rarely claim these triggers.