CtrlK
BlogDocsLog inGet started
Tessl Logo

embedding-strategies

Select and optimize embedding models for semantic search and RAG applications. Use when choosing embedding models, implementing chunking strategies, or optimizing embedding quality for specific domains.

63

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

57%

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 well-organized overview with excellent progressive disclosure, but it leans on reference data and defers most executable guidance to details.md, leaving the in-skill workflow and actionability incomplete. The dated model table also introduces a freshness concern.

Suggestions

Move or isolate the time-sensitive model versions/date into a clearly marked section (e.g., a dated 'current models' block with an 'older/deprecated' subsection) so staleness does not penalize conciseness.

Add at least one concrete, executable chunking or embedding code snippet inline so the skill is actionable without always opening references/details.md.

Tighten the embedding pipeline into explicit numbered steps with a validation checkpoint (e.g., verify embedding dimensions/normalization before indexing) to give the workflow clear feedback loops.

DimensionReasoningScore

Conciseness

The body is mostly lean and unpadded, but the "Embedding Model Comparison (2026)" table embeds time-sensitive version strings and a date that the rubric penalizes outside a deprecated/old-patterns section.

2 / 3

Actionability

The model comparison table gives concrete selection data, but executable code/commands and concrete chunking details are deferred to references/details.md and the pipeline diagram is conceptual.

2 / 3

Workflow Clarity

The embedding pipeline is shown as a linear sequence (Document → Chunking → Preprocessing → Embedding Model → Vector) but lacks validation checkpoints or feedback loops, and the branch hints are underspecified.

2 / 3

Progressive Disclosure

A clear overview with a well-signaled, verified one-level-deep reference (references/details.md) and content appropriately split between the overview and the detail file.

3 / 3

Total

9

/

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.

A strong description that concisely states the capability and provides explicit, natural trigger terms with a clear Use-when clause. The only weakness is a somewhat narrow capability list (select/optimize) rather than a broader set of concrete actions.

DimensionReasoningScore

Specificity

Names the domain and two concrete actions ("Select and optimize embedding models"), but the capability list is limited rather than comprehensive.

2 / 3

Completeness

Explicitly answers both what (select/optimize embeddings for semantic search and RAG) and when via an explicit "Use when…" clause.

3 / 3

Trigger Term Quality

Good coverage of natural terms a user would say: "embedding models", "RAG", "semantic search", and "chunking strategies".

3 / 3

Distinctiveness Conflict Risk

A clear niche (embeddings for semantic search/RAG) with distinct triggers unlikely to fire for unrelated skills.

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