CtrlK
BlogDocsLog inGet started
Tessl Logo

hybrid-search-implementation

Combine vector and keyword search for improved retrieval. Use when implementing RAG systems, building search engines, or when neither approach alone provides sufficient recall.

52

Quality

56%

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 ./skills/hybrid-search-implementation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

22%

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

The body is well-structured and brief but almost entirely generic: it provides no actual hybrid-search implementation guidance, relies on boilerplate instructions, and points to a resource file that is missing. Actionability and workflow clarity are the weakest dimensions.

Suggestions

Replace the generic Instructions with concrete hybrid-search guidance: name fusion methods (e.g. reciprocal rank fusion, weighted score combination), libraries, and a minimal executable code example.

Turn the workflow into a real sequenced process with explicit validation (e.g. evaluate recall@k on a test set before and after fusion) instead of boilerplate steps.

Either create `resources/implementation-playbook.md` with the promised detailed patterns and examples, or remove the broken reference.

DimensionReasoningScore

Conciseness

The body is short and avoids concept explanations, but the Instructions ("Clarify goals, constraints, and required inputs", "Apply relevant best practices and validate outcomes") and the "Do not use this skill when" bullets are generic boilerplate that could be tightened.

2 / 3

Actionability

Despite the title "Hybrid Search Implementation", the body gives no concrete code, commands, libraries, or fusion techniques (e.g. RRF, score normalization) — only abstract direction, matching the 'vague or abstract; no concrete code/commands' anchor.

1 / 3

Workflow Clarity

The listed steps are generic boilerplate (clarify → apply best practices → validate) rather than a real hybrid-search workflow, with no concrete validation checkpoints for the actual task.

1 / 3

Progressive Disclosure

Sections are well organized and the reference to `resources/implementation-playbook.md` is one level deep and clearly signaled, but that referenced file does not exist on disk, so the disclosure promise is broken.

2 / 3

Total

6

/

12

Passed

Description

90%

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, uses third-person voice, and clearly answers both what the skill does and when to use it with natural trigger terms. Its only weakness is that it names a single combined action rather than enumerating multiple concrete operations.

DimensionReasoningScore

Specificity

"Combine vector and keyword search for improved retrieval" names the core action and goal but lists only one combined action rather than multiple specific concrete operations, matching the 'names domain and some actions' anchor.

2 / 3

Completeness

It states what ("Combine vector and keyword search for improved retrieval") and an explicit when ("Use when implementing RAG systems, building search engines, or when neither approach alone provides sufficient recall"), satisfying both halves.

3 / 3

Trigger Term Quality

Natural user-facing terms like "RAG systems", "search engines", "vector and keyword search", and "neither approach alone provides sufficient recall" give good coverage of phrasings a user would actually say.

3 / 3

Distinctiveness Conflict Risk

The combination of vector and keyword search is a clear niche with distinct triggers unlikely to fire for unrelated skills, fitting the 'clear niche with distinct triggers' anchor.

3 / 3

Total

11

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
rmyndharis/antigravity-skills
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.