CtrlK
BlogDocsLog inGet started
Tessl Logo

search

Search vault content by keyword using Grep. Zero dependencies — works in any vault without indexes or plugins. Groups results by directory for easy scanning.

53

Quality

60%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./vault-template/.claude/skills/search/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

70%

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

The content is well-structured and clearly sequenced for a read-only search skill, with a sensible fallback path and no external-reference complexity. Its main weaknesses are a redundant Grep block in Step 1 and a directory-exclusion step described in prose rather than as executable configuration.

Suggestions

Collapse the two Grep blocks in Step 1 into a single executable call and show the exclusion as concrete config (e.g. an explicit exclude/glob pattern or a post-filter step) rather than prose.

Clarify how to exclude hidden and template directories using an actual Grep parameter or a defined filtering step instead of the instruction to "Filter out results".

DimensionReasoningScore

Conciseness

The body is lean and avoids explaining concepts Claude already knows, but Step 1 repeats the same Grep config twice (once without and once with `path: .`), which is redundant and could be tightened.

2 / 3

Actionability

Provides a concrete Grep config and an explicit output template, but directory exclusion is given only as prose ("Filter out results from .claude/, .obsidian/, and Templates/") with no executable exclude mechanism, leaving key guidance incomplete.

2 / 3

Workflow Clarity

The four steps (search, group, present, suggest related) are clearly sequenced with a No-Results fallback for recovery; the task is read-only and non-destructive, so the destructive/batch cap on workflow clarity does not apply.

3 / 3

Progressive Disclosure

A single self-contained SKILL.md is organized into clear sections (Usage, How to Execute, No Results, Tips) with no nested references and no need for external bundle files, matching the simple-skill carve-out for well-organized content.

3 / 3

Total

10

/

12

Passed

Description

50%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description clearly states the skill's purpose and method with concrete actions, but it omits an explicit trigger/Use-when clause and its keywords lack the variation coverage needed for top scores. It is competent but not exemplary.

Suggestions

Add an explicit trigger clause, e.g. "Use when searching for text across vault notes, finding where a keyword or topic is mentioned, or locating notes by content."

Broaden trigger terms to include natural variations like "find", "locate", and "look up" alongside "search".

Reframe "using Grep" (a tool name) in terms of the user-facing outcome to reduce reliance on technical jargon for triggering.

DimensionReasoningScore

Specificity

Names the domain ("vault content"), the tool ("using Grep"), and concrete actions ("Search vault content by keyword", "Groups results by directory"), matching the score-2 anchor of naming domain and some actions without being comprehensive.

2 / 3

Completeness

Clearly states what the skill does but has no "Use when..." trigger clause or equivalent, which per the judging guidelines caps completeness at 2.

2 / 3

Trigger Term Quality

Contains natural terms users would say ("search", "keyword", "vault") but misses common variations like "find" or "locate", and "Grep" leans technical, matching the score-2 anchor.

2 / 3

Distinctiveness Conflict Risk

The "vault" framing and directory grouping form a niche, but "Search vault content by keyword" is broadly applicable and could overlap with general search or grep skills, matching the score-2 anchor.

2 / 3

Total

8

/

12

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

Total

15

/

16

Passed

Repository
ballred/obsidian-claude-pkm
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.