CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

knowledge-base-search

Search and locate relevant content within a local knowledge base (files, indices, or PageIndex). Use when you need verifiable citations (file + page/paragraph) to support answers from local sources.

Quality

69%

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 ./scientific-skills/Other/knowledge-base-search/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

60%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 well-structured body with a clear five-step workflow, concrete search commands, and real bundle files. The main weaknesses are duplicated workflow content across sections, an example CSV that conflicts with the actual provided template, and missing executable guidance for the vector/PageIndex retrieval paths it advertises.

Suggestions

Align the example CSV output with assets/hit_list_template.csv — the body's example uses English headers (file_path,location,snippet,relevance_score,notes) while the template uses Chinese headers (来源文件,位置,命中片段,相关性评分,备注) — either fix the template or the example so the claimed compatibility is real.

Merge the "Example Usage" steps with the "Implementation Details" section, which currently repeat the same workflow (index confirmation, query strategy, ranking, citation resolution), nearly halving the body length.

Add an explicit validation checkpoint in step 5 (e.g., verify each snippet traces back to the cited location and the hit list matches the template columns before saving) and integrate guide.md's quality check into the workflow.

Provide an executable method or explicit fallback for vector index and PageIndex retrieval, which are currently advertised but have no runnable commands.

DimensionReasoningScore

Conciseness

No generic filler explaining concepts Claude already knows, but the document duplicates its own workflow: the "Example Usage" steps and "Implementation Details" sections each cover index detection, query/synonym strategy, filtering/ranking, and citation resolution, and "Key Features" overlaps "When to Use". Fits "mostly efficient but could be tightened"; not 2 because every section carries skill-specific guidance rather than padding.

3 / 5

Actionability

Provides concrete executable commands (glob patterns, `grep -RIn "API key\|key rotation\|rotate" ./kb/`) and a worked CSV example, but key details are missing: vector index and PageIndex retrieval have no executable method (assumed external tooling), and the example CSV headers (file_path,location,snippet,relevance_score,notes) do not match the actual assets/hit_list_template.csv columns (来源文件,位置,命中片段,相关性评分,备注) despite the body claiming compatibility. Fits "some concrete guidance but incomplete"; not 4 because the template mismatch and unexecutable retrieval paths are more than minor gaps.

3 / 5

Workflow Clarity

Five clearly sequenced steps with an explicit error-recovery fallback ("If indices are missing/corrupted, fall back to direct file scanning; if scanning is not possible, report the limitation and required remediation") and a relevance-filtering checkpoint in step 4. Not 5 because there is no checkpoint verifying the saved hit list against the template columns or confirming snippets trace back to sources; not 3 because the sequence and fallback loop are explicit. The read-only nature of the skill means the destructive/batch cap does not apply.

4 / 5

Progressive Disclosure

Both referenced bundle files exist (references/guide.md, assets/hit_list_template.csv) and are clearly signaled in Dependencies, one level deep. Not 5 because guide.md largely duplicates body content (output formats, checklists) rather than adding depth, and detailed implementation content (ranking weights, citation resolution rules) remains inline in the ~120-line body despite a references file being available; not 3 because references are clearly signaled and shallow.

4 / 5

Total

14

/

20

Passed

Description

65%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 solid description that explicitly covers what the skill does and when to use it, with good natural trigger terms and a reasonably distinct niche. The main weaknesses are limited action coverage (only search/locate mentioned) and second-person phrasing in the trigger clause.

Suggestions

Rewrite the trigger clause in third person (e.g., "Use when the user needs verifiable citations..." or "Use when working with local knowledge bases...") to match the rubric's voice requirement and avoid the specificity penalty.

Enumerate more concrete capabilities in the description (e.g., rank and filter hits, output citation hit lists, compare how multiple documents treat a topic) to raise specificity beyond two generic actions.

Add natural trigger synonyms such as "documentation search", "local sources", or "source verification" to broaden keyword coverage.

DimensionReasoningScore

Specificity

The description names the domain ("local knowledge base (files, indices, or PageIndex)") and 1-2 concrete actions ("Search and locate relevant content"), fitting anchor 3, but the rubric's second-person penalty ("Use when you need verifiable citations...") reduces it by 1. Not anchor 1 because the domain and actions are concrete, not vague.

2 / 5

Completeness

Explicitly answers both: what ("Search and locate relevant content within a local knowledge base") and when ("Use when you need verifiable citations (file + page/paragraph) to support answers from local sources"). Not 5 because the 'when' covers a single trigger scenario and could enumerate more use cases (fact lookup, wording verification, document comparison); clearly above 3 since both what and when are explicit.

4 / 5

Trigger Term Quality

Includes natural phrases users would say ("knowledge base", "search", "citations", "local sources", "file + page/paragraph") with good coverage. Not 5 because "PageIndex" is technical jargon and common variations like "documentation", "find the source", or "quote" are missing; not 3 because multiple natural trigger terms are present rather than a single keyword.

4 / 5

Distinctiveness Conflict Risk

The citation-with-location niche ("verifiable citations (file + page/paragraph) to support answers from local sources") is mostly distinct from generic file-search skills. Not 5 because "Search and locate relevant content within a local knowledge base" still overlaps with generic search/RAG-style skills; not 3 because the citation-traceability trigger is a clear differentiator.

4 / 5

Total

14

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

aipoch/medical-research-skills

Path

scientific-skills/Other/knowledge-base-search/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.