CtrlK
BlogDocsLog inGet started
Tessl Logo

zip-export-deliverable

Ensures codebase deliverables are properly exported as ZIP archives through a dedicated finalization step

54

Quality

60%

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

Quality

Content

67%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 is a well-structured, actionable guide with concrete commands, a complete Python example, validation checkpoints, and a checklist. Its main weaknesses are redundancy (Purpose/Pitfall overlap, duplicated Python example, generic Related Patterns) and a missing explicit error-recovery loop in the bash workflow.

Suggestions

Remove the redundant 'Common Pitfall' section (it restates the Purpose) and drop or condense the generic 'Related Patterns' filler to improve conciseness.

Add an explicit error-recovery feedback loop to Step 4 (e.g., 'If size is 0 or unzip lists nothing, re-run zip -r and check for path/permission errors before proceeding').

Decide between the bash and Python implementations rather than including both as full blocks; if both are needed, move the Python variant to a short note so the primary bash workflow stays lean.

DimensionReasoningScore

Conciseness

Mostly efficient with no basic-concept over-explanation, but the 'Common Pitfall' restates the Purpose, the Python 'Code Example' duplicates the bash workflow, and 'Related Patterns' is generic filler Claude already knows — clear room to tighten.

3 / 5

Actionability

Provides concrete copy-paste bash commands (zip -r, ls -lh, unzip -l) and a complete executable Python function with error handling; minor gaps are the templated '<deliverable-name>.zip ./<project-directory>' form and the assumption that 'zip' is installed.

4 / 5

Workflow Clarity

Five clearly sequenced steps with explicit validation checkpoints (Step 1 verify structure, Step 4 verify archive size/contents) plus a checklist; the operation is non-destructive so no cap applies, but the bash flow lacks an explicit 'if verification fails, fix and retry' feedback loop.

4 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ absent) and the single SKILL.md is well-organized with clear section headers; at ~100 lines the under-50-line 5-exception does not apply, and minor section redundancy plus the absence of any external references keep it at 4.

4 / 5

Total

15

/

20

Passed

Description

53%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, fairly specific purpose but omits any explicit 'when to use' trigger guidance, which caps completeness and weakens trigger-term quality. It is distinct but would benefit from natural user-facing trigger phrases and file-extension synonyms.

Suggestions

Add an explicit 'Use when ...' clause naming natural triggers (e.g., 'Use when delivering a codebase or project as a .zip, or when the user asks to package/compress a project directory for export').

Include synonyms and the file extension users actually say — 'zip file', '.zip', 'compress', 'package' — to improve trigger-term coverage.

Tighten specificity by listing the concrete actions (verify structure, run zip -r, verify the archive) rather than summarizing them as 'a dedicated finalization step'.

DimensionReasoningScore

Specificity

Names the domain ('codebase deliverables') and 1-2 concrete actions ('exported as ZIP archives', 'through a dedicated finalization step'), but coverage is not comprehensive — only a single main action with a qualifier.

3 / 5

Completeness

Has a clear 'what' (ensure deliverables are exported as ZIP via a finalization step) but no 'when'/'Use when' trigger guidance at all, capping completeness at 3 per the missing-trigger guideline.

3 / 5

Trigger Term Quality

Contains relevant keywords ('ZIP archives', 'codebase deliverables', 'exported') but misses common variations and synonyms users would say (e.g., 'zip file', '.zip', 'compress', 'package').

3 / 5

Distinctiveness Conflict Risk

Targets a clear niche (ZIP export finalization) that is mostly distinct, with only minor overlap risk against general archiving/packaging skills; lack of explicit triggers keeps it from a 5.

4 / 5

Total

13

/

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.