CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

handoff

Use when capturing session state before switching context, ending a session, or manually preserving progress — creates a structured handoff document in docs/handoffs/ so a future session can resume seamlessly

Quality

84%

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

82%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.

A highly actionable, well-structured skill: the process is concrete and copy-paste ready, with clear sequencing and a completion checkpoint. The only meaningful gaps are localized verbosity in the Cross-Agent section and the absence of a validation step for the produced handoff document.

DimensionReasoningScore

Conciseness

The body is dominated by tight operational content (exact git commands, a full template, slug guidelines), but the Cross-Agent Handoff use-case bullets and the 'Why this works' paragraph ('The handoff document is the contract...') are explanation Claude could infer and could be trimmed.

4 / 5

Actionability

Fully executable guidance throughout: exact commands ('git diff --name-only', 'git status --porcelain', 'ls .claude/plans/*.md'), a complete copy-paste markdown template with frontmatter, exact output paths ('docs/handoffs/YYYY-MM-DD-<topic>.md'), and a ready-to-use confirmation format.

5 / 5

Workflow Clarity

A clearly sequenced 5-step process (Gather → Topic → Write → Fill → Confirm) with a closing confirmation checkpoint, but no validation step verifying the written document is complete or correct. The operation is non-destructive, so the batch/destruction cap does not apply.

4 / 5

Progressive Disclosure

A single-file skill with well-organized, clearly headed sections and no buried or nested references. At ~155 lines it exceeds the simple-skill threshold, and the Cross-Agent use cases and compaction-hook details could plausibly live in a reference file, keeping it just below a 5.

4 / 5

Total

17

/

20

Passed

Description

78%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 that clearly and explicitly states both what the skill does and when to use it, with natural trigger phrases and a distinct handoff niche. Its main weakness is specificity — it names only a couple of concrete actions rather than enumerating what the handoff document captures.

Suggestions

Enumerate what the handoff document records (e.g., goals, decisions, progress, next steps) to lift specificity from naming the domain plus two actions to listing several concrete actions.

Add one or two common user synonyms such as 'save my progress' or 'before compaction' to the trigger phrasing for fuller natural-term coverage.

DimensionReasoningScore

Specificity

Quotes 'capturing session state' and 'creates a structured handoff document in docs/handoffs/' — the domain plus roughly two concrete actions with a specific output location, but not the several specific actions (e.g., recording goals, decisions, progress, next steps) needed for a higher score.

3 / 5

Completeness

Explicitly answers 'what' ('creates a structured handoff document in docs/handoffs/ so a future session can resume seamlessly') and 'when' with concrete trigger phrases ('Use when capturing session state before switching context, ending a session, or manually preserving progress').

5 / 5

Trigger Term Quality

Natural phrases like 'switching context', 'ending a session', 'preserving progress', and 'resume' match what users would say, but common synonyms such as 'save my progress', 'wrap up', or 'before compaction' are missing.

4 / 5

Distinctiveness Conflict Risk

'handoff document', 'session state', and the docs/handoffs/ location define a clear niche, but 'manually preserving progress' is broad enough for minor overlap with sibling skills like capturing solved problems.

4 / 5

Total

16

/

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

lucianghinda/superpowers-ruby

Path

skills/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.