CtrlK
BlogDocsLog inGet started
Tessl Logo

deliverable-completion

Clarifies that file creation tasks are complete when the deliverable is successfully written—no submission step required

50

Quality

55%

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/deliverable-completion/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

60%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 well-structured and actionable with a clear verify-then-declare workflow, but it is noticeably verbose for a single-point skill, re-explaining the same idea and including code Claude already knows.

Suggestions

Collapse the Purpose, Core Principle, Common Mistakes table, and Example Task Flow into a single concise statement of the principle plus one short example, removing redundant restatements.

Drop the trivial file-creation code snippets ('with open(...)', 'echo content > output.txt') that Claude already knows; keep only the verify and declare steps.

Tighten the 'When This Applies' / 'When This Does NOT Apply' lists into a compact bulleted reference rather than prose-heavy sections.

DimensionReasoningScore

Conciseness

The body restates a single simple principle many times across Purpose, Core Principle, Execution Workflow, a Common Mistakes table, and an Example Task Flow, and includes trivial code examples ('with open(...)', 'echo content > file') that Claude already knows.

2 / 5

Actionability

Provides concrete, executable guidance—file-creation code, verification commands (ls, cat), and an explicit do-not list—with only minor vagueness ('use available tools like write_file, create_file, etc.').

4 / 5

Workflow Clarity

A clear three-step sequence (Create → Verify → Declare Completion) with an explicit verification checkpoint; not a destructive/batch operation so no validation cap applies, though no error-recovery loop is needed.

4 / 5

Progressive Disclosure

No bundle files exist and none are needed; the body is well-organized into clearly labeled sections, making navigation easy for a self-contained single-purpose skill.

4 / 5

Total

14

/

20

Passed

Description

50%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 clearly states what the skill clarifies in third person, but it omits any explicit 'when to use' trigger guidance and uses only modestly natural keywords, leaving it mid-pack on completeness and trigger quality.

Suggestions

Add an explicit 'Use when...' clause naming the situations this applies to (e.g., 'Use when a task asks you to create a file-based deliverable and you are tempted to look for a submission or finalize tool').

Include more natural trigger phrases and file extensions a user might say ('create a document', 'generate a report', '.docx', '.pdf', 'write a file').

Sharpen distinctiveness by naming the specific misconception it counters rather than the broad 'file creation tasks' domain.

DimensionReasoningScore

Specificity

Names the domain ('file creation tasks') and a concrete behavioral rule ('complete when the deliverable is successfully written—no submission step required'), but offers only one assertion rather than a list of concrete capabilities.

3 / 5

Completeness

The 'what' is clear (clarifies that file writing completes the task, no submission needed) but there is no 'Use when...' or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric.

3 / 5

Trigger Term Quality

Contains relevant terms ('file creation tasks', 'deliverable', 'submission step') but lacks the natural trigger phrases a user would actually say and misses common synonyms or variations.

3 / 5

Distinctiveness Conflict Risk

The submit-tool misconception is a fairly distinct niche, but the broad 'file creation tasks' framing could overlap with many general file-handling skills.

3 / 5

Total

12

/

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.