session-handoff
Generate a structured handoff document capturing current progress, open tasks, key decisions, and context needed to resume work. Use when ending a session, saying "continue later", "save progress", "session summary", or "pick up where I left off".
94
93%
Does it follow best practices?
Impact
93%
2.06xAverage 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, lists concrete deliverables, and provides explicit trigger guidance with natural user phrases. It follows the recommended pattern of 'what it does' followed by 'Use when...' with multiple realistic trigger terms. The description is concise yet comprehensive, and occupies a distinct niche that minimizes conflict risk.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Generate a structured handoff document capturing current progress, open tasks, key decisions, and context needed to resume work.' This clearly describes what the skill produces and what it captures. | 3 / 3 |
Completeness | Clearly answers both 'what' (generate a structured handoff document capturing progress, tasks, decisions, and context) and 'when' (explicit 'Use when' clause with multiple trigger scenarios). Both are well-articulated. | 3 / 3 |
Trigger Term Quality | Includes highly natural trigger phrases users would actually say: 'continue later', 'save progress', 'session summary', 'pick up where I left off', and 'ending a session'. These cover common variations of how users express the need to pause and resume work. | 3 / 3 |
Distinctiveness Conflict Risk | This skill occupies a clear niche — session handoff/continuity documents. The trigger terms are specific to session management and unlikely to conflict with general documentation or note-taking skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
87%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 provides clear, actionable guidance for generating session handoff documents. The output template is comprehensive and immediately usable, and the guardrails add meaningful constraints. The only notable gap is the lack of a verification step to ensure the handoff document accurately reflects the actual session state (e.g., cross-checking git output against the written summary).
Suggestions
Add a brief verification step after generating the handoff, such as 'Verify: confirm git status output matches the Status section and all modified files appear in Files Touched.'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. The opening line distinguishing handoff from wrap-up is a useful clarification. No unnecessary explanations of concepts Claude already knows. Every section earns its place. | 3 / 3 |
Actionability | Provides concrete bash commands for gathering state, a fully structured markdown template with specific placeholders, and a copy-pasteable resume command format. The guardrails section adds specific, actionable constraints. | 3 / 3 |
Workflow Clarity | The workflow steps are listed clearly but lack validation checkpoints. There's no verification step to confirm the handoff document is complete or accurate (e.g., checking that all uncommitted changes are captured, or that test status was actually verified rather than assumed). For a document generation task this is less critical than for destructive operations, but the workflow is still somewhat implicit about how to verify completeness. | 2 / 3 |
Progressive Disclosure | For a skill of this size and scope, the content is well-organized with clear sections (Trigger, Workflow, Commands, Output, Guardrails). No need for external file references given the focused nature of the skill, and the structure supports easy scanning. | 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.