working-directory-resolution

Resolve file access failures by changing to the correct working directory before command execution

Quality

67%

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/working-directory-resolution/SKILL.md

Quality

Content

85%

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

The body is highly actionable with concrete, executable bash examples and a clear single-pattern workflow supported by a fallback sequence. Its main weakness is mild redundancy across the symptoms, when-to-apply, and pitfalls sections that could be tightened.

Suggestions

Consolidate the overlapping "Problem Symptoms", "When to Apply", and "Common Pitfalls" sections to remove repeated examples and reduce tokens.

Trim the opening explanatory paragraph that restates the working-directory concept Claude already knows.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete bash examples, but sections like "Problem Symptoms", "When to Apply", and the "Common Pitfalls" table overlap with each other, and the opening paragraph explains a concept Claude already understands, fitting the score-2 anchor.	2 / 3
Actionability	It provides multiple copy-paste-ready, executable bash commands (e.g., `cd /workspace/project && cat config.json`, `[ -d /workspace/project ] && cd /workspace/project && ls`) plus a run_shell example, matching the fully-executable score-3 anchor.	3 / 3
Workflow Clarity	This is a simple single-purpose pattern whose core action (prepend `cd`) is unambiguous, and it includes a numbered fallback sequence; per the simple-skills note, workflow clarity can score 3 for a clear single action without destructive/batch validation needs.	3 / 3
Progressive Disclosure	The skill is a single self-contained file with clear section headers and no need for external references (no bundle files exist), so the well-organized section structure satisfies the score-3 anchor for simple skills without nested references.	3 / 3
	Total	11 / 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 specific and grammatically clean in third person, but it lacks an explicit usage trigger and relies on somewhat technical phrasing rather than natural user terms. Adding a "Use when..." clause with common error strings would raise completeness and trigger quality.

Suggestions

Add an explicit trigger clause such as "Use when read_file or shell commands report 'file not found' or 'No such file or directory' for files that should exist."

Include natural user-facing terms (e.g., "file not found", "can't find file", "wrong directory") alongside the technical phrasing.

Narrow the trigger from the generic "file access failures" to working-directory-specific symptoms to reduce overlap with other file skills.

Dimension	Reasoning	Score
Specificity	The description names a concrete domain ("file access failures") and a specific mechanism ("changing to the correct working directory before command execution"), but it lists a single action rather than multiple specific concrete actions, matching the score-2 anchor.	2 / 3
Completeness	It clearly states what the skill does but provides no explicit "Use when..." trigger clause; per the guidelines a missing explicit trigger caps completeness at 2 even though the "when" is faintly implied by "file access failures".	2 / 3
Trigger Term Quality	Relevant keywords like "file access failures" and "working directory" are present, but common natural variations a user would actually say (e.g., "file not found", "No such file or directory") are missing, so it falls short of full coverage.	2 / 3
Distinctiveness Conflict Risk	The working-directory mechanism is a distinct niche, but the broad trigger phrase "file access failures" could overlap with general file-handling skills, placing it at the score-2 "somewhat specific but could still overlap" anchor.	2 / 3
	Total	8 / 12 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/working-directory-resolution/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.