CtrlK
BlogDocsLog inGet started
Tessl Logo

verify-all-deliverables

Ensure all required output files are created and verified before marking a task complete

55

Quality

61%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./benchmarks/gdpval/skills/verify-all-deliverables/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

81%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 is a well-engineered verification workflow with strong sequencing, validation, and feedback loops, plus concrete bash commands. Its main weakness is mild redundancy between the Purpose, Common Pitfalls, and Example Workflow sections.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence, giving the process and executable commands without explaining concepts Claude already knows; the Purpose and Common Pitfalls sections lightly duplicate the steps and could be trimmed.

4 / 5

Actionability

Concrete executable bash is provided ('ls -la', 'stat -c%s', a '[ -s "$file" ]' loop) plus an exact checklist format; placeholders like [filename.extension] keep it from being fully copy-paste ready.

4 / 5

Workflow Clarity

Five clearly sequenced steps with an explicit critical checkpoint, per-file and final validation, a troubleshoot-before-proceeding feedback loop, and a mandatory 'Only then declare complete' gate — a textbook checklist-with-validation workflow for a batch operation.

5 / 5

Progressive Disclosure

Single-purpose, well-organized with clear section headers and no need for external references; at ~75 lines it slightly exceeds the under-50-line simple-skill threshold, and the Example Workflow plus Common Pitfalls table partially restate the steps.

4 / 5

Total

17

/

20

Passed

Description

42%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 lacks explicit trigger guidance and relies on generic keywords, limiting discoverability and distinctiveness. Adding a 'Use when...' clause with concrete trigger phrases would materially raise completeness and trigger-term quality.

Suggestions

Append a 'Use when...' clause naming concrete triggers, e.g. 'Use when a task requires creating multiple output files (e.g. spreadsheet + document, report + summary) and you must confirm all are present before completing.'

Add natural user-facing keywords and synonyms such as 'deliverables', 'output files', 'verify files exist', and 'before declaring complete'.

Tighten specificity by naming the verification criteria (non-zero size / existence check) rather than the abstract 'verified'.

DimensionReasoningScore

Specificity

Names the domain (output files) and concrete actions ('created and verified', 'marking a task complete') but coverage is not comprehensive — no file types or verification methods are specified.

3 / 5

Completeness

The 'what' is clear ('Ensure all required output files are created and verified') but the 'when' is only weakly implied by 'before marking a task complete' and there is no explicit 'Use when...' clause, capping completeness at 3.

3 / 5

Trigger Term Quality

Keywords ('output files', 'verified', 'complete') are generic and miss the natural phrases a user would actually say; no 'Use when' trigger phrasing is present.

2 / 5

Distinctiveness Conflict Risk

It carves a niche (deliverable verification before completion) but the language is generic enough to overlap with other QA, checklist, or completion-gating skills.

3 / 5

Total

11

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
HKUDS/OpenSpace
Reviewed

Table of Contents

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.