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.
96
100%
Does it follow best practices?
Impact
83%
1.72xAverage score across 3 eval scenarios
Passed
No known issues
Quality
Discovery
100%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 strong skill description that clearly communicates its purpose as an end-of-session workflow, lists specific actions it performs, and provides natural trigger phrases users would actually say. It uses proper third-person voice and is concise without being vague. The description effectively distinguishes itself from other skills through its unique session-ending context.
| 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 a session summary') and when ('Use when saying "wrap up", "done for the day", "finish coding", or ending a coding session') with explicit triggers. | 3 / 3 |
Trigger Term Quality | Includes natural phrases users would actually say: 'wrap up', 'done for the day', 'finish coding', 'ending a coding session'. These are realistic, conversational trigger terms covering multiple variations. | 3 / 3 |
Distinctiveness Conflict Risk | The concept of an 'end-of-session ritual' is a clear, distinct niche. The trigger terms ('wrap up', 'done for the day', 'finish coding') are specific to session-ending contexts and unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 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 a well-crafted skill that is concise, actionable, and clearly structured. The workflow has explicit validation checkpoints (failing tests, uncommitted changes) with defined responses, and the concrete bash commands make the quality check step immediately executable. The content respects Claude's intelligence while providing all necessary specifics.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every section is lean and purposeful. No unnecessary explanations of what git, linting, or testing are. The learning categories are a compact list, and the guardrails are terse but clear. | 3 / 3 |
Actionability | Provides concrete, executable bash commands for the quality check step, specific output format expectations, and clear guardrails with specific actions (commit or stash). The learning format `[LEARN] Category: Rule` is a concrete template. | 3 / 3 |
Workflow Clarity | The 5-step workflow is clearly sequenced with logical ordering (audit → check → learn → plan → summarize). Includes validation checkpoints: tests must pass before ending, uncommitted changes trigger a decision point, and the final confirmation question acts as a gate. | 3 / 3 |
Progressive Disclosure | For a skill under 50 lines with a single-purpose ritual, the content is well-organized into clearly labeled sections (Trigger, Workflow, Commands, Categories, Guardrails, Output) without needing external references. Easy to scan and navigate. | 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.
- Repository
- rohitg00/pro-workflow
- Commit
1de1554
- 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.