Content
78%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
An exceptionally lean, well-sequenced instruction-only body with an explicit verification step and appropriate guardrails. Its main weakness is actionability: the steps describe what to do without any executable commands or error-recovery guidance for the verification stage.
Suggestions
Add the concrete commands for each step — e.g., inspection via 'git ls-files && git status --ignored', archive creation via tar/zip with an explicit exclude list, and verification via 'unzip -l' / 'du -sh' — so guidance is executable rather than descriptive.
Add a feedback loop after step 5: what to do when the archive fails to open, the file list contains an excluded category (e.g., .env*), or the size is unexpectedly large (rebuild the archive with corrected excludes).
Specify the required contents and format of EXPORT_MANIFEST.md (e.g., file list, sizes, exclusion summary) so step 2 is reproducible.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is six terse numbered directives with zero padding and no explanation of concepts Claude already knows (e.g., 'Inspect tracked, untracked, ignored, sensitive, generated, and oversized paths without printing secrets'). Every token earns its place, matching the level-5 anchor; level 4 would require some trimmable over-explanation, which is absent. | 5 / 5 |
Actionability | Guidance names concrete artifacts ('EXPORT_MANIFEST.md', '.env*') and categories, but no executable commands are given for inspecting paths (e.g., git ls-files/status), creating the archive (tar/zip), or verifying it (unzip -l, du -sh) — matching the level-3 anchor of concrete-but-incomplete guidance with missing key details. It is not level 4 because that anchor expects concrete code or commands with only minor gaps, and none are present. | 3 / 5 |
Workflow Clarity | The six steps form a clear sequence with an explicit validation checkpoint ('Verify the archive opens, inspect its file list, and confirm its size before handoff'), matching level 4 ('most checkpoints present'). It is not level 5 because there is no error-recovery feedback loop — what to do if the archive fails to open or the file list reveals a secret — and not capped at 3 since validation for this batch/packaging operation is present. | 4 / 5 |
Progressive Disclosure | The skill is under 50 lines, single-purpose, and needs no external references; the body is well-organized with a clear single heading and ordered steps, and no bundle files exist to mis-navigate. Per the rubric's simple-skill guideline this earns a 5; level 4 would imply organization gaps that are not present. | 5 / 5 |
Total | 17 / 20 Passed |