CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

claude-handoff

Hand the current conversation off to a fresh background agent that picks up the work immediately.

Quality

80%

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

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/claude-handoff/SKILL.md

The canonical home for this skill is claude-handoff in mattpocock/skills

SKILL.md
Quality
Evals
Security

Quality

Content

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

The body is an exemplary lean instruction skill: a complete, copy-paste-ready CLI invocation plus specific directives on naming, summary contents, artifact de-duplication, redaction, and argument handling. As a short, single-purpose skill with no bundle files, it fully satisfies the simple-skill exceptions for workflow clarity and progressive disclosure.

DimensionReasoningScore

Conciseness

Every sentence is a directive ("launch a background agent seeded with the summary as its prompt", "Redact any sensitive information", "Do not duplicate content already captured in other artifacts") with zero padding and no explanation of concepts Claude already knows — matching the lean, every-token-earns-its-place anchor.

5 / 5

Actionability

The body provides a copy-paste-ready command (`claude --bg --name "<descriptive name>" "<handoff summary>"`) plus concrete directives covering the common case, including a worked example name (`--name "Fix login bug"`) and handling of user arguments — matching the fully-executable anchor. It is not 4 because no gaps remain in the executable guidance.

5 / 5

Workflow Clarity

This is a simple, single-purpose skill where the sequence — write the summary, launch the agent seeded with it, manage via `claude agents` — is unambiguous, so the simple-skill exception applies. The operation is neither destructive nor batch, so no validation cap applies; not 4 because nothing in the flow is left implicit.

5 / 5

Progressive Disclosure

The body is under 50 lines, requires no external references (none exist in the bundle), and each short paragraph carries exactly one directive, so the under-50-lines exception applies. It is not 4 because there is no content that belongs in a separate file and no organization gaps.

5 / 5

Total

20

/

20

Passed

Description

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

The description is concise and third-person with one clearly stated, concrete capability, but it lacks any "Use when..." trigger guidance and offers only a single action with limited keyword variations. Adding an explicit trigger clause and natural synonyms (e.g., "handoff", "new session") would materially improve it.

Suggestions

Add an explicit 'Use when...' clause naming the situations that call for this skill, e.g. "Use when the user wants a handoff, to continue work in a fresh session, or to transfer context to a new agent."

Include natural synonyms and phrasings users would actually say — "handoff", "hand off the conversation", "continue in a new session", "context transfer" — to broaden trigger-term coverage.

Name a second concrete capability (e.g., tailoring the handoff summary to the user's stated focus or seeding the new agent with it) to raise specificity from one action to several.

DimensionReasoningScore

Specificity

"Hand the current conversation off to a fresh background agent" names one concrete action in a specific domain, matching the '1-2 concrete actions, but not comprehensive' anchor. It is not 4 because only a single action is described, and not 2 because the action is concrete rather than generic.

3 / 5

Completeness

The description clearly answers "what" ("Hand the current conversation off to a fresh background agent") but contains no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Terms like "hand off", "conversation", and "background agent" are natural, but common variations such as "handoff", "new session", or "context transfer" are missing, matching 'some relevant keywords but missing common variations or synonyms'.

3 / 5

Distinctiveness Conflict Risk

Background-agent handoff is a distinct niche with unique vocabulary; minor overlap risk remains with session-summary or continuation skills. It is not 5 because no explicit trigger phrases fully separate it from those adjacent skills.

4 / 5

Total

13

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

tonykay/transcriber

Path

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