prioritize-reference-files

Ensures agents read and use provided reference files before searching or fabricating data

Quality

56%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./benchmarks/gdpval/skills/prioritize-reference-files/SKILL.md

Quality

Content

56%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 skill delivers a clear, mostly actionable workflow with a strong verification mindset, but it pads sections Claude could infer and inlines reference-like material rather than splitting it out. The primary read_file examples read as pseudocode rather than executable calls.

Suggestions

Replace the placeholder read_file(filetype=..., file_path=...) calls with the actual tool invocation syntax (or clearly mark them as schema illustrations) so guidance is copy-paste executable.

Move the file-type read examples and the .docx fallback runbook into a bundled reference file (e.g. references/docx-extraction.md) and link to it, keeping SKILL.md a lean overview.

Trim the anti-patterns list and verification checklist where they merely restate the workflow, to reduce token cost.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and well-sectioned, but sections like the verbose anti-patterns list, the checklist restating the workflow, and explanatory lines such as 'The agent will attempt multiple extraction methods' add padding Claude could infer.	3 / 5
Actionability	It offers concrete fallback commands (unzip/grep) and an example, but the primary 'read_file(filetype=..., file_path=...)' calls are pseudocode-style placeholders that are not executable as written, leaving key steps incomplete.	3 / 5
Workflow Clarity	A clear 5-step sequence with an explicit verify-extraction fallback loop and a closing checklist; the operations are read/extract (non-destructive) so the missing validation cap does not apply, though the fallback flow is slightly more narrative than checkpointed.	4 / 5
Progressive Disclosure	No bundle files exist and the single body is reasonably sectioned, but a sizable reference-style block (file-type read_file snippets and the .docx fallback runbook) is inlined that would fit a separate reference; navigation is just sequential headings with no file pointers.	3 / 5
	Total	13 / 20 Passed

Description

37%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 conveys a clear purpose but is thin on concrete actions and natural trigger terms, and it omits an explicit 'Use when...' clause. It is distinct enough to avoid gross conflicts yet broad enough to risk overlap with general file skills.

Suggestions

Add concrete actions: e.g. 'Read, parse, and extract data from attached .xlsx/.csv/.json/.pdf/.docx files before searching the web or generating synthetic data.'

Include an explicit trigger clause: 'Use when the task mentions attached, provided, or reference files (e.g. see file, attached spreadsheet, provided .xlsx).'

Add natural synonyms and extensions users say ('attached', 'provided', 'see file', file extensions) to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	The phrase 'read and use provided reference files' names a domain but the actions are minimal and generic — it states only that agents should read/use files, with no concrete capabilities (parse, extract, validate) enumerated.	2 / 5
Completeness	It has a clear 'what' (ensures agents read/use reference files first) but no 'when'/Use-when clause; per the guidelines, a missing explicit trigger caps completeness at 3, and the 'when' is only weakly implied by 'before searching or fabricating data'.	3 / 5
Trigger Term Quality	'reference files' is one generic keyword; the description lacks the natural phrases and file extensions users actually say (e.g. 'attached spreadsheet', 'provided .xlsx', 'see file'), so natural trigger coverage is thin.	2 / 5
Distinctiveness Conflict Risk	'reference files' is fairly broad and could overlap with many file-handling skills, but the 'before searching or fabricating' framing carves out a somewhat specific niche, so it is distinct but with moderate overlap risk.	3 / 5
	Total	10 / 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/prioritize-reference-files/SKILL.md
Commit: 3827781

Reviewed: 9 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.