CtrlK
BlogDocsLog inGet started
Tessl Logo

algolia-automation

Automate Algolia tasks via Rube MCP (Composio). Always search tools first for current schemas.

74

6.18x
Quality

61%

Does it follow best practices?

Impact

99%

6.18x

Average score across 3 eval scenarios

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

Quality

Content

75%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 a well-structured, actionable guide with concrete MCP calls, validation checkpoints, and a useful pitfall/reference table. Minor redundancy in the search-first messaging and the absence of an explicit execution-error feedback loop keep it just short of top marks.

Suggestions

Consolidate the repeated "always search tools first" guidance into one place to remove redundancy across Prerequisites, Tool Discovery, and Step 1.

Add an explicit validate→fix→retry feedback loop for RUBE_MULTI_EXECUTE_TOOL failures (e.g. inspect error, re-search schema, retry) to strengthen workflow clarity for batch/index operations.

Provide one fully-resolved worked example (a concrete tool_slug with real arguments) so users can see a complete end-to-end call beyond placeholders.

DimensionReasoningScore

Conciseness

The body is largely lean and assumes Claude's competence, with only minor redundancy such as the "search tools first" directive repeated across Prerequisites, Tool Discovery, and Step 1.

4 / 5

Actionability

It supplies concrete MCP tool invocations with named parameters (RUBE_SEARCH_TOOLS, RUBE_MANAGE_CONNECTIONS, RUBE_MULTI_EXECUTE_TOOL); remaining placeholders like "TOOL_SLUG_FROM_SEARCH" are justified because schemas are fetched dynamically.

4 / 5

Workflow Clarity

A clear sequenced workflow (discover → check connection → execute) includes validation checkpoints (confirm ACTIVE status before executing, handle pagination), though there is no explicit error-recovery feedback loop for failed tool executions.

4 / 5

Progressive Disclosure

Content is well organized into clearly signaled sections (Prerequisites, Setup, Tool Discovery, Core Workflow, Known Pitfalls, Quick Reference) with no bundle files to navigate; at ~80 lines it stays appropriately single-file with good structure.

4 / 5

Total

16

/

20

Passed

Description

48%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 identifies the domain and tooling but is light on concrete capabilities and entirely lacks a "Use when" trigger clause. It is distinct enough to avoid most conflicts but would benefit from naming specific Algolia operations and explicit trigger phrases.

Suggestions

Name concrete Algolia operations in the description (e.g. manage indices, index records, configure synonyms, set search settings).

Add an explicit "Use when..." trigger clause listing natural phrases users would say (Algolia search, search index, reindexing, facets/synonyms).

Replace the generic "Automate Algolia tasks" with 2-3 specific actions to lift specificity above the domain-only anchor.

DimensionReasoningScore

Specificity

"Automate Algolia tasks" names the domain but the only action is the generic verb "Automate"; no concrete operations (e.g. indexing records, managing synonyms) are listed, and "Always search tools first" is a directive rather than a capability.

2 / 5

Completeness

It clearly states what the skill does ("Automate Algolia tasks via Rube MCP") but provides no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3 per the rubric guidelines.

3 / 5

Trigger Term Quality

"Algolia" is a natural keyword a user would say, but coverage relies on technical jargon ("Rube MCP", "Composio") and omits common synonyms like search index, records, synonyms, or faceting.

3 / 5

Distinctiveness Conflict Risk

The Algolia-specific framing via Rube MCP/Composio carves a clear niche with minimal conflict risk, though it could overlap slightly with a general Composio/Rube automation skill.

4 / 5

Total

12

/

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.

Validation15 / 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
ComposioHQ/awesome-claude-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.