CtrlK
BlogDocsLog inGet started
Tessl Logo

ctx-index

Index a local file or directory into context-mode's persistent FTS5 knowledge base so future ctx_search calls can retrieve focused snippets without rereading raw files. Trigger: /context-mode:ctx-index

70

Quality

86%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

87%

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-crafted, concise skill that provides clear, actionable guidance for indexing content into a knowledge base. Its main weakness is the lack of a validation/verification step after indexing — Claude should confirm the operation succeeded and handle potential errors. The safety section is a strong addition that provides clear guardrails.

Suggestions

Add a validation step after indexing (e.g., verify file/section count returned, handle errors if indexing fails or returns unexpected results).

DimensionReasoningScore

Conciseness

Every line serves a purpose. No unnecessary explanations of what indexing is or how FTS5 works. The skill assumes Claude knows the concepts and focuses on the specific tool usage and constraints.

3 / 3

Actionability

Provides concrete, executable code examples for both MCP tool invocation and CLI fallback. Includes specific parameter names, values, and a clear example of how to report results back to the user.

3 / 3

Workflow Clarity

Steps are listed in a logical sequence (prefer MCP → ask for path if needed → use path not content → index → fallback → report), but there's no validation checkpoint after indexing. The skill doesn't instruct Claude to verify the index succeeded or handle errors/failures from the indexing operation.

2 / 3

Progressive Disclosure

For a simple, single-purpose skill under 50 lines with no need for external references, the content is well-organized into clear sections (Instructions, Safety) with appropriate depth. No monolithic walls of text or unnecessary nesting.

3 / 3

Total

11

/

12

Passed

Description

85%

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 a well-crafted, technically specific description that clearly identifies what the skill does (indexing files into an FTS5 knowledge base) and when to use it (via the explicit trigger command). Its main weakness is that the trigger terms are heavily technical/internal jargon, which may not match natural user language patterns, though the explicit command trigger partially compensates for this.

Suggestions

Add more natural-language trigger terms that users might say, such as 'add files to search index', 'make files searchable', or 'index for later retrieval'.

DimensionReasoningScore

Specificity

The description lists concrete actions: 'Index a local file or directory', 'persistent FTS5 knowledge base', and 'retrieve focused snippets without rereading raw files'. These are specific, concrete capabilities.

3 / 3

Completeness

It clearly answers 'what' (index a local file or directory into a persistent FTS5 knowledge base) and 'when' (the explicit trigger '/context-mode:ctx-index' is provided, and the purpose 'so future ctx_search calls can retrieve focused snippets' clarifies the use case). The trigger line serves as an explicit 'when' clause.

3 / 3

Trigger Term Quality

It includes some relevant technical terms like 'index', 'FTS5', 'ctx_search', 'ctx-index', and 'knowledge base', but these are fairly technical. Users might naturally say 'index files' or 'search files', but terms like 'FTS5' and 'ctx_search' are internal/jargon. Missing common variations like 'search', 'find', 'lookup', or 'add to index'.

2 / 3

Distinctiveness Conflict Risk

The description is highly specific to a particular system ('context-mode', 'FTS5 knowledge base', 'ctx_search', 'ctx-index'). It has a clear niche and is very unlikely to conflict with other skills due to the specific command trigger and technical domain.

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.

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

Passed

Repository
mksglu/context-mode
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.