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.
57
48%
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 ./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 good description that clearly identifies its domain (Algolia search) and includes an explicit 'Use when' clause with relevant trigger terms. Its main weaknesses are that the capabilities are described more as topic areas than concrete actions, and some trigger terms like 'search functionality' are generic enough to potentially conflict with other search-related skills.
Suggestions
Replace topic-area language with concrete actions, e.g., 'Configures Algolia indices, implements React InstantSearch components, tunes ranking and relevance rules, manages searchable attributes and facets.'
Add more Algolia-specific trigger terms to reduce conflict risk, e.g., 'algolia dashboard, search index, faceted search, algolia api key, searchable attributes, ranking formula'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Algolia search) and some actions/areas like 'implementation, indexing strategies, React InstantSearch, and relevance tuning', but these are more like topic areas than concrete actions (e.g., 'configure faceted search', 'set up searchable attributes'). | 2 / 3 |
Completeness | Clearly answers both 'what' (Algolia search implementation, indexing strategies, React InstantSearch, relevance tuning) and 'when' with an explicit 'Use when:' clause listing trigger scenarios. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'algolia', 'instantsearch', 'search api', 'search functionality', 'adding search to'. These cover the most common ways a user would phrase requests related to Algolia search. | 3 / 3 |
Distinctiveness Conflict Risk | The Algolia-specific terms ('algolia', 'instantsearch') are distinctive, but broader terms like 'search functionality' and 'search api' could overlap with other search-related skills (e.g., Elasticsearch, generic search implementations). | 2 / 3 |
Total | 10 / 12 Passed |
Implementation
14%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is a shallow outline with no executable code, entirely placeholder sharp edges, and a meaningless 'When to Use' section. It reads like a skeleton or draft rather than a functional skill—it describes what Algolia features exist but never shows Claude how to actually use them. The placeholder table with repeated 'Issue' / 'See docs' entries is particularly problematic as it wastes tokens while providing zero value.
Suggestions
Add concrete, executable code examples for each pattern (e.g., a complete React InstantSearch component with hooks, an indexing script using algoliasearch client)
Replace the placeholder sharp edges table with real issues and specific solutions (e.g., 'API key exposed in client bundle → Use search-only API key, never admin key')
Add step-by-step workflows with validation for indexing operations (e.g., batch upload with error handling and verification that records were indexed correctly)
Remove or rewrite the 'When to Use' section—it currently adds no information and wastes tokens
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is moderately concise but includes some unnecessary framing (e.g., 'Indexing strategies for keeping Algolia in sync with your data') and the 'When to Use' section is completely vacuous. The sharp edges table is entirely placeholder content, wasting tokens. | 2 / 3 |
Actionability | There is no executable code anywhere in the skill. It describes concepts and lists hook names but provides no concrete code examples, commands, or copy-paste ready snippets. The sharp edges table contains only placeholder 'Issue' and 'See docs' entries with zero actual guidance. | 1 / 3 |
Workflow Clarity | While the indexing section lists three approaches, there are no clear step-by-step workflows, no validation checkpoints, and no sequenced processes. The sharp edges table—which could provide critical workflow guidance—is entirely placeholder content. | 1 / 3 |
Progressive Disclosure | The content is a monolithic file with no references to external files, no links to detailed documentation, and no clear navigation structure. All sections are at the same shallow depth with no way to drill deeper into any topic. | 1 / 3 |
Total | 5 / 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
- sickn33/antigravity-awesome-skills
- Commit
d739c8b
- 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.