search-config

Search indexing configuration and full-text search management

Quality

56%

Does it follow best practices?

Impact

Pending

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

Discovery

32%

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 provides a basic indication of the skill's domain but is too terse and lacks actionable detail. It fails to specify concrete capabilities, omits trigger guidance entirely, and uses generic terms that could cause selection conflicts with related skills.

Suggestions

Add a 'Use when...' clause with explicit triggers like 'Use when configuring search engines, creating indexes, managing Elasticsearch/Solr, or optimizing full-text search queries'.

List specific concrete actions such as 'create and configure search indexes, define analyzers and tokenizers, manage synonyms, optimize search performance'.

Include natural trigger terms users would say: 'Elasticsearch', 'Solr', 'search index', 'FTS', 'text search', 'search configuration'.

Dimension	Reasoning	Score
Specificity	Names the domain (search indexing, full-text search) and general actions (configuration, management), but lacks specific concrete actions like 'create indexes', 'configure analyzers', 'optimize queries', or 'manage synonyms'.	2 / 3
Completeness	Only addresses 'what' at a high level and completely lacks any 'when' guidance. No 'Use when...' clause or explicit trigger conditions are provided.	1 / 3
Trigger Term Quality	Includes some relevant terms ('search indexing', 'full-text search') but misses common variations users might say like 'Elasticsearch', 'Solr', 'search queries', 'index', 'FTS', or specific file/database types.	2 / 3
Distinctiveness Conflict Risk	The 'search' and 'configuration' terms are fairly generic and could overlap with database configuration skills, search API skills, or general config management. 'Full-text search' adds some specificity but not enough to clearly distinguish.	2 / 3
	Total	7 / 12 Passed

Implementation

79%

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 API reference that excels at providing concrete, executable code examples in a token-efficient manner. The main weaknesses are the lack of explicit workflows with validation steps for potentially destructive operations (rebuild, clear) and the monolithic structure that could benefit from splitting detailed backend configurations into separate files.

Suggestions

Add a workflow section showing the complete process for setting up search from scratch, including validation steps to verify the backend is working correctly

Include explicit validation/verification steps after destructive operations like rebuild and clear (e.g., 'After rebuild, verify with: await search.getStats() to confirm document counts')

Consider splitting backend-specific configuration details into separate reference files (e.g., ELASTICSEARCH.md, TYPESENSE.md) with the main skill providing quick-start guidance

Dimension	Reasoning	Score
Conciseness	The content is lean and efficient, presenting API references and commands without unnecessary explanation. It assumes Claude understands TypeScript, search concepts, and backend technologies without over-explaining.	3 / 3
Actionability	Provides fully executable TypeScript code examples that are copy-paste ready, with concrete configuration options, method signatures, and real usage patterns including filters, callbacks, and batch operations.	3 / 3
Workflow Clarity	While individual operations are clear, there's no explicit workflow for common multi-step processes like setting up a new search system or migrating backends. Missing validation checkpoints for operations like rebuild or clear that could be destructive.	2 / 3
Progressive Disclosure	Content is well-organized with clear sections and tables, but it's a monolithic reference document. Complex topics like backend configuration or embedding setup could benefit from separate detailed files with the main skill providing an overview.	2 / 3
	Total	10 / 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: 2a8c94e

Reviewed: 28 days 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.