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

59

Quality

67%

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

85%

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

The body delivers concrete, executable guidance with a clear verify-gated workflow and well-organized self-contained sections. The main weakness is conciseness — redundant restatements of the core principle and explanation of basic file I/O that Claude already knows.

Suggestions

Collapse the Core Principle section and Common Mistakes table, which restate the Purpose and Step 3, to remove redundancy.

Trim the basic file-creation examples (`with open`, `echo >`) since Claude already knows standard file I/O; keep only the verify-and-declare guidance that is the skill's novel insight.

Replace the hand-wavy 'Or use available tools like write_file, create_file, etc.' with a single concrete instruction.

DimensionReasoningScore

Conciseness

The Core Principle and Common Mistakes table restate the Purpose and Step 3, and the workflow explains basic file I/O (`with open`, `echo >`) that Claude already knows; mostly efficient but could be tightened.

2 / 3

Actionability

Provides concrete, executable code (`with open(...)`, `echo >`, `ls -la`, `cat`) and a specific example task flow with a sample completion report — copy-paste ready guidance.

3 / 3

Workflow Clarity

A clear 3-step sequence (Create → Verify → Declare) with an explicit validation checkpoint gated by 'Once verification passes'; appropriate for a simple, non-destructive skill.

3 / 3

Progressive Disclosure

Single-file skill with well-organized sections (Purpose, Core Principle, Execution Workflow, Common Mistakes, When This Applies / Does NOT Apply), no nested references, and no need to split for this concept size.

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 conveys a clear, specific conceptual niche (file creation = task completion, no submission needed) in third person, but it lacks an explicit 'Use when...' trigger clause and its natural-language keyword coverage is limited. All dimensions land at the mid-level anchor.

Suggestions

Add an explicit trigger clause, e.g. 'Use when creating document, report, or code file deliverables and you are unsure whether a submission step is needed.'

Broaden natural trigger terms to include user phrasings like 'report', 'document', 'export', or 'generate a file'.

Lead with a concrete action verb list (e.g. 'Confirms file creation tasks are complete once written to disk') rather than the abstract verb 'Clarifies'.

DimensionReasoningScore

Specificity

Names the domain ('file creation tasks', 'deliverable', 'submission step') and the clarifying action, but does not enumerate multiple specific concrete actions the skill performs.

2 / 3

Completeness

It clearly answers 'what' (clarifies completion means the file is written, no submission step) but provides no 'Use when...' clause or equivalent explicit trigger guidance, capping completeness at 2.

2 / 3

Trigger Term Quality

'file creation tasks', 'deliverable', and 'submission step' are reasonably natural keywords, but coverage of common user phrasings is limited and missing variations.

2 / 3

Distinctiveness Conflict Risk

The no-submission-misconception niche is conceptually distinct, but the trigger 'file creation tasks' is broad and could overlap with many document-creation skills.

2 / 3

Total

8

/

12

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.