CtrlK
BlogDocsLog inGet started
Tessl Logo

finalize-zip-deliverable

Ensures codebase deliverables are properly archived into a ZIP file before marking task complete

46

Quality

57%

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

Quality

Content

50%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 skill gives concrete, executable ZIP commands and includes verification steps, but suffers from heavy repetition and a confused, duplicated section structure that hurts both conciseness and workflow clarity.

Suggestions

Consolidate the iteration-threshold guidance into a single section; remove the repeated restatements in the Early Warning System, fallback, zone list, and both checklists to cut padding.

Fix the broken workflow numbering (section 0 appears after section 1; two 'section 4' headers conflict) and merge the two checklists into one canonical pre-completion checklist.

Replace placeholder tokens like '<output_filename>.zip' and '<project_directory>/' with concrete example values to make the commands fully copy-paste ready.

DimensionReasoningScore

Conciseness

The body is noticeably verbose and padded: the iteration-threshold rule is restated five or more times across the Early Warning System, Minimum Viable ZIP Fallback, iteration zones, the pre-completion checklist, and the final Checklist, with repeated bolded emphasis ('MANDATORY', 'CRITICAL', 'BLOCKED') adding little new information.

2 / 5

Actionability

It provides concrete, executable commands ('zip -r project_fallback.zip ./project/', 'ls -lh', 'unzip -l') that are largely copy-paste ready, with only minor gaps from placeholder tokens like '<output_filename>.zip'.

4 / 5

Workflow Clarity

Validation checkpoints exist (verify file existence, non-zero size, optional content inspection) and there is a checklist, but the sequence is incoherent: section '### 1' is followed by '### 0', and two conflicting '### 4' / '## 4' headers appear, with duplicate checklists, making the ordering hard to follow.

3 / 5

Progressive Disclosure

No bundle files exist and none are needed, but the single-file structure has organization problems—duplicate section-4 headers, an out-of-order section-0, and two overlapping checklists—that make navigation harder than it should be.

3 / 5

Total

12

/

20

Passed

Description

46%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 the skill's purpose but omits any explicit trigger guidance and uses limited natural keywords. It is distinguishable but would benefit from a 'Use when...' clause and more synonyms.

Suggestions

Add an explicit trigger clause, e.g., 'Use when finalizing a codebase deliverable that must be packaged as a ZIP archive before task completion.'

Include natural synonyms and file extensions users would say, such as 'archive', 'package', and '.zip', to improve trigger-term coverage.

List the concrete actions performed (verify completeness, run zip, verify artifact) rather than only 'archived into a ZIP file' to raise specificity.

DimensionReasoningScore

Specificity

Names the domain ('codebase deliverables') and one concrete action ('archived into a ZIP file'), plus a condition ('before marking task complete'), but coverage is not comprehensive—it describes a single archiving action rather than multiple specific operations.

3 / 5

Completeness

It clearly answers 'what' (archives deliverables into a ZIP) but provides no explicit 'when'/'Use when...' trigger clause; per the rubric a missing trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

'ZIP file' is a natural keyword, but the description lacks common variations or synonyms (e.g., 'archive', 'package', '.zip') and offers no natural trigger phrase a user would say when needing this skill.

2 / 5

Distinctiveness Conflict Risk

The ZIP-before-completion niche is fairly distinct with low overlap risk against other skills, though 'codebase deliverables' is somewhat generic and could lightly overlap with general packaging/archiving skills.

4 / 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.

Validation — 16 / 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.