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:boisenoise/skills-collections --skill algolia-searchOverall
score
61%
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
90%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
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 reasonable high-level overview of Algolia integration patterns but fails to deliver actionable guidance. The complete absence of executable code examples is a critical gap for a technical integration skill, and the placeholder 'Sharp Edges' table with empty content actively harms quality. The skill reads more like a topic outline than practical implementation guidance.
Suggestions
Add executable code examples for each pattern (React InstantSearch setup, Next.js SSR configuration, indexing operations with algoliasearch client)
Replace the placeholder 'Sharp Edges' table with actual issues and solutions, or remove it entirely
Add concrete code for batch indexing operations showing partialUpdateObjects and saveObjects usage
Include links to reference files or external documentation for advanced topics like custom widgets and relevance tuning
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Content is relatively lean and avoids excessive explanation, but the 'Sharp Edges' table is completely empty/placeholder with generic 'Issue' and 'See docs' entries that waste tokens without providing value. | 2 / 3 |
Actionability | No executable code examples provided despite describing React hooks, Next.js setup, and indexing strategies. Content describes what to use but never shows how with concrete, copy-paste ready code. | 1 / 3 |
Workflow Clarity | The indexing section lists three approaches with some best practices, but lacks explicit step sequences, validation checkpoints, or error recovery guidance for data synchronization operations. | 2 / 3 |
Progressive Disclosure | No references to external files or documentation despite mentioning 'See docs' repeatedly. Content is a flat structure with no clear navigation to detailed materials or examples. | 1 / 3 |
Total | 6 / 12 Passed |
Validation
91%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.