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.
66
Quality
63%
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
89%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 solid skill description with excellent trigger terms and clear distinctiveness for Algolia-specific search tasks. The main weakness is the use of vague framing ('Expert patterns for') instead of concrete action verbs describing what the skill actually does. The explicit 'Use when:' clause is well-structured with relevant keywords.
Suggestions
Replace 'Expert patterns for' with concrete action verbs like 'Implements Algolia search, configures indexes, builds React InstantSearch components, and tunes relevance settings'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Algolia search) and mentions some capabilities like 'indexing strategies', 'React InstantSearch', and 'relevance tuning', but uses vague framing ('Expert patterns') rather than listing concrete actions like 'configure indexes' or 'implement faceted search'. | 2 / 3 |
Completeness | Clearly answers both what (Algolia search implementation, indexing, InstantSearch, relevance tuning) and when (explicit 'Use when:' clause with trigger terms). The structure explicitly addresses both questions. | 3 / 3 |
Trigger Term Quality | Includes good natural keywords users would say: 'algolia', 'instantsearch', 'search api', 'search functionality', and 'adding search to'. These cover common variations of how users would request search implementation help. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with Algolia-specific terminology ('Algolia', 'InstantSearch', 'relevance tuning'). Unlikely to conflict with generic search or other search provider skills due to the specific product naming. | 3 / 3 |
Total | 11 / 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 content functions as a bare index/table of contents rather than a functional skill. While it's concise and has clear references to sub-skills, it provides zero actionable guidance, no workflow context, and no overview explaining what Algolia is or when to use each sub-skill. The main SKILL.md should provide at minimum a quick-start example or decision tree for choosing between the sub-skills.
Suggestions
Add a brief quick-start section with a minimal executable code example for the most common Algolia use case
Include a decision matrix or brief descriptions explaining when to use each sub-skill (e.g., 'Use React InstantSearch for client-side search, use Next.js SSR for SEO-critical pages')
Add at least one concrete, copy-paste ready code snippet demonstrating basic Algolia initialization or search query
| 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 sub-skills. | 1 / 3 |
Progressive Disclosure | References to sub-skills are one level deep and clearly signaled, but the main file lacks any overview content or quick-start guidance to help users understand when to use each sub-skill. | 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
3395991
- 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.