CtrlK
BlogDocsLog inGet started
Tessl Logo

search

Use when the user wants to find prior work, checkpoints, or agent conversations by topic, repo, branch, author, or recent time window

67

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

83%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 compact, executable skill body: copy-paste-ready CLI commands, a clear numbered process with a fallback, and clean sectioning with no nested references. The only gap is the absence of an explicit validate-then-retry checkpoint, though the read-only operations make that lower-stakes.

DimensionReasoningScore

Conciseness

The body is largely lean — executable commands, terse heuristics, and short failure-mode bullets with little over-explanation of concepts Claude already knows — with only minor instances ('followed by a blank line, then the content') that could be trimmed.

4 / 5

Actionability

Provides copy-paste-ready, fully executable commands for every step (`entire search ... --json`, filtered variants, `entire explain --checkpoint ... --full --no-pager`, plus a `--raw-transcript` fallback) covering the common cases.

5 / 5

Workflow Clarity

The Process section is a clearly numbered sequence (search → review/summarize → drill into a hit) with a real fallback path for `--full` failure, but it lacks an explicit validate/retry checkpoint and the operations are read-only so the destructive-cap doesn't apply — minor checkpoint gaps keep it at 4.

4 / 5

Progressive Disclosure

Under 50 lines, no bundle files exist, and content is organized into well-signaled sections (When to Use, Process, Search Heuristics, Failure Modes) with no nested references — meeting the simple-skill exception for a top score.

5 / 5

Total

18

/

20

Passed

Description

78%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 trigger-forward description that clearly answers both what and when, with strong natural keyword coverage and concrete filter dimensions. It is slightly thin on enumerated concrete actions beyond 'find', keeping specificity from the top level.

Suggestions

Lead with the concrete actions (e.g., 'Find prior agent checkpoints and conversations, then open full transcripts') before the filter list to lift specificity.

Add a couple of user-synonym phrases already in the body ('search past work', 'find the previous implementation') into the description itself.

DimensionReasoningScore

Specificity

Names the domain (finding prior work/checkpoints/conversations) and the concrete filter dimensions ('topic, repo, branch, author, or recent time window'), but lists no concrete actions beyond 'find' itself — comparable to 'Names domain and 1-2 concrete actions, but not comprehensive'.

3 / 5

Completeness

Explicitly states the 'when' via an opening 'Use when the user wants to...' clause with concrete triggers, and the 'what' (find prior work/checkpoints/conversations by named dimensions) — both are present and concrete.

5 / 5

Trigger Term Quality

Strong natural keyword coverage ('prior work', 'checkpoints', 'agent conversations', 'repo', 'branch', 'author', 'recent time window') that mirrors phrasing users would actually say, though a few common synonyms ('search past work', 'history') live only in the body.

4 / 5

Distinctiveness Conflict Risk

The 'prior work, checkpoints, agent conversations' niche is clearly distinct from most skills, but the bare 'search' name plus 'find prior work' could overlap with session-handoff and general search until the conversation/checkpoint scope disambiguates — minor overlap risk.

4 / 5

Total

16

/

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
SnowingFox/ai-skills
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.