Vector embeddings configuration and semantic search
65
51%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./src/skills/bundled/embeddings/SKILL.mdQuality
Discovery
22%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is too terse and abstract to effectively guide skill selection. It names a domain (vector embeddings/semantic search) but fails to specify concrete actions Claude can perform and provides no guidance on when to use this skill. The lack of a 'Use when...' clause and missing action verbs significantly limit its utility.
Suggestions
Add specific concrete actions like 'Configure embedding models, create vector indexes, perform similarity queries, set up semantic search pipelines'
Include a 'Use when...' clause with explicit triggers such as 'Use when the user mentions embeddings, vector search, similarity matching, RAG setup, or semantic retrieval'
Add common keyword variations users might say: 'vector database', 'embedding model', 'similarity search', 'RAG', 'vector store', 'cosine similarity'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses abstract language ('configuration', 'semantic search') without listing concrete actions. It doesn't specify what actions Claude can perform - no verbs like 'create', 'configure', 'query', or 'index'. | 1 / 3 |
Completeness | Only weakly addresses 'what' (configuration and search) and completely lacks any 'when' guidance. No 'Use when...' clause or explicit trigger conditions are provided. | 1 / 3 |
Trigger Term Quality | Contains some relevant technical keywords ('vector embeddings', 'semantic search') that users might say, but misses common variations like 'embedding model', 'similarity search', 'vector database', 'RAG', or 'vector store'. | 2 / 3 |
Distinctiveness Conflict Risk | 'Vector embeddings' and 'semantic search' provide some domain specificity, but 'configuration' is vague and could overlap with general config skills. The description doesn't clearly carve out its niche. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
79%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured API reference that excels at providing concrete, executable code examples without unnecessary explanation. The main weaknesses are the lack of explicit multi-step workflows with validation checkpoints and the monolithic structure that could benefit from progressive disclosure to separate files.
Suggestions
Add a 'Common Workflows' section showing complete sequences like 'index documents → validate storage → search' with explicit validation steps between operations
Include error handling examples for API failures, rate limits, and invalid inputs
Consider splitting the provider comparison tables and detailed use cases into separate reference files, keeping SKILL.md as a quick-start overview
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, presenting API references and examples without explaining what embeddings are or how vector search works conceptually. Every section provides actionable information without padding. | 3 / 3 |
Actionability | Provides fully executable TypeScript code examples throughout, with complete function signatures, configuration objects, and copy-paste ready snippets for all major operations including embedding, search, storage, and caching. | 3 / 3 |
Workflow Clarity | While individual operations are clear, there's no explicit workflow for common multi-step processes like 'index a document collection then search it.' Missing validation steps for batch operations and no error handling guidance for API failures. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but it's a monolithic reference document. Could benefit from splitting provider details, use cases, or the full API reference into separate files with a leaner overview in the main skill. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
2a8c94e
Table of Contents
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.