CtrlK
BlogDocsLog inGet started
Tessl Logo

ccc

This skill should be used when code search is needed (whether explicitly requested or as part of completing a task), when indexing the codebase after changes, or when the user asks about ccc, cocoindex-code, or the codebase index. Trigger phrases include 'search the codebase', 'find code related to', 'update the index', 'ccc', 'cocoindex-code'.

72

Quality

88%

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

93%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 well-crafted skill body: lean, executable, and properly split across reference files with clear navigation. The only gap is the absence of an explicit validation checkpoint in the core search workflow, which keeps workflow clarity at 4.

DimensionReasoningScore

Conciseness

Lean and operational throughout — it gives only the specifics Claude lacks (flags, pagination, freshness heuristics, init retry flow) without explaining what semantic search or indexing is. Every section earns its tokens; no padded concept explanations. Not below 5 because there is no over-explanation to trim.

5 / 5

Actionability

Provides copy-paste-ready commands for the common cases — `ccc search <query>`, language/path filtering, `--offset/--limit` pagination, `ccc init`/`ccc index`/`ccc search --refresh`, plus a `sed` fallback for terminals. Examples are executable and cover the typical workflow. Not below 5 because no key command is left to pseudocode.

5 / 5

Workflow Clarity

The Ownership section gives a clear sequenced feedback loop: init error → `ccc init` → `ccc index` → retry, with index-freshness guidance as an implicit checkpoint. Not a 5 because the main search workflow lacks an explicit validation/verification step (e.g., checking result relevance before acting); not a 3 because a real error-recovery checkpoint is present.

4 / 5

Progressive Disclosure

SKILL.md is a concise overview with one-level-deep, clearly signaled references to real bundle files — [management.md](references/management.md) and [settings.md](references/settings.md) — each in a dedicated section. Content is appropriately split and navigation is easy; no nested or buried references.

5 / 5

Total

19

/

20

Passed

Description

83%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 strong description that clearly states both capability and trigger conditions with concrete, natural phrases and tool-name disambiguation. Its main limitation is slightly narrow action variety and some overlap risk from generic search phrasing.

DimensionReasoningScore

Specificity

Names the domain (code search/indexing) and several concrete actions — "code search", "indexing the codebase after changes", "update the index", "find code related to" — with only minor coverage gaps. Not a 5 because the action variety is narrow (search + index variants) rather than comprehensive.

4 / 5

Completeness

Explicitly answers both what (semantic code search and index management) and when ("This skill should be used when code search is needed... when indexing the codebase after changes, or when the user asks about ccc...") with concrete trigger phrases. Has an explicit 'Use when...' clause, so no cap applies.

5 / 5

Trigger Term Quality

Includes natural trigger phrases users would say ("search the codebase", "find code related to", "update the index") plus tool-name variants ("ccc", "cocoindex-code"), giving good keyword coverage. Not a 5 because common synonyms/variations (e.g. "grep", "look for", "where is") are missing.

4 / 5

Distinctiveness Conflict Risk

The tool-specific triggers ("ccc", "cocoindex-code", "codebase index") carve a clear niche, but generic phrases like "search the codebase" and "find code related to" create minor overlap risk with other code-search skills. Not a 5 due to that residual overlap; not a 3 because the named-tool triggers make it clearly more distinct.

4 / 5

Total

17

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
cocoindex-io/cocoindex-code
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.