CtrlK
BlogDocsLog inGet started
Tessl Logo

file-locate-verify

Systematic workflow to resolve FileNotFoundError by locating and verifying file paths

56

Quality

63%

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

Fix and improve this skill with Tessl

tessl review fix ./benchmarks/gdpval/skills/file-locate-verify/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 body is a well-structured, self-contained workflow with an explicit verification checkpoint and actionable shell commands. Its main weaknesses are mild explanatory padding and Python examples built on non-standard tool wrappers rather than executable code.

Suggestions

Trim explanatory restatements of what `ls -la` and `list_dir` output mean, since Claude already knows these.

Replace or clarify the `list_dir`/`run_shell` wrapper calls with either real executable Python (e.g. subprocess) or clearly-labeled tool-call pseudocode so the examples are unambiguously actionable.

Add a brief error-recovery note for when `find` returns multiple or no results, to strengthen the verification feedback loop.

DimensionReasoningScore

Conciseness

Mostly efficient with concrete commands, but several lines explain what Claude already knows (e.g. "This reveals files in the immediate context..." and what `ls -la` confirms about permissions/size), which could be trimmed.

2 / 3

Actionability

The bash commands (`find . -iname ... 2>/dev/null`, `ls -la ...`) are concrete and copy-paste ready, but the Python examples rely on non-standard `list_dir`/`run_shell` wrappers that read more like pseudocode than executable code.

2 / 3

Workflow Clarity

A clear four-step sequence with an explicit verification checkpoint (Step 3) and a tied-together complete example; the guidance to only proceed after verification provides the required validation feedback loop.

3 / 3

Progressive Disclosure

A single, self-contained, single-purpose skill with well-organized sections (When to Use, Steps, Example, Pitfalls, Tools) and no bundle files; per the simple-skill guideline, well-organized sections warrant a top score when no external references are needed.

3 / 3

Total

10

/

12

Passed

Description

57%

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 is concrete, third-person, and tied to a distinctive error niche, but it lacks an explicit "Use when..." trigger clause and only covers a narrow set of actions. Adding explicit trigger guidance and a few more action verbs would lift the weaker dimensions.

Suggestions

Append an explicit trigger clause, e.g. "Use when you hit a FileNotFoundError or need to confirm a file's path before an operation that depends on it."

Broaden trigger terms to include natural variations like "file not found", "missing file", or "unknown file location".

Expand the action list slightly (e.g. "locate, verify, and confirm permissions of file paths") to strengthen specificity.

DimensionReasoningScore

Specificity

Names the domain (FileNotFoundError) and two concrete actions ("locating and verifying file paths"), but the action list is narrow and not comprehensive like the top anchor's multiple verbs.

2 / 3

Completeness

It answers "what" (resolve the error by locating and verifying paths) but the "when" is only implied via the error name; there is no explicit "Use when..." trigger clause, which caps completeness at 2.

2 / 3

Trigger Term Quality

"FileNotFoundError" is a natural term a user would cite, but coverage is limited to that single error name with no common variations (e.g. "file not found", "missing file", "path").

2 / 3

Distinctiveness Conflict Risk

Tying the skill to the specific FileNotFoundError niche gives it a clear, distinct trigger unlikely to fire for unrelated skills.

3 / 3

Total

9

/

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
HKUDS/OpenSpace
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.