CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

autorag-doctor

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.

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

85%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a highly actionable, well-sequenced diagnostic workflow with excellent validation loops and executable commands throughout — no concept padding, every token carries operational specifics. The main weakness is packaging: all reference material lives inline in one long file and one cited path (docs/minsync-setup.md) is missing from the bundle.

Suggestions

Move the diagnostic-codes table and the repair-playbook detail into references/ files (e.g. references/diagnostic-codes.md, references/repair-playbook.md) and keep SKILL.md as a lean overview with well-signaled one-level-deep links.

Fix or remove the dangling reference to docs/minsync-setup.md, since no bundle file exists at that path.

Trim the embedder-history narrative (Q8_0 gateway compatibility details) to the actionable rule — rebuild or re-embed — or relocate it to a reference file.

DimensionReasoningScore

Conciseness

The body is dense with non-obvious operational detail (null-vs-[] semantics, lock ownership rules, identity-mismatch history) and never explains concepts Claude already knows, but at ~280 lines sections like the embedding-model-mismatch narrative and the long diagnostic-codes table could be trimmed or split. Not 5 because a few passages (e.g., the Q8_0 gateway history paragraph) run longer than the instruction strictly needs; not 3 because there is no padding or generic explanation.

4 / 5

Actionability

Guidance is fully executable throughout: exact triage commands ('autorag status --json', 'autorag setup --format json'), a per-datasource table of native check and re-sync commands, concrete MCP probe payloads ('autorag.search {"query":"a word that certainly appears","topK":3}'), and copy-paste repair commands including exact cargo install pins. Coverage of common failure cases is essentially complete.

5 / 5

Workflow Clarity

A clear four-phase sequence (triage core → probe datasources → prove searchability → repair playbook) with explicit validation: 'Searchable must come from an actual query in step 3, never inferred from index state', 're-run the failing check', 'Re-run autorag status --json afterwards to confirm inFlight: false', and a completion condition checklist. Destructive operations (kill orphan, delete lock, index rebuild) each carry confirm-first guards, giving strong feedback loops.

5 / 5

Progressive Disclosure

Section structure and tables are good, but the skill is a single ~280-line monolith with no bundle: reference material (the 25-row diagnostic-codes table, per-datasource repair detail, embedder history) is inlined where a references/ file would keep SKILL.md a lean overview. It also points to 'docs/minsync-setup.md', which does not exist in the bundle. Not 2 because headers and tables make it navigable; not 4 because content that should be separate is inline and one reference is dangling.

3 / 5

Total

17

/

20

Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: comprehensive third-person capability inventory paired with an explicit, symptom-driven 'Use when' clause. Trigger terms are natural and specific to the AutoRAG domain, keeping conflict risk minimal. Only slight room to broaden trigger synonyms for no-results scenarios.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions in third person ('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'), covering the full diagnose-and-repair scope comprehensively. Not the level below (4) because the action list is complete rather than having minor coverage gaps.

5 / 5

Completeness

Both questions are answered explicitly: 'what' is a full capability inventory (checks X, Y, Z; fixes orphan locks, mismatches, stale indexes, missing setup) and 'when' is a concrete 'Use when...' clause enumerating six explicit trigger scenarios. Matches the top anchor exactly; the 4 anchor applies only when the 'when' is less explicit.

5 / 5

Trigger Term Quality

Trigger phrasing is natural and symptom-oriented ('search returns nothing or too little', 'refresh hangs or fails', 'a datasource disappeared from results', 'indexes look stale', 'the embedder is unavailable', 'check, diagnose, verify, or repair AutoRAG'). Not 5 because a few common user phrasings are missing (e.g., 'no results', 'can't find my messages/notes', 'AutoRAG is broken'); not 3 because coverage is broad and symptom-led rather than partial.

4 / 5

Distinctiveness Conflict Risk

The skill occupies a clear niche — 'AutoRAG install doctor' — with tool-specific triggers (AutoRAG, MinSync, datasource CLIs) that no generic search/indexing skill would claim. Minimal overlap risk; no neighboring anchor fits better.

5 / 5

Total

19

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

Marker-Inc-Korea/AutoRAG

Path

skills/autorag-doctor/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.