Generate a structured handoff document designed for the next session to consume immediately and continue where you left off. Use when ending a session.
Install with Tessl CLI
npx tessl i github:rohitg00/pro-workflow --skill session-handoff92
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
75%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description effectively communicates its purpose and includes an explicit 'Use when' clause, making it complete. However, it could be more specific about what the handoff document contains and include more natural trigger terms users might actually say when wanting to preserve session context.
Suggestions
Add specific actions the skill performs, e.g., 'captures current progress, open tasks, key decisions, and context needed to resume work'
Expand trigger terms to include natural phrases like 'wrap up', 'save progress', 'continue later', 'session summary', 'pause work'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (handoff document) and one action (generate), but lacks detail on what the document contains or what 'structured' means concretely. Does not list multiple specific actions. | 2 / 3 |
Completeness | Clearly answers both what ('Generate a structured handoff document designed for the next session to consume immediately and continue where you left off') and when ('Use when ending a session') with an explicit trigger clause. | 3 / 3 |
Trigger Term Quality | Includes 'handoff document' and 'ending a session' which are relevant, but misses common variations users might say like 'wrap up', 'save progress', 'continue later', 'session summary', or 'pick up where I left off'. | 2 / 3 |
Distinctiveness Conflict Risk | Has a clear niche focused on session continuity and handoff documents. The specific purpose of cross-session context preservation is distinct and unlikely to conflict with other skills. | 3 / 3 |
Total | 10 / 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 exemplary skill that demonstrates excellent content quality. It's concise yet complete, provides a fully actionable template with concrete commands, and has clear workflow structure. The guardrails section adds valuable quality criteria without bloat.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every section earns its place. No unnecessary explanations of what handoffs are or why they matter. The distinction from wrap-up is stated in one line, then moves directly to actionable content. | 3 / 3 |
Actionability | Provides executable bash commands for gathering state, a complete markdown template with specific placeholders, and a copy-pasteable resume command format. Claude knows exactly what to produce. | 3 / 3 |
Workflow Clarity | Clear 5-step workflow with logical sequence. The output template itself serves as a checklist ensuring nothing is missed. Guardrails provide validation criteria for quality. | 3 / 3 |
Progressive Disclosure | For a skill under 50 lines with no need for external references, this is well-organized with clear sections (Trigger, Workflow, Commands, Output, Guardrails). Content is appropriately self-contained. | 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.
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.