algolia-search
Expert patterns for Algolia search implementation, indexing strategies, React InstantSearch, and relevance tuning Use when: adding search to, algolia, instantsearch, search api, search functionality.
67
59%
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 ./.agent/skills/algolia-search/SKILL.mdQuality
Discovery
82%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 is a reasonably well-structured skill description with explicit trigger guidance and good keyword coverage for Algolia-specific searches. The main weakness is that the capabilities are described at a category level rather than with specific concrete actions, and some trigger terms are generic enough to potentially conflict with other search-related skills.
Suggestions
Replace category labels with specific actions: 'Configure Algolia indices, implement React InstantSearch components, tune search relevance rankings' instead of 'indexing strategies' and 'relevance tuning'
Add more Algolia-specific trigger terms to reduce conflict risk: 'algolia dashboard', 'searchable attributes', 'facets', 'InstantSearch widgets'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Algolia search) and mentions some capabilities like 'indexing strategies', 'React InstantSearch', and 'relevance tuning', but these are more category labels than concrete actions. Missing specific verbs like 'configure', 'implement', 'optimize'. | 2 / 3 |
Completeness | Clearly answers both what (Algolia search implementation, indexing, InstantSearch, relevance tuning) and when (explicit 'Use when:' clause with specific triggers like 'adding search to', 'algolia', 'search functionality'). | 3 / 3 |
Trigger Term Quality | Good coverage of natural terms users would say: 'algolia', 'instantsearch', 'search api', 'search functionality', 'adding search'. These are terms users would naturally use when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | While 'Algolia' and 'InstantSearch' are distinctive, generic terms like 'search functionality' and 'search api' could overlap with other search-related skills (Elasticsearch, generic search implementations). The Algolia-specific terms help but don't fully prevent conflicts. | 2 / 3 |
Total | 10 / 12 Passed |
Implementation
37%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is essentially an empty shell that only serves as a navigation index to sub-skills. While concise, it provides zero actionable content, no workflow guidance, and insufficient context for Claude to understand when to use each sub-skill. The main SKILL.md should contain at least a quick start example or decision tree for choosing between the sub-skills.
Suggestions
Add a quick start section with a minimal executable Algolia integration example (e.g., basic search client setup and query)
Include a decision matrix or brief descriptions explaining when to use each sub-skill (e.g., 'Use React InstantSearch for client-side search UI, use SSR for SEO-critical pages')
Add a basic workflow showing the typical integration sequence: 1) Set up indexing, 2) Configure search, 3) Build UI
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is extremely minimal with no unnecessary explanation or padding. Every line serves a purpose as a navigation hub. | 3 / 3 |
Actionability | The skill provides no concrete code, commands, or executable guidance. It only lists links to sub-skills without any actionable content in the main file itself. | 1 / 3 |
Workflow Clarity | There is no workflow, sequence, or process described. The content is purely a table of contents with no guidance on when or how to use the linked modules. | 1 / 3 |
Progressive Disclosure | The structure uses one-level-deep references which is good, but there's no quick start content, no overview of what Algolia integration involves, and no guidance on which sub-skill to use when. | 2 / 3 |
Total | 7 / 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 | |
- Repository
- Dokhacgiakhoa/antigravity-ide
- Commit
332e58b
- 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.