CtrlK
BlogDocsLog inGet started
Tessl Logo

algolia-search

Expert patterns for Algolia search implementation, indexing strategies, React InstantSearch, and relevance tuning

45

Quality

48%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/antigravity-awesome-skills-claude/skills/algolia-search/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

42%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill provides excellent, actionable code examples covering the full Algolia integration surface area, but suffers significantly from being a monolithic document that tries to cover everything inline. The Sharp Edges and Validation Checks sections are hollow stubs that waste tokens without providing value. The content would be dramatically improved by splitting into focused sub-files and trimming explanatory text that Claude doesn't need.

Suggestions

Split the seven major pattern sections into separate bundle files (e.g., react-instantsearch.md, indexing.md, security.md, relevance.md) and make SKILL.md a concise overview with links to each.

Either flesh out the Sharp Edges section with actual mitigation details and code, or remove the stub entries entirely - listing 'Admin API Key in Frontend Code / Severity: CRITICAL' with no content wastes tokens.

Remove explanatory prose that Claude already knows (e.g., 'Three main approaches: 1. Full Reindexing...', widget type listings, key type descriptions) and let the code examples speak for themselves.

Add a brief workflow overview at the top showing the typical integration sequence (configure index → index data → build search UI → tune relevance) to connect the individual patterns.

DimensionReasoningScore

Conciseness

The skill is extremely verbose at ~500+ lines. It explains concepts Claude already knows (what API keys are, what faceting is, what autocomplete is), lists widget types that are in documentation, and includes extensive code examples that could be significantly condensed. The Sharp Edges and Validation Checks sections are skeletal stubs with just severity labels and no actionable content, wasting tokens. Anti-patterns sections repeat information already shown in code comments.

1 / 3

Actionability

The code examples are fully executable, copy-paste ready TypeScript/React code with proper imports, environment variable usage, and realistic patterns. Examples cover client setup, indexing, SSR, faceted search, autocomplete, and security - all with concrete, runnable code rather than pseudocode.

3 / 3

Workflow Clarity

Individual patterns are clear but there's no overarching workflow connecting them (e.g., 'first configure index, then index data, then build UI'). The full reindex with zero-downtime example has good sequential steps, but the Sharp Edges section lists items without any detail or mitigation steps, and Validation Checks lack actionable remediation workflows. No explicit validation checkpoints for the indexing pipeline.

2 / 3

Progressive Disclosure

This is a monolithic wall of text with no bundle files to offload detailed content. All seven major patterns with full code examples are inlined in a single file. The Sharp Edges section has 10 items that are just titles with severity labels - no content. References point to external URLs only. Content would benefit enormously from splitting into separate files (e.g., INDEXING.md, SSR.md, SECURITY.md) with the SKILL.md serving as an overview.

1 / 3

Total

7

/

12

Passed

Description

54%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description benefits from strong, specific product-level terminology (Algolia, React InstantSearch) that makes it distinctive and includes good trigger terms. However, it lacks concrete action verbs describing what the skill actually does and entirely omits a 'Use when...' clause, significantly hurting completeness. The description reads more like a topic list than an actionable skill description.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about Algolia setup, search indexing, configuring search relevance, or building search UIs with React InstantSearch.'

Replace vague topic labels with concrete actions, e.g., 'Configures Algolia search indices, implements faceted search with React InstantSearch, tunes ranking and relevance rules, and manages index synchronization strategies.'

DimensionReasoningScore

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. It doesn't list specific operations like 'configure search indices', 'build faceted search UI', or 'set ranking rules'.

2 / 3

Completeness

Describes the 'what' at a high level but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and the 'what' itself is also somewhat vague, bringing this to 1.

1 / 3

Trigger Term Quality

Includes strong natural keywords users would say: 'Algolia', 'search', 'indexing', 'React InstantSearch', and 'relevance tuning'. These are terms developers would naturally use when seeking help with Algolia integration.

3 / 3

Distinctiveness Conflict Risk

Algolia is a very specific product/service, and the combination of 'Algolia', 'React InstantSearch', and 'relevance tuning' creates a clear niche that is unlikely to conflict with other skills.

3 / 3

Total

9

/

12

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 9 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (925 lines); consider splitting into references/ and linking

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

9

/

11

Passed

Repository
popey/claude-code-skills
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.