
Autorag Doctor
Diagnose and repair a broken or half-working AutoRAG install so every configured source...
Install
npx skills add Marker-Inc-Korea/AutoRAG --skill autorag-doctor -g -a claude-code -y- Repository
- Marker-Inc-Korea/AutoRAG5.3k
- Category
- AI and agents
- Updated
- 3d ago
- License
- Apache-2.0
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- No, instructions only
What it does
Diagnose and repair a broken or half-working AutoRAG install so every configured source is both indexed and searchable. Checks AutoRAG, MinSync, Jikji, the embedding backend, and every CLI-backed datasource (lazykatok, discrawl, slacrawl, wacrawl, telecrawl, notcrawl, mailcrawl), then fixes orphan locks, orphan processes, embedding dimension or identity mismatches, stale indexes, and missing setup. Use when search returns nothing or too little, refresh hangs or fails, a datasource disappeared from results, indexes look stale, the embedder is unavailable, or the user asks to check, diagnose, verify, or repair AutoRAG.
AutoRAG doctor
Goal: every configured datasource is indexed and actually returns
hits. A green status is not enough, the run is done only when a real query
returns a real hit per datasource, or the datasource is reported as genuinely
empty or not configured.
Always finish with the status table in Report.
Safety
- Diagnosis and repair never delete, move, or edit source documents; a doctor run changes only AutoRAG-owned state.
- Never delete a datasource's native store (
~/Library/Application Support/katok,~/.discrawl,~/.mailcrawl, Telegram/WhatsApp/Notion archives). AutoRAG only reads them; rebuilding them is the owning CLI's job. - Only AutoRAG-owned state under
AUTORAG_HOMEand the workspace.autoragdirectory may be reset. - Never print token or password values. Report credential names only.
- Kill a process only after confirming it is an AutoRAG-owned orphan.
1. Triage the core
autorag status --json
autorag health --json
autorag setup --format json
statusreportsstate,stale,diagnostics, and per-component state forminsync,jikji, anddatasources.stale: trueor anystale-indexdiagnostic means the corpus changed since the last successful refresh.healthresolves the single search model and does one live completion probe.--skip-probesonly proves config shape, never live access; do not claim a healthy model from it.setup --format jsonreportsembedding.backend(remote,daemon, orin-process) and the resolvedprovider/model/dimensionwhen a backend is alive, orembedding.reasonand aremediationwhen none is. It only probes; it never starts a daemon. Semantic search needs the daemon (or a remote endpoint) to be running: a backend that is absent is a realembedding-unavailablestate, not normal.

