Name: algolia-search
Rating: 62.4 (1 reviews)
Author: membranedev

algolia-search

Algolia Search integration. Manage Indexs, Records, Rules, Tasks, Clusters, Users. Use when the user wants to interact with Algolia Search data.

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/algolia-search/SKILL.md

Quality

Content

68%Weight 40%Scale 1-5

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

The body is highly actionable with copy-paste CLI commands and a well-structured connection workflow, but it is dragged down by a padded introductory paragraph and a lack of validation guidance around destructive actions like deleting indices.

Suggestions

Remove or condense the marketing-style opening paragraph about what Algolia is, since Claude already knows this.

Add a verification/checkpoint step before destructive actions, e.g. 'Before running delete-index or delete-record, confirm the target index/objectID with the user and consider a retrieve-record or list-indices call first.'

Consider splitting the detailed connection-state reference (READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) into a references file to push progressive disclosure toward 5.

Dimension	Reasoning	Score
Conciseness	Mostly efficient executable commands, but the opening paragraph ('Algolia Search is a hosted search engine that provides website and mobile app developers with the tools to build fast and relevant search experiences...') explains general knowledge Claude already has and could be trimmed.	3 / 5
Actionability	Fully executable, copy-paste-ready commands throughout (install, login, connection ensure, action list/run with --input JSON, request proxy) plus a concrete popular-actions table and proxy flag table covering the common cases.	5 / 5
Workflow Clarity	The connection workflow has strong validation and feedback loops, but destructive operations (Delete Index, Delete Record) are run via 'membrane action run' with no verification step, and the rubric caps destructive-skill workflow clarity at 3.	3 / 5
Progressive Disclosure	A single cohesive CLI guide with well-organized section headers and clear navigation; no bundle files exist and none are strictly needed, though at over 50 lines the simple-skill 5 exception does not apply.	4 / 5
	Total	15 / 20 Passed

Description

78%Weight 40%Scale 1-5

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 is well-constructed, explicitly stating both capability and trigger conditions with a clear product niche. Its main weakness is a generic 'Manage' verb and a somewhat vague 'when' clause that could name concrete user intents.

Suggestions

Replace the generic verb 'Manage' with distinct concrete actions (e.g., 'Create, search, update, and delete Indices, Records, Rules...') to lift specificity toward 5.

Tighten the 'Use when' clause with concrete trigger phrases, e.g. 'Use when the user wants to search records, manage indices, or configure Algolia rules and API keys.'

Fix the typo 'Indexs' to 'Indices' for natural-term quality.

Dimension	Reasoning	Score
Specificity	Lists six concrete resource types (Indexs, Records, Rules, Tasks, Clusters, Users) for comprehensive coverage, but the single generic verb 'Manage' lacks distinct CRUD actions, keeping it below a 5.	4 / 5
Completeness	Explicitly answers both 'what' (manage Algolia resources) and 'when' ('Use when the user wants to interact with Algolia Search data'), but the 'when' is generic rather than tied to concrete trigger phrases, so not a 5.	4 / 5
Trigger Term Quality	Includes natural product and resource keywords ('Algolia Search', 'Indexs, Records, Rules, Tasks, Clusters, Users') plus an explicit 'Use when...' trigger, though a few natural synonyms are missing.	4 / 5
Distinctiveness Conflict Risk	Targets a clearly named product niche ('Algolia Search integration') with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	17 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/algolia-search/SKILL.md
Commit: f484c82

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.