CtrlK
BlogDocsLog inGet started
Tessl Logo

zip-deliverable-finalization

Ensure codebase deliverables are properly packaged as ZIP exports in a dedicated final step

56

Quality

64%

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

Quality

Content

75%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 highly actionable with executable commands and a clear sequenced workflow including verification. Its main weakness is redundancy between the Steps, Common Mistakes table, and Example sections, and the absence of an error-recovery feedback loop.

Suggestions

Collapse the 'Common Mistakes' table and 'Example' section into the Steps, or trim them to avoid restating the same guidance three times.

Add a brief error-recovery loop after the verification step (e.g., if 'unzip -l' fails or the file is missing, re-run the zip command and recheck).

Remove the generic restated bullet lists under Step 2 ('All code files are written and saved', etc.) since they restate obvious completion criteria.

DimensionReasoningScore

Conciseness

The body is mostly efficient and does not over-explain basic concepts, but the 'Common Mistakes' table and 'Example' section largely restate the Steps, adding redundancy that could be trimmed.

3 / 5

Actionability

Provides copy-paste ready, fully executable commands ('zip -r project.zip ./project', 'ls -la project.zip', 'unzip -l project.zip') and a concrete end-to-end example covering the common case.

5 / 5

Workflow Clarity

A clear six-step sequence includes an explicit verification checkpoint (Step 5), but there is no error-recovery feedback loop describing what to do if packaging or verification fails.

4 / 5

Progressive Disclosure

Well-organized into clearly labeled sections (Purpose, When to Apply, Steps, Common Mistakes, Example, Notes) and appropriately self-contained with no external references needed, though minor redundancy between sections keeps it just below fully clean.

4 / 5

Total

16

/

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 clearly states what the skill does but omits any explicit 'when to use' trigger guidance, capping completeness. Trigger terms are relevant but lack common synonyms and file extensions.

Suggestions

Add a 'Use when...' clause with concrete trigger phrases (e.g., 'Use when the user asks to export, package, or download a codebase as a ZIP archive').

Broaden trigger term coverage to include natural synonyms like 'zip file', 'archive', and the '.zip' extension.

Name a second concrete action (e.g., verifying the archive contents) to lift specificity above a single action.

DimensionReasoningScore

Specificity

Names the domain ('codebase deliverables', 'ZIP exports') and one concrete action ('packaged as ZIP exports in a dedicated final step'), but offers only a single action rather than comprehensive coverage.

3 / 5

Completeness

The 'what' is clear (package deliverables as ZIP in a dedicated step) but there is no 'Use when...' clause or equivalent trigger guidance, so per the rubric completeness is capped at 3.

3 / 5

Trigger Term Quality

Includes relevant keywords ('ZIP exports', 'packaged', 'deliverables') but misses common natural variations users say such as 'zip file', 'archive', or the '.zip' extension.

3 / 5

Distinctiveness Conflict Risk

The ZIP-packaging niche is mostly distinct with clear triggers, though 'codebase deliverables' has minor overlap risk with general project-creation skills.

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.