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.
Install with Tessl CLI
npx tessl i github:haniakrim21/everything-claude-code --skill algolia-search66
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 implementation. The main weakness is that the capabilities could be more concrete - listing specific actions rather than abstract concepts like 'patterns' and 'strategies'. The explicit 'Use when:' clause with relevant keywords is a strong point.
Suggestions
Replace abstract terms like 'Expert patterns' and 'indexing strategies' with concrete actions such as 'Configure search indices, implement faceted filtering, set up query rules'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Algolia search) and mentions some actions like 'implementation, indexing strategies, relevance tuning' but these are somewhat abstract rather than concrete actions like 'configure indices' or 'set up faceted search'. | 2 / 3 |
Completeness | Clearly answers both what (Algolia search implementation, indexing, React InstantSearch, relevance tuning) AND when with explicit 'Use when:' clause listing specific trigger scenarios. | 3 / 3 |
Trigger Term Quality | Good coverage of natural terms users would say: 'algolia', 'instantsearch', 'search api', 'search functionality', 'adding search to'. These are terms users would naturally use when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Very distinct niche focused specifically on Algolia. The explicit mention of 'Algolia', 'InstantSearch', and Algolia-specific concepts makes it unlikely to conflict with generic search or other search provider skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
27%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a high-level overview of Algolia integration patterns but fails to deliver actionable guidance. The complete absence of code examples for a technical integration skill is a critical gap. The sharp edges table appears to be a broken template with placeholder content, making it useless.
Suggestions
Add executable code examples for each pattern (React InstantSearch setup, SSR configuration, indexing operations) - these should be copy-paste ready
Fix the sharp edges table with actual issues, severities, and concrete solutions instead of placeholder 'Issue' and 'See docs' text
Include specific code snippets for the hooks mentioned (useSearchBox, useHits, etc.) showing actual usage patterns
Add validation steps for the indexing workflow, such as how to verify sync status or handle indexing failures
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Content is relatively lean and avoids over-explaining basic concepts, but includes some unnecessary filler phrases like 'Modern React InstantSearch setup' and could be tighter. The sharp edges table is completely broken with placeholder text. | 2 / 3 |
Actionability | No executable code examples provided despite being a technical integration skill. Lists hooks and concepts abstractly without showing actual implementation. 'See docs' is not actionable guidance. | 1 / 3 |
Workflow Clarity | The indexing section lists three approaches with some ordering, but lacks concrete steps, validation checkpoints, or error handling. SSR section mentions considerations but doesn't sequence them into a workflow. | 2 / 3 |
Progressive Disclosure | No references to external files for detailed content. The sharp edges table is completely broken with placeholder 'Issue' and 'See docs' entries that provide no actual navigation or information. | 1 / 3 |
Total | 6 / 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 | |
- 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.