CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

gsd-cleanup

Archive accumulated phase directories from completed milestones

Quality

68%

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 ./pi/package-skills/gsd-cleanup/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 lean, well-structured overview with genuine operational discipline: fail-closed dispatch rules, a read-first include instruction, and a dry-run-plus-confirmation checkpoint on a destructive batch operation. Its main weakness is that the actual task steps (how completed milestones are identified, how archiving is executed) are only named, not specified, with everything deferred to an external templated workflow file.

Suggestions

In the <process> section, specify how to identify completed milestones (e.g. which file or status field in .planning/ records milestone completion) instead of leaving the first step abstract.

Add a post-archive verification step (e.g. confirm .planning/phases/ now contains only active-phase directories and the archived tree is intact) to close the feedback loop for this batch operation.

Note how the __GSD_PI_ENGINE_ROOT__ placeholder resolves at install time, or provide a fallback lookup, so the single external reference is reliably navigable rather than an unverifiable path.

DimensionReasoningScore

Conciseness

The ~25-line body is dense and operational with no explanations of concepts Claude already knows; the Pi dispatch paragraph covers custom-tool behavior ("GSD provides the gsd_dispatch tool... cannot dispatch further") that is genuinely unknown. Minor over-explanation remains — e.g. the Agent(...) equivalence sentence and the restated fail-closed rules could be trimmed — so it fits 'efficient; minor instances of over-explanation' rather than the lean 5 anchor.

4 / 5

Actionability

Dispatch mechanics are concrete ("call gsd_dispatch with role... and task..."), but the core process is high-level: "Identify completed milestones, show a dry-run summary, and archive on confirmation" gives no indication of how completion is determined or how archiving is performed, with those key details deferred entirely to an external file. This is 'some concrete guidance but incomplete; missing key details', not the mostly-executable anchor 4.

3 / 5

Workflow Clarity

The sequence is clear (read <execution_context> files "Before doing anything else", then identify → dry-run → archive on confirmation) and includes a real checkpoint for a batch/destructive operation ("show a dry-run summary, and archive on confirmation"), so the missing-validation cap does not apply. It falls short of anchor 5 because there is no post-archive verification or error-recovery loop, and 'identify completed milestones' is left implicit.

4 / 5

Progressive Disclosure

The body is a lean overview with a single, clearly signaled, one-level-deep reference ("<execution_context> @__GSD_PI_ENGINE_ROOT__/gsd-core/workflows/cleanup.md"), and detail is appropriately split out. It is not a 5 because the referenced path is an unresolved template placeholder with no bundle files present (no references/, scripts/, or assets/), so navigation cannot be verified against the actual bundle — a minor organization gap.

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 states a single concrete action clearly and occupies a distinct niche, but it omits any explicit 'when to use' guidance and lacks natural trigger synonyms, capping completeness and trigger-term quality at the midpoint. Adding a 'Use when...' clause with user-facing phrases would lift it substantially.

Suggestions

Add an explicit trigger clause, e.g. "Use when .planning/phases/ has accumulated directories from past milestones, or when the user asks to clean up or archive finished phases."

Include natural synonyms users would actually say — "cleanup", "clean up", "tidy up", "finished/completed phases" — alongside the current domain jargon.

State the concrete effect of the action (e.g. "moves them into .planning/milestones/v{X.Y}-phases/") to sharpen specificity beyond the single verb "archive".

DimensionReasoningScore

Specificity

"Archive accumulated phase directories from completed milestones" names the domain (phase directories, completed milestones) and one concrete action (archive), matching the 'names domain and 1-2 concrete actions' anchor. It does not list several specific actions (no mention of where things move or what the archive contains), so it is not a 4.

3 / 5

Completeness

The 'what' is clear (archive phase directories from completed milestones) but there is no 'Use when...' clause or equivalent explicit trigger guidance in the description, which caps completeness at 3 per the judging guidelines; "from completed milestones" only weakly implies timing. It is above anchor 2 because the 'what' is concrete, not vague.

3 / 5

Trigger Term Quality

Relevant keywords exist ("Archive", "phase directories", "milestones") but common variations a user would naturally say are missing — e.g. "cleanup", "clean up", "tidy", "finished phases", "old phases". This matches 'some relevant keywords but missing common variations or synonyms' rather than the good-coverage anchor 4.

3 / 5

Distinctiveness Conflict Risk

The operation is a clear niche (archiving GSD planning phase directories) unlikely to trigger generic skills, fitting 'mostly distinct; minor overlap risk'. It is not a 5 because related gsd-* maintenance/milestone skills could plausibly share 'milestones'/'planning' triggers, and no distinct trigger phrases are stated to disambiguate.

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

open-gsd/gsd-core

Path

pi/package-skills/gsd-cleanup/SKILL.md

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.