CtrlK
BlogDocsLog inGet started
Tessl Logo

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

2.06x
Quality

93%

Does it follow best practices?

Impact

93%

2.06x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

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 a clear, actionable template for session handoffs. Its strengths are the concrete output template, executable git commands, and efficient writing that respects Claude's intelligence. The workflow could benefit from a light validation step to ensure completeness of the generated document.

Suggestions

Add a brief validation checkpoint after generating the handoff, e.g., 'Verify: confirm all uncommitted files from git status appear in Files Touched, and test status reflects actual test run results.'

DimensionReasoningScore

Conciseness

The skill is lean and efficient. It doesn't explain what a handoff is in unnecessary detail, opens with a crisp distinction from wrap-up, and every section earns its place. No padding or concept explanations Claude already knows.

3 / 3

Actionability

Provides concrete bash commands to gather state, a fully structured markdown template with specific fields and examples, and a copy-pasteable resume command format. The output template is directly usable, not abstract.

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). For a non-destructive operation this is acceptable but the sequence could be tighter.

2 / 3

Progressive Disclosure

For a 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). No monolithic walls of text or unnecessary nesting.

3 / 3

Total

11

/

12

Passed

Description

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 multiple natural trigger phrases). It uses third person voice, is concise, and occupies a distinct niche that minimizes conflict risk with other skills.

DimensionReasoningScore

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). Both are well-articulated.

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

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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
rohitg00/pro-workflow
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.