Tessl • The management layer for AI agent skills

Blog Docs Log inGet started

SkillPublic

search-config

Search indexing configuration and full-text search management

Quality

64%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./src/skills/bundled/search-config/SKILL.md

Quality

Content

65%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 highly actionable with comprehensive executable examples, but it is a monolithic 258-line API reference that should be split into referenced files, repeats content, and lacks validation feedback loops for destructive/batch operations.

Suggestions

Move the bulk TypeScript API reference into a separate referenced file (e.g., references/API.md) and keep SKILL.md as a concise overview with one-level-deep links.

Add validation/verification steps for destructive and batch operations (e.g., verify index stats after rebuild, confirm before clear/clearAll, check latency after optimize).

De-duplicate the hybrid search example (shown in both the Search section and Hybrid Search Weights section) to tighten token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient code but includes repetition (hybridSearch appears in two sections) and lightly padded comments/best-practices bullets that could be tightened, fitting the score-3 anchor 'Mostly efficient but includes some unnecessary explanation or could be tightened'.	3 / 5
Actionability	It provides fully executable, copy-paste-ready TypeScript snippets and chat commands covering the common cases (index, search, hybrid, stats, rebuild, optimize, clear, backend config), matching the score-5 anchor.	5 / 5
Workflow Clarity	Operations are grouped by purpose and a loose best-practices list exists, but destructive/batch operations (rebuild, clear, clearAll) lack any validation or verification feedback loops, so per the rubric cap workflow_clarity cannot exceed 3.	3 / 5
Progressive Disclosure	At ~258 lines this exceeds the simple-skill threshold and inlines a large API reference that belongs in separate files; it is well-sectioned with headers (better than score 2) but has no external references to split content into, fitting score 3.	3 / 5
	Total	14 / 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 identifies a clear niche but relies on generic action verbs and omits any 'Use when...' trigger guidance, capping completeness. Trigger terms are relevant but lack common synonyms.

Suggestions

Add an explicit 'Use when...' clause naming concrete trigger situations (e.g., 'Use when configuring search backends, rebuilding indexes, or tuning full-text/hybrid search').

Replace generic verbs ('configuration', 'management') with specific actions like 'Configure search backends, rebuild indexes, and tune hybrid search weights'.

Include natural synonyms and file/term variations users might say ('search results', 'search backend', 'indexing', 'semantic search').

Dimension	Reasoning	Score
Specificity	The description names the domain ('Search indexing configuration and full-text search management') but the actions ('configuration', 'management') are generic rather than concrete, matching the score-2 anchor 'Names the domain but actions are minimal or generic'.	2 / 5
Completeness	A clear 'what' is present (configure search indexing, manage full-text search) but there is no 'when'/'Use when...' trigger clause, so per the rubric cap completeness stays at 3.	3 / 5
Trigger Term Quality	It includes some relevant natural keywords ('search indexing', 'full-text search') but misses common variations and synonyms users might say ('search results', 'search backend', 'search mode'), fitting the score-3 anchor for partial keyword coverage.	3 / 5
Distinctiveness Conflict Risk	Search-index configuration is a fairly specific niche with minimal overlap risk, fitting the score-4 anchor 'Mostly distinct; minor overlap risk with closely related skills', though the broad word 'search' leaves slight overlap with general search skills.	4 / 5
	Total	12 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: alsk1992/CloddsBot
Path: src/skills/bundled/search-config/SKILL.md
Revision: c930628

Reviewed: 1 month ago

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.

search-config

Table of Contents

Is this your skill?