zip-deliverable-finalization

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

Quality

67%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

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

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 content is highly actionable with a clear, validated workflow and clean organization, scoring 3 on three dimensions. The only weakness is redundancy: the Common Mistakes table and Example largely restate the Steps, so conciseness sits at 2.

Suggestions

Trim the redundant 'Common Mistakes' table or 'Example' section since both restate content already covered in 'Steps', keeping only what adds new information.

If retaining the Example, make it demonstrate an edge case (e.g. excluding build artifacts with `-x`) rather than repeating the basic zip/verify/report sequence.

Drop definitional phrasing in 'Purpose' like 'do not assume that creating the project structure equals completion' in favor of a single direct instruction.

Dimension	Reasoning	Score
Conciseness	The body is mostly actionable but padded: the 'Common Mistakes' table and the 'Example' section each restate the same steps already given in 'Steps', so it could be tightened, matching the level-2 'mostly efficient but could be tightened' anchor.	2 / 3
Actionability	It gives fully executable, copy-paste-ready commands such as `zip -r project.zip ./project`, `ls -la project.zip`, and `unzip -l project.zip`, matching the level-3 anchor for specific executable examples.	3 / 3
Workflow Clarity	A clear six-step sequence includes an explicit verification checkpoint (Step 5: 'Verify the Archive' with `ls -la` and `unzip -l`), matching the level-3 'clear sequence with explicit validation steps' anchor; ZIP creation is not a destructive/batch operation requiring a feedback loop cap.	3 / 3
Progressive Disclosure	It is a single, well-organized SKILL.md with clearly labeled sections (Purpose, When to Apply, Steps, Common Mistakes, Example, Notes) and no need for external references, so per the simple-skill note a clean section structure earns 3.	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 is specific enough to identify the skill's purpose but stops at level 2 across all dimensions because it lacks an explicit 'Use when' trigger and only names a single action. Adding trigger phrasing and one or two more concrete actions would lift it.

Suggestions

Add an explicit 'Use when...' clause naming the natural trigger terms users would say, e.g. 'Use when a task asks to export, download, package, or deliver a codebase as a ZIP archive.'

Name a couple more concrete actions beyond 'packaged' (e.g. 'zip, verify, and report codebase deliverables') to reach the level-3 specificity anchor.

Include common phrasings a user might actually say ('zip up the project', 'downloadable codebase') to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ("codebase deliverables") and one concrete action ("packaged as ZIP exports"), but does not list multiple specific concrete actions like the level-3 anchor (e.g. "extract, fill, merge").	2 / 3
Completeness	It states what the skill does ("Ensure codebase deliverables are properly packaged as ZIP exports in a dedicated final step") but never says when to use it, so per the guidelines a missing explicit trigger caps completeness at 2.	2 / 3
Trigger Term Quality	"ZIP exports" and "packaged" are plausible natural terms, but there is no "Use when..." clause and common variations a user would say (e.g. "zip up the project", "download the code") are missing, matching the level-2 anchor.	2 / 3
Distinctiveness Conflict Risk	"ZIP exports in a dedicated final step" carves out a recognizable niche, but it could still overlap with general packaging/export skills, fitting the level-2 "somewhat specific but could overlap" anchor rather than a clearly distinct level-3 niche.	2 / 3
	Total	8 / 12 Passed

Validation

100%

Warnings & errors only

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: HKUDS/OpenSpace
Path: benchmarks/gdpval/skills/zip-deliverable-finalization/SKILL.md
Commit: c5a9c4b

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.