Conciseness

Efficient and dense — nearly every sentence is an AutoRAG-specific operational fact Claude could not know, with commands, paths, and diagnostic codes rather than concept explanations. Not 5: a few rules are wordy, and 'jikji-unavailable', 'embedder-unavailable', and 'datasource-auth-error' are each explained twice (once in the repair playbook, again in the diagnostic codes table), which could be consolidated.

Actionability

Fully executable throughout: a per-datasource table of exact native-check and re-sync commands, copy-paste refresh/rebuild/retry commands, concrete MCP invocations with arguments ('autorag.search {"query":...,"topK":3}', 'autorag.evidence {"sessionId":...}'), and a worked SQL cross-check example. Specific examples cover the common failure cases.

Workflow Clarity

A clear triage → probe → prove-searchability → repair → report sequence with explicit validation checkpoints: repairs must be re-verified by re-running the failing check, 'Re-run autorag status --json afterwards to confirm inFlight: false', never kill a running sync, and a completion condition gates the run on real query hits. The destructive operations (kills, lock deletion, index reset) all carry confirm-first validation, so the destructive/batch cap does not apply.

Progressive Disclosure

Well-sectioned single file with no nested references and clear navigation (triage, per-datasource table, repair playbook, codes table, report). Not 5: the ~280-line body keeps the full diagnostic-codes table and repair playbook inline where well-signaled one-level references could carry them, and the lone external pointer 'docs/minsync-setup.md' is not part of the bundle. Not 3: structure is good and inline placement is defensible for a repair run that needs the codes at hand.

Specificity

Lists multiple concrete actions — 'Diagnose and repair', 'Checks AutoRAG, MinSync, Jikji, the embedding backend, and every CLI-backed datasource', 'fixes orphan locks, orphan processes, embedding dimension or identity mismatches, stale indexes, and missing setup' — with comprehensive coverage of both components and failure modes. It exceeds the 'minor gaps' bar for 4 because the enumerated fixes map one-to-one to the skill's repair scope.

Completeness

Explicitly answers 'what' (diagnose and repair an AutoRAG install, checking named components and fixing named failure classes) and 'when' via a concrete 'Use when...' clause enumerating six trigger scenarios. This matches the 5 anchor example's structure of full what + explicit trigger phrases.

Trigger Term Quality

Natural user phrases are comprehensively covered: 'search returns nothing or too little', 'refresh hangs or fails', 'a datasource disappeared from results', 'indexes look stale', 'the embedder is unavailable', plus the synonym set 'check, diagnose, verify, or repair'. No common variation users would say when facing a broken AutoRAG install is missing.

Distinctiveness Conflict Risk

The entire description is anchored on AutoRAG and its specific backing CLIs (MinSync, Jikji, lazykatok, discrawl, etc.), a clear niche with distinct triggers; it would not plausibly fire for a non-AutoRAG skill.