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

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

71%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 highly actionable — every command is executable with exact flags, JSON shapes, and failure diagnostics — and the preflight/search/maintenance flow is well checkpointed. Its weaknesses are structural and editorial: ~290 lines of inlined reference-grade detail that belongs in bundled reference files, a dangling docs/minsync-setup.md pointer, and several over-long passages that could be tightened without losing information.

Suggestions

Move the calculator operations, filee/dupey conversion details, and automations.json specification into files under references/ (e.g. references/calculator.md, references/conversions.md, references/automations.md), leaving SKILL.md as a lean overview with clearly signaled one-level-deep links.

Fix or remove the dangling "docs/minsync-setup.md#embedding-backends" reference — no docs/ directory exists in the bundle — by shipping that file or pointing to an existing location.

Tighten the multi-clause passages (the search `locations` bullet, the timezone-abbreviation rules, and the evidence-field list) into shorter bullets or a table so each token earns its place.

DimensionReasoningScore

Conciseness

The body is dense and almost entirely skill-specific operational detail Claude could not know (config keys, diagnostics names, tool semantics), so it avoids the 'explains known concepts' failure, but sections like the calculator operations list, the timezone-abbreviation rules, and the multi-clause `locations` bullet run long and could be tightened, matching 'mostly efficient but includes some unnecessary explanation or could be tightened' rather than the minor-trim profile of anchor 4.

3 / 5

Actionability

Commands are copy-paste ready throughout ("autorag search \"...\" --top-k 5 --json --debug", "autorag evidence <sessionId> --result 1 --json", the full maintenance command block) and concrete JSON examples cover common cases like the automation rule, matching 'fully executable; copy-paste ready code or commands; specific examples cover the common cases'; anchor 4 would imply missing key details, but flags, fallbacks, and config keys are all specified.

5 / 5

Workflow Clarity

The Preflight → Search → Maintenance flow is clearly sequenced with explicit checkpoints (preflight config check plus `status`/`health --json`, `--debug` diagnostics for citation and reference verification, automation loop guards and run-rate disabling, and a recovery path 'use autorag-setup rather than guessing'), fitting 'clear sequence with most checkpoints present'; it falls short of anchor 5 because the destructive/batch paths (file conversions, automation agent writes) lack a systematic validate-then-fix feedback loop rather than scattered guards.

4 / 5

Progressive Disclosure

Headers organize the ~290-line body, but no bundle files exist (no references/, scripts/, or assets/), so deep reference material — calculator semantics, filee/dupey conversion details, the automations.json spec — is inlined in SKILL.md where it belongs in separate files, and the single outward reference ("docs/minsync-setup.md#embedding-backends") is buried in the Rules section and dangling (no docs/ directory in the bundle), matching 'some structure but could be better organized; references present but not clearly signaled; content that should be separate is inline'.

3 / 5

Total

15

/

20

Passed

Description

87%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 that clearly states capabilities, gives explicit trigger phrases, and deftly boundaries itself against the autorag-setup skill. The only gaps are modest: slightly generic action verbs and a few missing natural synonyms (research papers, plain documents, extensions) that the body content actually covers.

DimensionReasoningScore

Specificity

Lists four concrete actions ("Search, summarize, compare, and answer questions") tied to a defined corpus ("local documents and configured datasources"), matching the 'several specific actions; minor gaps' anchor rather than 5, since coverage omits distinguishing capabilities like citation/evidence inspection and stays at the verb level rather than the comprehensive level of the 5-anchor example.

4 / 5

Completeness

Explicitly answers both what ("Search, summarize, compare, and answer questions from an already configured AutoRAG librarian") and when ("Use when the user asks AutoRAG to search PDFs, wikis, notes, or a knowledge base") with concrete trigger phrases, plus a boundary clause routing setup tasks to autorag-setup — a clear match to the top anchor; anchor 4 would require the 'when' to be less explicit, which it is not.

5 / 5

Trigger Term Quality

Natural terms "PDFs, wikis, notes, or a knowledge base" are phrases users would actually say, but common variations the body itself uses ("research papers", plain "documents", file extensions like .pdf) are missing from the description, which fits 'good keyword coverage; a few natural terms missing' rather than the comprehensive synonym coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

The "already configured AutoRAG librarian" framing carves a clear niche, and the trailing sentence ("Use autorag-setup for install, model, roots, indexing, or datasource changes") explicitly disambiguates from the sibling setup skill, giving minimal conflict risk; anchor 4's 'minor overlap risk with closely related skills' is already addressed by that routing sentence.

5 / 5

Total

18

/

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.