CtrlK
BlogDocsLog inGet started
Tessl Logo

file-search

Modern file and content search using fd, ripgrep (rg), and fzf. Triggers on: fd, ripgrep, rg, find files, search code, fzf, fuzzy find, search codebase.

90

2.22x
Quality

Does it follow best practices?

Impact

80%

2.22x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

92%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A tight, highly actionable command reference that assumes Claude's competence and stays token-efficient. The one real defect is progressive disclosure: the sole referenced bundle file is missing, leaving the 'load for advanced patterns' path broken.

Suggestions

Create ./references/advanced-workflows.md (git integration, shell functions, power workflows) so the referenced 'Additional Resources' path resolves, or remove the pointer if no such file is intended.

Eliminate the minor duplication between the inline code blocks and the Quick Reference table, e.g. keep the table for recall and trim redundant flag comments in the prose sections.

DimensionReasoningScore

Conciseness

The body is lean and code-first with terse inline comments, assuming Claude's competence and avoiding any explanation of what fd/rg/fzf are; the only minor redundancy is the Quick Reference table re-listing commands already shown.

3 / 3

Actionability

Every example is real, executable shell (e.g. 'fd -e py -x rg "async def" {}', 'fd -e ts | fzf -m | xargs code') with specific flags and pipe combinations, copy-paste ready.

3 / 3

Workflow Clarity

This is a simple single-purpose reference skill whose single action (look up a command, run it) is unambiguous and organized into clear per-tool sections; no destructive or batch operations require validation checkpoints.

3 / 3

Progressive Disclosure

The body is a clean overview with a clearly signaled one-level pointer ('For detailed patterns, load: ./references/advanced-workflows.md'), but that referenced file does not exist in the bundle, so navigation leads to a dead end and undermines the disclosure structure.

2 / 3

Total

11

/

12

Passed

Description

90%

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 names its tools, states its purpose, and supplies an explicit trigger clause with natural user terms. Its main weakness is specificity: it describes the capability at a high level rather than listing concrete search actions.

Suggestions

Add concrete actions to the capability statement, e.g. 'Find files by name/type and search code content with fd, ripgrep, and fzf' to reach full specificity.

Consider folding a couple of high-frequency trigger verbs (e.g. 'grep', 'locate files') into the trigger list to broaden natural-language coverage.

DimensionReasoningScore

Specificity

Names the tools and domain ('file and content search using fd, ripgrep (rg), and fzf') but describes the capability at a high level rather than enumerating multiple concrete actions like 'find by name' or 'search by type'.

2 / 3

Completeness

It states what the skill does (file and content search with fd/rg/fzf) and provides an explicit 'Triggers on:' clause covering when to use it, answering both what and when.

3 / 3

Trigger Term Quality

The 'Triggers on:' clause lists natural, user-spoken terms (find files, search code, fuzzy find, search codebase) plus the tool names, giving good coverage of what a user would actually say.

3 / 3

Distinctiveness Conflict Risk

Tool-specific triggers (fd, rg, fzf) carve a clear niche for this search skill, making it unlikely to fire for unrelated skills; the mild genericness of 'search codebase' is not enough to drop it.

3 / 3

Total

11

/

12

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
NeverSight/skills_feed
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.