prioritize-context-data

Ensures agents check and use provided context files for data before attempting external searches.

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/prioritize-context-data/SKILL.md

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 a clear, well-organized instruction skill with a strong sequenced workflow and verification gate. Its weaknesses are mild verbosity in the Warnings section and slightly hedged, non-executable tool guidance.

Suggestions

Trim the Warnings section: drop explanations Claude already knows (local files are faster than scraping; users expect files to be used) and keep only novel cautions.

Tighten tool guidance from "appropriate tools (e.g., read_file, pandas, pdf_reader)" to a single recommended tool per file type with a one-line usage snippet.

Consider merging the redundant gate statements between the Critical Rule, step 3, and step 5 into one explicit "Confirm the file lacks the data before searching" checkpoint.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and well-structured, but the Warnings section and parts of the Objective restate things Claude already knows (local files are faster than web scraping, users expect attached files to be used), so it is not fully lean, fitting anchor 2.	2 / 3
Actionability	Steps name concrete tools (read_file, pandas, pdf_reader) and give a citation example, but the guidance is hedged ("appropriate tools (e.g., ...)") with no directly executable code, matching anchor 2's "some concrete guidance but incomplete."	2 / 3
Workflow Clarity	Five steps are clearly sequenced with an explicit gate in step 3 ("Do not proceed to web search until you have confirmed the file lacks the necessary information") and a closing checklist that acts as a verification loop, matching anchor 3.	3 / 3
Progressive Disclosure	This is a single self-contained file with no bundle files referenced, and it is organized into clearly labeled sections (Objective, Critical Rule, Workflow Steps, Checklist, Example Usage, Warnings), satisfying the simple-skill anchor 3 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 is a clear, third-person statement of intent but stays generic: it lacks concrete enumerated actions, natural trigger terms, and an explicit "Use when" clause. It is adequate but not distinctive or self-triggering.

Suggestions

Add an explicit "Use when..." trigger clause naming scenarios users would say, e.g. "Use when a task provides attached data files (CSV, XLSX, PDF) and you need figures or facts from them."

Replace generic verbs with concrete actions, e.g. "Inspect, read, and extract data from provided context files before falling back to web search."

Include natural trigger terms users actually say ("attached spreadsheet", "provided CSV", "the file I gave you") to improve distinctiveness and recall.

Dimension	Reasoning	Score
Specificity	It names the domain ("provided context files for data") and two actions ("check and use") but the verbs are generic rather than a comprehensive list of concrete actions, matching anchor 2 rather than the multi-action anchor 3.	2 / 3
Completeness	The description states what the skill does but provides only an implied trigger (when context files are present) with no explicit "Use when..." clause, which per the guidelines caps completeness at 2.	2 / 3
Trigger Term Quality	Terms like "context files", "data", and "external searches" are relevant but limited and miss common user phrasings, fitting anchor 2's "some relevant keywords but missing common variations" rather than full coverage.	2 / 3
Distinctiveness Conflict Risk	"Prioritize provided context files over external searches" is a recognizable niche but the framing is general enough that it could overlap with other file-handling or research skills, matching anchor 2.	2 / 3
	Total	8 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: HKUDS/OpenSpace
Path: benchmarks/gdpval/skills/prioritize-context-data/SKILL.md
Commit: c5a9c4b

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