search-config

Search indexing configuration and full-text search management

Quality

40%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./src/skills/bundled/search-config/SKILL.md

Quality

Content

57%

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

The skill provides comprehensive, executable TypeScript API examples and clear chat commands, making it highly actionable. However, it reads as a flat API reference dump rather than a well-structured skill—it lacks workflow sequencing for multi-step or destructive operations, has no progressive disclosure via external files, and includes some unnecessary padding like obvious best practices and redundant tables.

Suggestions

Add explicit validation/confirmation steps for destructive operations like clear/clearAll and error handling guidance for batch indexing

Split the detailed API reference into a separate REFERENCE.md file, keeping SKILL.md as a concise overview with quick-start examples and links

Remove the 'Best Practices' section (obvious guidance Claude already knows) and the search backends/modes tables which duplicate information already shown in code examples

Add a sequenced workflow for common multi-step tasks like 'set up search from scratch' or 'migrate backends' with validation checkpoints

Dimension	Reasoning	Score
Conciseness	The content is reasonably structured but includes some unnecessary verbosity—the console.log examples for stats are padding, the best practices section states obvious things Claude already knows, and the search backends/modes tables add little value beyond what the code examples already show.	2 / 3
Actionability	The skill provides fully executable TypeScript code examples covering all major operations (indexing, searching, hybrid search, rebuilding, backend configuration). The chat commands are also concrete and copy-paste ready.	3 / 3
Workflow Clarity	Individual operations are clear, but there's no sequenced workflow for multi-step processes like rebuilding indexes or switching backends. Notably, destructive operations like 'clear' and 'clearAll' lack any validation or confirmation steps, and batch indexing has no error handling or verification guidance.	2 / 3
Progressive Disclosure	This is a monolithic wall of API reference content with no references to external files. The entire API surface is inlined in a single document with no navigation structure beyond section headers—content like backend configuration details and hybrid search tuning could be split into separate reference files.	1 / 3
	Total	8 / 12 Passed

Description

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.

The description is too terse and abstract, relying on broad nouns ('configuration', 'management') rather than concrete actions. It completely lacks a 'Use when...' clause, making it difficult for Claude to know when to select this skill. The domain is identifiable but insufficiently detailed to stand out among related skills.

Suggestions

Add a 'Use when...' clause with explicit trigger terms, e.g., 'Use when the user asks about setting up search indexes, configuring full-text search, Elasticsearch mappings, or search relevance tuning.'

Replace vague nouns with specific actions, e.g., 'Creates and configures search indexes, defines text analyzers and tokenizers, manages field mappings, and tunes search relevance scoring.'

Include common tool/technology names and file types users might mention, such as 'Elasticsearch', 'Solr', 'Lucene', 'OpenSearch', or specific config file formats.

Dimension	Reasoning	Score
Specificity	The description names a domain ('search indexing', 'full-text search') but does not list any concrete actions. 'Configuration' and 'management' are vague abstract nouns, not specific capabilities like 'create indexes', 'define analyzers', or 'tune relevance scoring'.	1 / 3
Completeness	The description weakly addresses 'what' (configuration and management) but completely lacks a 'when should Claude use it' clause. There are no explicit triggers or usage guidance, which per the rubric caps completeness at 2 at best, and the 'what' is too vague to even reach that level.	1 / 3
Trigger Term Quality	It includes some relevant keywords like 'search indexing', 'full-text search', and 'configuration' that users might mention, but misses common variations such as 'Elasticsearch', 'Solr', 'search queries', 'relevance', 'analyzers', 'tokenizers', or specific file/tool references.	2 / 3
Distinctiveness Conflict Risk	The 'full-text search' and 'search indexing' terms provide some specificity that distinguishes it from generic skills, but 'configuration' and 'management' are broad enough to overlap with database management, DevOps configuration, or other search-adjacent skills.	2 / 3
	Total	6 / 12 Passed

Validation

90%

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 — 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

Repository: alsk1992/CloddsBot
Commit: e71a5f6

Reviewed: 2 months 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.