Conciseness

Mostly efficient operational detail Claude cannot know (commands, frontmatter specs, gate criteria), but padded in places — e.g. 'The memory surface is only as good as what gets written into it. This is the step that keeps it alive — without it the profile stays empty and the session recap has nothing to inject' is motivational fluff, and several rationale passages could be tightened.

Actionability

Concrete copy-paste-ready commands with flags ('obsidian-wiki memory profile set <key> "<value>" --confidence 0.85', 'sync CAPTURE type=<type> page="<path>"', '${QMD_CLI:-qmd} update'), exact paths, slug examples, and confidence calibration. Minor gaps keep it from 5: correction mode's 'update an existing derived page when one owns the claim' lacks a concrete lookup procedure, and '<obsidian-wiki memory now>' is an unexplained placeholder.

Workflow Clarity

Three modes cleanly separated with sequenced steps, an explicit KEEP/SKIP gate, a mandatory sha256 pre/post verification loop in correction mode, and QMD failure recovery ('do not roll back the vault changes; report the QMD status separately'). Falls short of 5 because quick mode says 'Stop here; do not run the full-mode steps below' while Step 5b instructs 'In quick mode, do this step but skip Step 6' — an internal contradiction — and the unnumbered 'Before You Start' / 'Step 5b' disrupt the sequence.

Progressive Disclosure

The raw-file spec is properly offloaded to a real, one-level-deep, clearly signaled reference ('Read references/RAW-FORMAT.md for the full frontmatter spec'), which exists in the bundle. However, the body leans on three separate sections of an external llm-wiki/SKILL.md plus .skills/llm-wiki/references/MEMORY.md, and inlines the large correction-mode YAML schema and four full body templates that could live in reference files.

Specificity

Names the domain and two concrete actions ('Turn the current conversation or finding into a structured permanent wiki note', 'QUICK MODE writes a fast _raw/ note') but omits correction mode, classification, and index updating, so coverage is not comprehensive.

Completeness

Explicitly answers both what ('Turn the current conversation or finding into a structured permanent wiki note') and when ('Use for save/capture/preserve requests'), but the 'when' is terse and does not distinguish when quick mode vs. full mode applies, keeping it short of the level-5 anchor.

Trigger Term Quality

'Use for save/capture/preserve requests' plus a concrete invocation example ('@research save this') gives good natural keyword coverage, but misses common variations like 'remember this', 'note this down', or 'log this'.

Distinctiveness Conflict Risk

Clear niche (conversation-to-wiki capture) with an explicit boundary — 'This captures current discussion, not external source ingestion' — that disambiguates it from the closely related ingestion skill, matching the clear-niche anchor with minimal conflict risk.