delegated-file-edit-verification

Verify delegated file-edit results directly in the target workspace before accepting success, and rerun with absolute paths if the delegate's report conflicts with reality.

Quality

62%

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/delegated-file-edit-verification/SKILL.md

Quality

Content

66%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 body delivers a well-sequenced, validated workflow with executable code examples, but is noticeably verbose due to heavy restatement across redundant sections, and is a long monolithic file with minor organizational gaps.

Suggestions

Consolidate the redundant 'Verification checklist', 'Anti-patterns to avoid', 'Why this works', and 'Success criterion' sections — they largely restate the 7-step procedure and core principle.

Remove the empty '## Examples' header (line 157) and unify the subsequent '## Example:' subsections under it for cleaner structure.

Add a brief database-verification example or drop 'databases' from the scoped formats so coverage matches the stated scope.

Dimension	Reasoning	Score
Conciseness	For a single-concept skill ('verify delegated edits; rerun with absolute paths on mismatch'), the ~275-line body restates the same idea across the procedure, verification checklist, anti-patterns, 'Why this works', and 'Success criterion' sections — several padded, redundant sections rather than lean guidance.	2 / 5
Actionability	Provides copy-paste ready, executable shell commands (ls, stat, find, test, head) and Python snippets (csv, openpyxl) covering the common cases, with only a minor coverage gap (databases are mentioned but not exemplified) and a slightly awkward header comprehension in the spreadsheet example.	4 / 5
Workflow Clarity	A clearly sequenced 7-step procedure with explicit validation checkpoints (steps 3 and 7), a feedback loop for error recovery (steps 5–7: detect conflict, rerun, re-verify), and a verification checklist — matching the top anchor.	5 / 5
Progressive Disclosure	Well-organized into clearly headed sections and self-contained with no external references needed, but it is a long monolithic file with minor structural issues (an empty '## Examples' header followed by separate '## Example:' headers) and some inline content that could be tightened.	4 / 5
	Total	15 / 20 Passed

Description

58%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 states a clear, specific purpose with concrete actions and a distinct niche, but lacks an explicit 'Use when...' trigger clause and relies on somewhat specialized rather than natural user keywords.

Suggestions

Add an explicit 'Use when...' clause naming concrete trigger situations, e.g. 'Use when a sub-agent or delegated tool reports it created or modified a file and correctness matters.'

Include more natural trigger terms a user would actually say (e.g. 'check the delegate's work', 'verify file edits', 'confirm the file was written') alongside the technical phrasing.

Consider adding common file extensions or formats (e.g. .xlsx, .csv) to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (delegated file-edit verification) and two concrete actions — 'Verify delegated file-edit results directly in the target workspace' and 'rerun with absolute paths' — which is above the generic two-action anchor but short of comprehensive multi-action coverage.	4 / 5
Completeness	The 'what' is clearly stated, but there is no explicit 'Use when...' trigger clause; the 'when' is only weakly implied via the conditions 'before accepting success' and 'if the delegate's report conflicts with reality', capping completeness at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	Relevant keywords like 'delegated file-edit', 'target workspace', and 'absolute paths' are present but specialized; common natural synonyms or file extensions a user would say are missing.	3 / 5
Distinctiveness Conflict Risk	The 'delegated file-edit verification' niche is distinct and unlikely to trigger for unrelated skills, with only minor overlap risk against general verification/validation skills.	4 / 5
	Total	14 / 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/delegated-file-edit-verification/SKILL.md
Commit: 3827781

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