file-locate-verify

Systematic workflow to resolve FileNotFoundError by locating and verifying file paths

Quality

60%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

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

Quality

Content

67%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.

The content delivers a clear, actionable, validated four-step workflow with concrete commands and a worked example. It is somewhat over-explanatory in places and lacks an explicit error-recovery feedback loop.

Suggestions

Trim basic explanations Claude already knows (e.g. what 2>/dev/null does, what ls -la reveals) to tighten conciseness.

Add a feedback loop: what to do when find returns no results or when verification shows the file is missing or unreadable.

Remove or compress the 'Complete Example' since it restates the step-by-step procedure, reducing redundancy.

Dimension	Reasoning	Score
Conciseness	The body explains basics Claude already knows ('Redirect stderr with 2>/dev/null to suppress permission errors', 'ls -la reveals if you have read/write access') and includes a redundant 'Complete Example' that restates the steps, fitting 'mostly efficient but includes some unnecessary explanation'; not a 2 because the structure is still purposeful and not heavily padded.	3 / 5
Actionability	Provides concrete executable commands (`find . -iname "filename.pdf" 2>/dev/null`, `ls -la /full/path/to/discovered/file.pdf`, `list_dir(path=".")`) plus a worked end-to-end example, matching 'mostly executable guidance with minor gaps'; not a 5 because the find-result parsing (`split('\n')[0]`) is fragile and placeholders require substitution.	4 / 5
Workflow Clarity	A clear four-step sequence (check dir → find → verify → execute) with an explicit validation checkpoint in Step 3 ('Before executing any operations... verify it exists'), matching 'clear sequence with most checkpoints present'; not a 5 because there is no error-recovery feedback loop for cases where find returns nothing or verification fails.	4 / 5
Progressive Disclosure	No bundle files exist and none are needed; the single self-contained file is well-organized into When to Use, Step-by-Step, Complete Example, Pitfalls, and Related Tools sections, matching 'good structure; most content appropriately placed'; not a 5 because the file exceeds the ~50-line simple-skill threshold and the Complete Example duplicates the procedure rather than being split out.	4 / 5
	Total	15 / 20 Passed

Description

53%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.

The description clearly states what the skill does but omits any explicit 'Use when' trigger guidance, capping completeness. Trigger coverage relies on a single technical term without common synonyms.

Suggestions

Add an explicit trigger clause, e.g. 'Use when you hit a FileNotFoundError or need to confirm a file path before operating on it.'

Broaden trigger terms with natural synonyms like 'file not found', 'missing file', or 'cannot locate file' alongside 'FileNotFoundError'.

Consider naming one more concrete action (e.g. 'checking permissions') to lift specificity above the 1-2 action band.

Dimension	Reasoning	Score
Specificity	Quotes 'resolve FileNotFoundError by locating and verifying file paths' — names the domain and two concrete actions (locating, verifying) but offers no broader coverage, matching the '1-2 concrete actions, not comprehensive' anchor; not a 4 because it lists only two actions with minor gaps rather than several.	3 / 5
Completeness	It states a clear 'what' ('systematic workflow to resolve FileNotFoundError by locating and verifying file paths') but provides no 'Use when...' trigger clause, so per the rubric's missing-trigger cap it cannot exceed 3; not a 4 because 'when' is entirely absent rather than weakly implied.	3 / 5
Trigger Term Quality	The single trigger keyword 'FileNotFoundError' is relevant but the description omits natural synonyms users might say ('file not found', 'missing file', 'can't find file'), fitting the 'some relevant keywords but missing common variations' anchor rather than the comprehensive 4.	3 / 5
Distinctiveness Conflict Risk	'FileNotFoundError' is a specific niche trigger and 'locating and verifying file paths' scopes it reasonably, matching 'mostly distinct; minor overlap risk'; not a 5 because the phrase 'locating and verifying file paths' is generic enough to overlap with general file-operation skills.	4 / 5
	Total	13 / 20 Passed

Validation

100%

Warnings & errors only

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: HKUDS/OpenSpace
Path: benchmarks/gdpval/skills/file-locate-verify/SKILL.md
Commit: 3827781

Reviewed: 10 days ago

Table of Contents

Discovery Implementation Validation

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.