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 an excellent skill description that clearly communicates what the skill does (generates structured handoff documents with specific content areas) and when to use it (with a well-crafted 'Use when' clause containing natural trigger phrases). It is concise, uses third person voice, and occupies a distinct niche that minimizes conflict risk with other skills.
| 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 contains. | 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). Fully complete. | 3 / 3 |
Trigger Term Quality | Includes natural phrases users would actually say: 'continue later', 'save progress', 'session summary', 'pick up where I left off', and 'ending a session'. These are highly natural and cover common variations of the intent. | 3 / 3 |
Distinctiveness Conflict Risk | The concept of a session handoff/continuity document is a clear niche. The trigger terms ('save progress', 'pick up where I left off', 'session summary') are distinct and unlikely to conflict with other skills like general documentation or note-taking. | 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 efficiently communicates its purpose and provides a concrete, actionable template. The distinction from wrap-up at the top is a nice touch. The main weakness is the workflow section, which lists steps sequentially but doesn't include any validation or review checkpoint before producing the final handoff document.
Suggestions
Add a brief validation step to the workflow, e.g., 'Review the handoff document: verify all uncommitted changes are noted, in-progress items have sufficient context, and the resume command is accurate and self-contained.'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. The opening line immediately distinguishes handoff from wrap-up, every section serves a purpose, and there's no unnecessary explanation of concepts Claude already knows. The template is well-structured without padding. | 3 / 3 |
Actionability | Provides concrete bash commands to gather state, a complete copy-paste-ready markdown template with specific fields, and a resume command format. The guardrails section adds actionable constraints. The template is directly executable as output. | 3 / 3 |
Workflow Clarity | The workflow steps are listed clearly but lack validation checkpoints. There's no explicit verification step (e.g., confirming all in-progress items are captured, verifying the resume command is accurate, or checking that uncommitted changes are noted). For a document generation task this is less critical than for destructive operations, but the workflow could benefit from a review/validation step before finalizing the handoff. | 2 / 3 |
Progressive Disclosure | For a simple, single-purpose skill under 50 lines with no need for external references, the content is well-organized with clear sections (Trigger, Workflow, Commands, Output, Guardrails). The structure is logical and easy to navigate without requiring additional files. | 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.
9fc35f5
Table of Contents
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.