CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/algolia-search/SKILL.md
SKILL.md
Quality
Evals
Security

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 delivers highly actionable, copy-paste-ready Membrane CLI instructions with a well-structured connection workflow. It is held back by boilerplate concept explanations, a dangling 'Step 2' reference, and the absence of validation guidance for destructive operations like index deletion.

Suggestions

Delete or compress the introductory paragraph explaining what Algolia is and the empty 'Overview' section — Claude already knows this.

Fix the dangling 'skip to Step 2' reference by actually labeling and including a Step 2 section (searching/running actions).

Add a verification step before destructive actions, e.g. run 'retrieve-record' or 'list-indices' to confirm the target index/record ID before 'delete-index'/'delete-record'.

DimensionReasoningScore

Conciseness

The body is mostly efficient CLI guidance, but the opening paragraph explains what Algolia is ('a hosted search engine that provides website and mobile app developers with the tools to build fast and relevant search experiences... used by companies of all sizes') — a concept Claude already knows — and the near-empty 'Overview' section (Index / Record / API Key) adds padding, matching 'mostly efficient but includes some unnecessary explanation'.

3 / 5

Actionability

Fully executable, copy-paste-ready commands throughout: 'npm install -g @membranehq/cli@latest', 'membrane connection ensure "https://www.algolia.com/" --json', 'membrane action run <actionId> --connectionId=... --input '{"key": "value"}' --json', plus a proxy options table — the specific commands cover the common cases end to end.

5 / 5

Workflow Clarity

The connection flow has good state handling (polling with --wait, READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR branches), but the text says 'skip to **Step 2**' when no Step 2 exists — a sequencing incoherence — and destructive actions like 'Delete Index' ("Delete an entire index and all its settings") have no verification guidance, capping clarity at 3.

3 / 5

Progressive Disclosure

A single-file skill with well-organized sections (install, auth, connect, search, run, proxy, best practices) and no bundle files to navigate; the ~145-line body keeps the action catalog and proxy options inline where a split into a reference file would be slightly cleaner, fitting 'good structure with minor organization gaps'.

4 / 5

Total

15

/

20

Passed

Description

67%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 clearly states what the skill does and includes an explicit 'Use when' clause, with concrete resource types giving it reasonable specificity. Weaknesses are thin trigger coverage (essentially only the product name), a circular when-clause, and a single generic verb with a typo ('Indexs').

Suggestions

Broaden trigger terms beyond the product name, e.g. 'Use when the user mentions Algolia, search indexing, records, query rules, or analytics tasks'.

Replace the single generic verb with specific actions, e.g. 'Manage indices: search records, add/update/delete records, configure query rules and tasks, manage API keys and users'.

Fix the typo 'Indexs' to 'Indices'.

DimensionReasoningScore

Specificity

"Manage Indexs, Records, Rules, Tasks, Clusters, Users" names six concrete resource types covering the API surface, though a single generic verb ("Manage") and the "Indexs" typo keep it short of comprehensive action coverage.

4 / 5

Completeness

Both parts are present: a clear what ("Algolia Search integration. Manage Indexs, Records...") and an explicit "Use when the user wants to interact with Algolia Search data" clause; the when is explicit but circular and could name more concrete trigger phrases, so it falls just below the top anchor.

4 / 5

Trigger Term Quality

"Algolia Search" plus the resource nouns provide some relevant keywords, but common natural variations users would say ("indexing", "search results", "query", "facets", ".algolia") are missing, matching the anchor with some keywords but missing variations.

3 / 5

Distinctiveness Conflict Risk

Naming the specific product "Algolia Search" in both the what and when clauses pins a clear niche with minimal wrong-skill triggering, but the sole trigger being the product name leaves minor overlap risk with generic search/index skills.

4 / 5

Total

15

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

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

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.