wrap-up
End-of-session ritual that audits changes, runs quality checks, captures learnings, and produces a session summary. Use when ending a coding session.
95
Does it follow best practices?
Validation for skill structure
Discovery
85%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-crafted description that clearly communicates the skill's purpose and when to use it. It excels at specificity and completeness with explicit trigger guidance. The main weakness is limited trigger term coverage - users might phrase session endings in various ways not captured here.
Suggestions
Expand trigger terms to include natural variations like 'wrap up', 'finish coding', 'done for the day', 'close out session', or 'end of day'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'audits changes', 'runs quality checks', 'captures learnings', and 'produces a session summary'. These are distinct, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('audits changes, runs quality checks, captures learnings, produces session summary') and when ('Use when ending a coding session') with an explicit trigger clause. | 3 / 3 |
Trigger Term Quality | Includes 'ending a coding session' which is a natural phrase, but misses common variations users might say like 'wrap up', 'finish up', 'done for today', 'session end', or 'close out'. | 2 / 3 |
Distinctiveness Conflict Risk | Clear niche as an 'end-of-session ritual' with distinct purpose. The combination of session-ending context plus audit/summary actions makes it unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent skill that demonstrates strong content quality across all dimensions. It's concise yet comprehensive, provides executable commands, has a clear workflow with validation checkpoints, and is well-organized for quick reference. The guardrails section appropriately handles edge cases like failing tests and uncommitted changes.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every section is lean and purposeful. No unnecessary explanations of what git or npm commands do. The workflow steps are terse but complete, and the learning categories are a simple list rather than verbose descriptions. | 3 / 3 |
Actionability | Provides concrete, copy-paste ready bash commands for the quality check phase. The workflow steps are specific actions, not vague descriptions. Output format is clearly specified with bullet points. | 3 / 3 |
Workflow Clarity | Clear 5-step numbered sequence with explicit validation checkpoint (step 2 quality check). Guardrails section provides feedback loops for failing tests and uncommitted changes, with specific actions to take. | 3 / 3 |
Progressive Disclosure | For a skill under 50 lines with no need for external references, the content is well-organized into logical sections (Trigger, Workflow, Commands, Categories, Guardrails, Output). Each section serves a clear purpose without unnecessary nesting. | 3 / 3 |
Total | 12 / 12 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 — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- 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.