creativecodeology/meilisearch
Meilisearch search engine integration with the JavaScript/TypeScript SDK (v0.44+). Use when working with Meilisearch indexes, search queries, filters, facets, sorting, multi-search, tenant isolation, document sync, or search settings configuration. Triggers on: meilisearch client setup, index creation, addDocuments, search with filters, facetDistribution, tenant tokens, multi-search, ranking rules, filterable/sortable/searchable attributes. Use this skill any time the user mentions Meilisearch, search indexing, full-text search in their app, or asks about tenant-scoped search — even for simple tasks like 'add search to this page', because the skill contains critical multi-tenancy and filter syntax patterns that prevent data leaks.
94
94%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%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 is an excellent skill description that excels across all dimensions. It provides comprehensive coverage of capabilities, includes both natural user language and technical trigger terms, explicitly states when to use it, and is highly distinctive to Meilisearch. The inclusion of the rationale about multi-tenancy patterns preventing data leaks adds valuable context for skill selection.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'index creation, addDocuments, search with filters, facetDistribution, tenant tokens, multi-search, ranking rules, filterable/sortable/searchable attributes'. Uses third person voice throughout. | 3 / 3 |
Completeness | Clearly answers both what (Meilisearch SDK integration with specific capabilities) and when with explicit 'Use when...' and 'Triggers on:' clauses. Also explains why to use it even for simple tasks (multi-tenancy patterns that prevent data leaks). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'Meilisearch', 'search indexing', 'full-text search', 'add search to this page', 'tenant-scoped search', plus technical terms like 'addDocuments', 'facetDistribution' that developers would use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche: specifically targets Meilisearch (not generic search), mentions SDK version (v0.44+), and includes Meilisearch-specific terminology like 'tenant tokens', 'ranking rules', 'facetDistribution' that wouldn't conflict with other search tools. | 3 / 3 |
Total | 12 / 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 high-quality skill with excellent actionability and workflow clarity. The multi-tenant safety patterns and Common Pitfalls section add significant value for production use. Minor verbosity in explanatory text (like defining what an index is) could be trimmed to improve token efficiency.
Suggestions
Remove explanatory sentences that define concepts Claude already knows, such as 'An index holds documents. Think of it like a database table optimized for search.' and 'Key hierarchy: Master key > Admin keys...'
Consider condensing the filter syntax examples into a more compact reference table format rather than individual code blocks
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with good code examples, but includes some unnecessary explanations Claude would know (e.g., 'An index holds documents. Think of it like a database table optimized for search.') and could be tightened in places like the Core Concepts section. | 2 / 3 |
Actionability | Excellent executable code throughout with copy-paste ready TypeScript examples. Every concept is backed by concrete, runnable code snippets with specific syntax patterns and real-world usage examples. | 3 / 3 |
Workflow Clarity | Clear emphasis on async task handling with explicit waitForTask validation steps. The multi-tenant section provides defense-in-depth patterns with validation, and the Common Pitfalls section serves as a verification checklist for error-prone operations. | 3 / 3 |
Progressive Disclosure | Well-structured with clear sections progressing from setup to advanced topics. References to external files (references/advanced-search.md, references/error-handling.md) are clearly signaled at the end, maintaining one-level-deep navigation. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
Reviewed
Table of Contents