wrap-up

End-of-session ritual that audits changes, runs quality checks, captures learnings, and produces a session summary. Use when saying "wrap up", "done for the day", "finish coding", or ending a coding session.

Quality

100%

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

Quality

Content

100%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A tight, well-structured ritual skill that leads with a numbered workflow, backs it with executable commands, and enforces validation through guardrails. No bundle files are needed or referenced, and the content respects the context budget.

Dimension	Reasoning	Score
Conciseness	The ~45-line body is lean and assumes Claude's competence — it gives commands and a checklist without explaining what git, lint, or tests are, so every token earns its place.	3 / 3
Actionability	Provides a copy-paste-ready command block (git status, npm run lint/typecheck, npm test) plus a concrete learning format ('[LEARN] Category: Rule') and explicit output structure, matching the executable-guidance anchor.	3 / 3
Workflow Clarity	A clearly sequenced 5-step workflow with guardrails acting as validation checkpoints ('If tests are failing, flag before ending session'), satisfying the explicit-checkpoint anchor rather than the checkpoint-missing level 2.	3 / 3
Progressive Disclosure	Under 50 lines, single-purpose, with well-organized sections (Trigger, Workflow, Commands, Guardrails, Output) and no external references needed — the rubric's simple-skill note permits a 3 here.	3 / 3
	Total	12 / 12 Passed

Description

100%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A concise, third-person description that names concrete capabilities and pairs them with explicit, natural trigger phrases. It cleanly answers both what the skill does and when to invoke it with no fluff or over-claims.

Dimension	Reasoning	Score
Specificity	Lists four concrete actions — 'audits changes, runs quality checks, captures learnings, and produces a session summary' — matching the multiple-specific-actions anchor rather than the single-domain level 2.	3 / 3
Completeness	Explicitly answers both what (the four actions) and when via an explicit 'Use when...' clause, matching the level-3 anchor; not capped at 2 because the trigger guidance is present.	3 / 3
Trigger Term Quality	Provides natural phrasings a user would actually say ('wrap up', 'done for the day', 'finish coding', ending a session), giving good coverage rather than the partial level-2 set.	3 / 3
Distinctiveness Conflict Risk	The 'end-of-session ritual' niche with session-ending triggers is clearly distinguishable from other skills and unlikely to fire for the wrong skill.	3 / 3
	Total	12 / 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: rohitg00/pro-workflow
Path: skills/wrap-up/SKILL.md
Commit: 7f7209d

Reviewed: 8 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.