CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

86%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.

A lean, highly actionable single-purpose skill: every step is concrete, sequencing is clear, and safety bounds are sensible. The only improvements are showing the exclude flag syntax and adding an explicit post-index verification step.

Suggestions

Show the exclude flag in a real call (e.g., `ctx_index({ path: ".", exclude: ["node_modules", "dist"] })` and the CLI `--exclude` form) instead of only naming it in the Safety section.

Add an explicit verification step after indexing, e.g., run `ctx_search` for a known snippet and confirm it returns focused results before reporting success.

Replace the placeholder `queries: ["..."]` with one realistic query example so the search command is copy-paste ready.

DimensionReasoningScore

Conciseness

Every line instructs ("Prefer the `ctx_index` MCP tool when it is available", "Use `path`, not large inline `content`, so file bytes do not enter the conversation") with no concept explanation or padding, matching anchor 5 — lean, efficient, and assuming Claude's competence.

5 / 5

Actionability

Concrete, mostly executable guidance: a complete `ctx_index({ path, source, maxDepth, maxFiles })` call, the CLI fallback `context-mode index . --source project:<name>`, and a `ctx_search` example. It sits at anchor 4 rather than 5 because `exclude`/`--exclude` is named in the Safety section but never shown in syntax, and the search example uses a bare `["..."]` placeholder — minor gaps.

4 / 5

Workflow Clarity

Six clearly sequenced steps with a reporting checkpoint ("Report the indexed source label, file count or section count") and a pre-flight guard ("ask the user before raising `maxFiles` above 500") match anchor 4. It is below anchor 5 because there is no explicit validate-that-search-returns-expected-snippets loop after indexing.

4 / 5

Progressive Disclosure

The body is under 50 lines, needs no external references (none exist in the bundle), and is well organized into Instructions, code examples, and Safety sections, which per the rubric's simple-skill guideline merits a 5.

5 / 5

Total

18

/

20

Passed

Description

67%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.

A specific, jargon-accurate description with a clear "what" and an explicit slash-command trigger, weakened mainly by trigger phrasing that users would not naturally say. Adding natural-language "Use when..." clauses and synonyms would lift trigger quality and completeness.

Suggestions

Add a natural-language trigger clause such as "Use when the user asks to index, make searchable, or build a search index of a file, directory, or repository."

Include user-facing synonyms (e.g., "search index", "knowledge base", "snippet search") so the description matches how users actually phrase the request, not just the slash command.

Consider mentioning one or two more concrete capabilities (e.g., excluding noisy paths, bounded repository indexing) to round out coverage toward the top specificity anchor.

DimensionReasoningScore

Specificity

The description names concrete actions with a precise mechanism — "Index a local file or directory into context-mode's persistent FTS5 knowledge base" and "retrieve focused snippets without rereading raw files" — listing several specific actions with only minor coverage gaps, matching anchor 4. It falls short of anchor 5 because it does not enumerate multiple distinct operations.

4 / 5

Completeness

It clearly answers "what" (index files into a persistent searchable knowledge base) and provides explicit trigger guidance via "Trigger: /context-mode:ctx-index", so the missing-trigger cap of 3 does not apply. It matches anchor 4 rather than 5 because the "when" is a slash-command only and lacks concrete natural-language "Use when..." trigger phrases.

4 / 5

Trigger Term Quality

Relevant keywords like "index", "file or directory", "search", and "snippets" are present, but the phrasing leans on technical jargon ("persistent FTS5 knowledge base", "ctx_search") and the trigger line is a slash command rather than natural user phrasing, matching anchor 3. It is not 4 because common natural variations (e.g., "make this repo searchable", "index this project") are missing.

3 / 5

Distinctiveness Conflict Risk

The description is tightly bound to the context-mode ecosystem ("context-mode's", "ctx_search", "/context-mode:ctx-index"), giving it a clear niche with only minor overlap risk against generic indexing or search skills — anchor 4. It is not 5 because broad terms like "index" and "search" alone could overlap with other retrieval-oriented skills.

4 / 5

Total

15

/

20

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

Validation for skill structure

No warnings or errors.

Repository

mksglu/context-mode

Path

skills/ctx-index/SKILL.md

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.