CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

handoff

This skill should be used when preparing a handoff checklist for agents and persisting it as a handoff note that can be picked up in a fresh thread.

69

Quality

87%

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 exemplarily lean, actionable single-file skill: copy-paste commands, exact paths and filename patterns, and an ordered checklist with fallback handling. The only gap is the absence of an explicit post-write verification step, which keeps workflow clarity just short of full marks.

DimensionReasoningScore

Conciseness

The body is lean and fully operational — path rules, filename pattern, and a seven-item checklist with no concept explanations or padding — every token earns its place and it assumes Claude's competence throughout.

5 / 5

Actionability

Copy-paste ready commands are given (git rev-parse --show-toplevel, git status -sb, tmux attach -t codex-shell, tmux capture-pane -p -J -t codex-shell:0.0 -S -200), plus exact directory conventions and a concrete filename pattern, covering the common cases an instruction-only skill needs.

5 / 5

Workflow Clarity

The sequence is clear and explicitly ordered (persist location → filename → content in numbered order → output format) with an error-recovery fallback ("If file write is not possible, print the handoff checklist in chat"), but there is no post-write validation checkpoint (e.g., confirming the file exists) — minor validation gaps keep it below anchor 5.

4 / 5

Progressive Disclosure

The skill is under 50 lines with no bundle files and no need for external references; content is well organized into clearly signaled sections (Persist, Checklist content, Output format, Notes), which per the simple-skill guideline merits a 5.

5 / 5

Total

19

/

20

Passed

Description

73%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 focused, third-person description with an explicit use-when clause and distinct niche triggers. Its main weakness is specificity: it names only two actions and omits the concrete capabilities the skill actually delivers (git-tracked persistence, tmux/process capture, structured checklist sections), which also limits natural trigger-term variety.

Suggestions

Add 1-2 more concrete capabilities to the description (e.g., "captures working-tree status, branch/PR state, tmux sessions, and next steps") to lift specificity from naming the domain to listing several specific actions.

Broaden trigger terms with natural synonyms users would say, such as "save session state", "resume work", or "hand off to a new thread", to improve trigger coverage beyond the repeated "handoff" phrasing.

Make the when-clause independently concrete rather than circular with the what (e.g., "Use when a session is ending, context is about to be lost, or a fresh thread must resume in-progress work").

DimensionReasoningScore

Specificity

Names the domain and two concrete actions ("preparing a handoff checklist", "persisting it as a handoff note") plus an outcome context ("picked up in a fresh thread"), but does not cover the skill's fuller scope such as git-tracked storage, running-process capture, or the structured checklist contents — fitting the 1-2 concrete actions anchor rather than the several-actions anchors above.

3 / 5

Completeness

Both what ("preparing a handoff checklist... persisting it as a handoff note") and an explicit when ("This skill should be used when...") are present, so it clears the anchor-3 cap; the when clause is near-circular with the what, keeping it below the independently concrete trigger phrases of anchor 5.

4 / 5

Trigger Term Quality

Includes natural phrases a user would say ("handoff checklist", "handoff note", "fresh thread") with the core term repeated, but misses common variations such as "session state", "save state", "resume work", or "context handoff" — good coverage with a few natural terms missing rather than comprehensive.

4 / 5

Distinctiveness Conflict Risk

"Handoff" for agent session continuity is a clear niche with distinct, specific triggers (handoff checklist, handoff note, fresh thread) and minimal overlap risk with other skills.

5 / 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

marchatton/agent-skills

Path

.agents/skills/00-utilities/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.