algolia-automation
Automate Algolia tasks via Rube MCP (Composio). Always search tools first for current schemas.
Install with Tessl CLI
npx tessl i github:haniakrim21/everything-claude-code --skill algolia-automation62
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
22%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 description is too vague to effectively guide skill selection. It names the platform (Algolia) and integration method (Rube MCP/Composio) but fails to specify concrete capabilities or provide explicit trigger conditions. The procedural note about searching tools is implementation guidance rather than a useful description.
Suggestions
Add specific Algolia operations like 'manage search indices, add/update/delete records, configure search settings, query analytics'
Include a 'Use when...' clause with trigger terms like 'Algolia', 'search index', 'indexing records', 'search configuration'
Add natural user phrases such as 'search functionality', 'index management', or 'search analytics'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'Automate Algolia tasks' without specifying what tasks (indexing, searching, managing records, etc.). 'Always search tools first' is procedural guidance, not a capability description. | 1 / 3 |
Completeness | Partially addresses 'what' (Algolia tasks) but very weakly. Completely missing a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes 'Algolia', 'Rube MCP', and 'Composio' as relevant keywords, but lacks natural user terms like 'search index', 'indexing', 'search results', or specific Algolia operations users might request. | 2 / 3 |
Distinctiveness Conflict Risk | 'Algolia' and 'Rube MCP (Composio)' provide some distinctiveness, but 'Automate tasks' is generic enough to potentially overlap with other automation or MCP-related skills. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured skill that efficiently guides Claude through Algolia automation via Rube MCP. The workflow is clear with proper validation steps, and the content respects token budget. The main weakness is that tool call examples use placeholder syntax rather than fully concrete examples with realistic argument values.
Suggestions
Replace placeholder comments like '/* schema-compliant args from search results */' with a concrete example showing actual Algolia-specific arguments (e.g., index name, search query)
Add one complete end-to-end example showing a real Algolia operation (like searching an index) with actual parameter values
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, avoiding explanations of what Algolia is or how MCP works. Every section provides actionable information without padding. | 3 / 3 |
Actionability | Provides concrete tool call patterns with parameter examples, but uses pseudo-code style rather than fully executable code. The argument placeholders like '/* schema-compliant args */' reduce copy-paste readiness. | 2 / 3 |
Workflow Clarity | Clear 3-step workflow with explicit sequencing (discover → check connection → execute). Includes validation checkpoint for connection status before proceeding. | 3 / 3 |
Progressive Disclosure | Well-organized with clear sections, quick reference table, and external link to toolkit docs. Content is appropriately scoped for a single skill file without unnecessary nesting. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
90%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.