CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

autorag

Search, summarize, compare, and answer questions from an already configured AutoRAG librarian over local documents and configured datasources. Use when the user asks AutoRAG to search PDFs, wikis, notes, or a knowledge base. Use autorag-setup for install, model, roots, indexing, or datasource changes.

Quality

88%

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

78%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.

The body is a dense, highly actionable operator manual: every command is copy-paste ready and workflows include diagnostics and safety rails. Its main weaknesses are inline reference-grade detail (automations schema, filee/dupey configuration) that belongs in separate bundle files, and a dangling reference to a docs/minsync-setup.md that is not present in the bundle.

Suggestions

Move the automations file schema, agent-profile semantics, and loop-guard details (the '## Maintenance' middle section) into a reference file such as references/automations.md, and the filee conversion configuration and dupey comparison semantics into references/conversions.md, keeping short summaries with clearly signaled links in SKILL.md.

Fix or clarify the 'docs/minsync-setup.md#embedding-backends' reference: either ship that file inside the skill bundle under a clearly signaled path, or point to the autorag product documentation location explicitly so the link is not dangling.

Tighten the configuration-knob prose (binaryPath/autoInstall/enabled/timeoutMs/dataDir) into a compact table or move it to the proposed conversions reference, which would also improve conciseness.

DimensionReasoningScore

Conciseness

Efficient and product-specific throughout — commands, flags, and config keys with no tutoring of concepts Claude already knows ('Do not bypass the librarian with ad hoc raw search when the user requested AutoRAG'). Not 5: the filee/dupey configuration-knob prose ('filee.binaryPath', 'autoInstall', 'timeoutMs', 'dataDir', dupey compare thresholds) and the citation-numbering semantics paragraph are dense prose that could be trimmed or relocated; not 3: padding is minor, not several unnecessary explanations.

4 / 5

Actionability

Fully executable, copy-paste-ready commands cover the common cases: 'autorag search "what were the key findings in the Q3 report" --top-k 5 --json --debug', 'autorag evidence <sessionId> --result 1 --json', the full Maintenance command block, and a concrete automations.json example with a realistic rule.

5 / 5

Workflow Clarity

Clear Preflight → Search → Maintenance sequencing with most checkpoints present: health/duplicates/status preflight, 'citation-without-result' diagnostics, dupey-compare verification of conversions, and automation loop guards with run caps. Not 5: sequences are prose-embedded rather than explicit step/checkpoint lists, and destructive-adjacent operations (index reset/rebuild) rely on prose cautions ('Never target source documents') rather than an explicit validation step.

4 / 5

Progressive Disclosure

Headers and subsections give real structure, but roughly a hundred lines of automations schema, filee configuration, and duplicate policy detail are inlined where a reference file belongs, and the single reference — 'See docs/minsync-setup.md#embedding-backends' — points to a file that does not exist in the skill bundle. Not 4: content that should be separate is inline and the one reference is not a real, clearly signaled bundle file; not 2: the sectioning is genuinely navigable.

3 / 5

Total

16

/

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.

The description is concise and complete: concrete verbs for the 'what', an explicit 'Use when' clause with natural trigger terms, and a clean boundary against the autorag-setup sibling skill. Only weakness is slightly incomplete synonym coverage in its trigger terms.

DimensionReasoningScore

Specificity

Lists four concrete actions — 'Search, summarize, compare, and answer questions' — against a concrete object ('local documents and configured datasources'), matching the comprehensive multi-action anchor. Not 4: coverage of the skill's core capability is complete, with no minor gaps.

5 / 5

Completeness

Explicitly answers both: what ('Search, summarize, compare, and answer questions from an already configured AutoRAG librarian over local documents and configured datasources') and when ('Use when the user asks AutoRAG to search PDFs, wikis, notes, or a knowledge base') with concrete trigger phrases.

5 / 5

Trigger Term Quality

'Use when the user asks AutoRAG to search PDFs, wikis, notes, or a knowledge base' gives good natural keyword coverage including the plural form 'PDFs'. Not 5: common synonyms and variations such as 'documents', 'research papers', or file extensions are absent; not 3: several natural user phrasings are explicitly present.

4 / 5

Distinctiveness Conflict Risk

Clear niche (a configured AutoRAG librarian) with explicit sibling disambiguation: 'Use autorag-setup for install, model, roots, indexing, or datasource changes.' Not 4: the explicit routing leaves minimal overlap risk with other skills.

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/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.