Conciseness

Mostly efficient — the Locations, Layout, CLI surface, and Quality bar sections are tight and earn their tokens — but the "Auto-research opt-in" section spends ~10 lines on a feature that "Phase 3.3.0 ships builder + query only. Loop arrives in 3.3.1", i.e. time-sensitive version-anchored content about a capability that does not exist yet, which the guidelines penalize. Not 4 because that speculative block plus the version numbers are clear padding; not 2 because the rest of the body is lean with no explanations of concepts Claude already knows.

Actionability

The CLI surface gives fully executable commands ("node $SKILL_ROOT/scripts/wiki-cli.js init <slug> --title 'X' --flavor research [--scope project]"), the layout tree is concrete, and the workflow references real operations. Not 5 because "See `templates/`" points at a directory that does not exist in the bundle (init_wiki.sh copies from $skill_dir/templates, so `init` cannot actually run as bundled), and compile-page guidance is deferred to prompt files that are also only in the missing templates/. Not 3 because the commands that are present are copy-paste ready.

Workflow Clarity

The "Workflow when invoked" section gives a clear 6-step sequence (resolve action → read wiki.config.md → cite sources.md rows → call wiki-cli.js page to sync FTS → append maintenance-log entry → update index.md), with the FTS re-index acting as a sync checkpoint. Not 5 because there is no validation or error-recovery step (e.g., what to do when a citation is missing or the CLI write fails) for what is a batch-write operation; not 3 because the sequence is explicit, ordered, and each step names its artifact.

Progressive Disclosure

Scored against the actual bundle: the body references `scripts/wiki-cli.js` and `init_wiki.sh` (both real), but "See `templates/` for wiki.config.md, index.md, prompt files" is a dangling reference — no templates/ directory exists in the bundle — and `references/wiki-flavors.md` (109 lines of per-flavor layouts) is never linked from the body at all, so the reference is buried and the inline Flavors table partially duplicates its role. Not 4 because one reference is broken and one bundle file is undiscoverable; not 2 because the body itself is well-sectioned and short with most content appropriately placed.

Specificity

Quotes concrete actions and mechanisms — "Start, structure, and grow a persistent research wiki", "folder of markdown pages with provenance", "shadow FTS5 index so any session can recall it" — but stops short of comprehensive coverage (page compiling, source ingestion, and querying are absent from the description). Not 5 because several real capabilities are left unnamed; not 3 because it goes well beyond 1-2 actions by naming the storage format, provenance model, and indexing mechanism.

Completeness

Both questions are explicitly answered: what ("Start, structure, and grow a persistent research wiki indexed in pro-workflow's SQLite knowledge base... shadow FTS5 index") and when ("Use when the user says 'start a wiki', 'add to wiki', 'compile a page', 'wiki on X'...") with concrete trigger phrases. Matches the score-5 anchor exactly; the 'Use when' clause is explicit, so the completeness cap of 3 does not apply.

Trigger Term Quality

Natural trigger phrases are quoted directly — "start a wiki", "add to wiki", "compile a page", "wiki on X", "long-lived knowledge base on a topic, paper, product, person, project, or codebase" — the phrasing a user would actually say. Not 5 because common variations like "notes on X", "remember this topic", or "second brain" are missing; well above 3 since multiple natural phrasings plus a topic-type list are present.

Distinctiveness Conflict Risk

The wiki/FTS5/knowledge-base niche is mostly distinct with dedicated triggers ("start a wiki", "compile a page") that few other skills would claim. Not 5 because "long-lived knowledge base on a topic, paper, product, person, project, or codebase" is broad enough to overlap with generic research or note-taking skills; not 3 because the wiki-specific triggers make mis-triggering unlikely.