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.
91
92%
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 well-crafted skill description that clearly communicates its purpose as a session-closing workflow. It lists specific actions, provides natural trigger phrases users would actually say, and occupies a distinct niche that is unlikely to conflict with other skills. The description is concise yet comprehensive.
| 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 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 like code review or testing. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A well-structured, concise session wrap-up ritual with clear sequencing and appropriate guardrails. The workflow is easy to follow and the commands are executable. The main gap is the lack of concrete output examples—a sample learning entry or session summary would elevate actionability.
Suggestions
Add a concrete example of a `[LEARN]` entry, e.g., `[LEARN] Testing: Always run integration tests after changing API routes`
Include a brief example of the expected one-paragraph session summary to make the output format unambiguous
| 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 | The bash commands are concrete and executable, but the workflow steps (Changes Audit, Learning Capture, Next Session Context) are described at a checklist level without concrete examples of output format. A sample `[LEARN]` entry or a sample session summary would make it fully actionable. | 2 / 3 |
Workflow Clarity | The five steps are clearly sequenced and logically ordered. Guardrails provide explicit validation checkpoints: flag failing tests before ending, ask about uncommitted changes. The final confirmation prompt ('Ready to end session?') acts as a gate before completion. | 3 / 3 |
Progressive Disclosure | This is a short, single-purpose skill under 50 lines with well-organized sections (Trigger, Workflow, Commands, Guardrails, Output). No need for external references, and the structure is easy to scan and navigate. | 3 / 3 |
Total | 11 / 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
9df6af8
- 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.