CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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".

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

93%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

An excellent, disciplined instruction-only skill body: lean, concrete, and self-contained, with a workflow, command set, and output template that leave no ambiguity about what to produce. The only gap is the absence of explicit validation checkpoints in the workflow (unimportant for read-only git operations, hence only a minor deduction).

Suggestions

Add a lightweight checkpoint to the workflow, e.g., after gathering git state, confirm uncommitted changes and failing tests are reflected in the Status section before generating the document — this would close the minor validation gap in an otherwise clear sequence.

DimensionReasoningScore

Conciseness

The 74-line body contains no explanations of concepts Claude already knows and no padding; even the wrap-up disambiguation ("Wrap-up is a checklist for you. Handoff is a document written for the next session.") is load-bearing, matching the lean anchor 5.

5 / 5

Actionability

Fully concrete guidance: copy-pasteable git commands (git status, git diff --stat, git log --oneline -5, git branch --show-current), a complete fill-in output template covering every section, and a concrete resume-command format — the instruction-only equivalent of copy-paste-ready code.

5 / 5

Workflow Clarity

The 5-step workflow (gather git state → list work → decisions → learnings → resume command) is clearly sequenced and maps onto real commands and a template that acts as a checklist, but there are no explicit validation checkpoints (e.g., verifying the gathered state is complete before writing), fitting anchor 4's "clear sequence, minor validation gaps" rather than 5.

4 / 5

Progressive Disclosure

Well-organized sections (Trigger, Workflow, Commands, Output, Guardrails) with everything appropriately inline for a self-contained skill: no nested or buried references, no content that warrants splitting into bundle files, and easy navigation — matching anchor 5's structure.

5 / 5

Total

19

/

20

Passed

Description

83%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: concrete, third-person, with an explicit and multi-phrase "Use when" clause that directly satisfies completeness. Its main weakness is that the description omits the skill's own name ("handoff") and related trigger synonyms, which both weakens trigger coverage and leaves minor overlap risk with generic summary/progress-saving skills.

Suggestions

Add "handoff" and "session transfer" to the description's trigger phrases — they are natural terms users would say and are currently only listed in the body's Trigger section, which is not loaded during skill selection.

Sharpen distinctiveness by adding a differentiator such as "for resuming work in a later session" to the trigger clause so it cannot be confused with generic 'save progress' or summary skills.

DimensionReasoningScore

Specificity

"Generate a structured handoff document capturing current progress, open tasks, key decisions, and context needed to resume work" enumerates four concrete content areas, but describes a single generating action rather than several distinct actions, matching anchor 4 (several specifics, minor coverage gaps) rather than 5 (multiple distinct actions).

4 / 5

Completeness

Explicitly answers both questions: the "what" (a structured handoff document with enumerated contents) and the "when" with multiple concrete quoted trigger phrases — a direct match to the anchor-5 example pattern.

5 / 5

Trigger Term Quality

Natural user phrases are present ("continue later", "save progress", "session summary", "pick up where I left off"), but the key terms "handoff" and "session transfer" — used in the body's Trigger section — are missing from the description itself, so coverage is good but not comprehensive.

4 / 5

Distinctiveness Conflict Risk

The resume-work niche is clear, but "save progress" and "session summary" could plausibly fire for a general summary, notes, or memory skill, and the most distinctive term ("handoff") is absent from the description — minor overlap risk with closely related skills (anchor 4) rather than minimal risk (anchor 5).

4 / 5

Total

17

/

20

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

rohitg00/pro-workflow

Path

skills/session-handoff/SKILL.md

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.