CtrlK
BlogDocsLog inGet started
Tessl Logo

rag-assistant

Knowledge base assistant that retrieves and cites documents from a curated index. Use when answering questions that must be grounded in specific source material with citations.

62

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./modules/skills/src/main/resources/META-INF/skills/rag-assistant/SKILL.md
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.

A compact, well-structured RAG assistant prompt with a clear answer workflow and explicit fallback handling. The main weakness is redundancy between the opening tool list, the Tools section, and the Guardrails.

Suggestions

Deduplicate the tool descriptions — present them once, either in the opening list or in the 'Tools' section, not both.

Collapse the 'Guardrails' into the numbered workflow where they overlap (e.g., cite-only and say-so rules) to remove restated instructions.

Add a brief example of the expected citation format to make the 'Cite which document(s)' step fully executable.

DimensionReasoningScore

Conciseness

The body is mostly efficient but includes redundancy — the three tools are described in the opening bullet list and again in the 'Tools' section, and the 'Guardrails' restate steps already in 'How to answer questions' — so it could be tightened.

3 / 5

Actionability

It names specific tools and gives a concrete numbered process ('Search… Read… Compose using ONLY… Cite… If not enough, say so'), with only minor gaps such as no example citation format.

4 / 5

Workflow Clarity

The 5-step 'How to answer questions' sequence is clear and includes an explicit insufficient-information checkpoint ('If the documents don't contain enough information, say so honestly'), though error-recovery guidance is light.

4 / 5

Progressive Disclosure

The body is under 50 lines with no external references needed, and is organized into clear, well-labeled sections (How to answer, Skills, Tools, Guardrails), meeting the simple-skill exception for a top score.

5 / 5

Total

16

/

20

Passed

Description

78%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 both capability and trigger condition in third-person voice with concrete citations language. It could be sharpened by naming more specific actions and adding a few more natural trigger synonyms.

Suggestions

Add one or two more concrete actions (e.g., 'search by topic', 'browse available sources') to lift specificity toward comprehensive coverage.

Include a few more natural trigger terms or file/format cues users might say (e.g., 'documentation lookup', 'cite your sources') to broaden trigger coverage.

DimensionReasoningScore

Specificity

The description names the domain (knowledge base retrieval) and two concrete actions — 'retrieves and cites documents from a curated index' — but offers only these two actions rather than comprehensive coverage.

3 / 5

Completeness

It explicitly answers both 'what' (retrieves and cites documents from a curated index) and 'when' ('Use when answering questions that must be grounded in specific source material with citations') with a concrete trigger phrase, in third-person voice.

5 / 5

Trigger Term Quality

It uses natural phrases a user might say ('knowledge base', 'documents', 'citations', 'grounded in specific source material') with good coverage, though a few common synonyms or variations are missing.

4 / 5

Distinctiveness Conflict Risk

The citation-grounded RAG niche is mostly distinct, with only minor overlap risk against general search or document-reading skills.

4 / 5

Total

16

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository
Atmosphere/atmosphere
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.