CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

handoff

Compact the current conversation into a handoff document for another agent to pick up.

Quality

77%

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 ./.claude/skills/handoff/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

92%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 exemplar of lean, instruction-only skill writing: concrete output target, explicit content requirements, a smart anti-duplication rule, and argument-aware tailoring with zero wasted tokens. The only minor improvement would be sketching the handoff document's expected structure.

DimensionReasoningScore

Conciseness

Four lean paragraphs with zero padding — no explanations of concepts Claude already knows, no verbosity, and every instruction earns its place. This matches the anchor "lean and efficient; assumes Claude's competence; every token earns its place".

5 / 5

Actionability

The guidance is concrete for an instruction-only skill: a named output file ("Save to the HANDOFF.md"), a required section ("suggested skills"), an enumerated dedup rule ("PRDs, plans, ADRs, issues, commits, diffs"), and explicit argument handling. It falls short of fully executable guidance only because no document structure or template is provided, leaving the handoff doc's shape implicit.

4 / 5

Workflow Clarity

This is a simple, single-purpose skill (write one document) and the single action is unambiguous: destination file, required section, dedup rule, and argument handling are all specified. The rubric's simple-skill exception applies, and the operation is neither destructive nor batch, so no validation steps are required.

5 / 5

Progressive Disclosure

The skill is under 50 lines, has no need for external references (none exist in the bundle), and its short paragraphs each address one distinct concern. Per the rubric's simple-skill guidance, this warrants a 5 with well-organized content and no unnecessary file splitting.

5 / 5

Total

19

/

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 communicates a clear, concrete single purpose but completely omits any usage triggers, leaving the "when should this be used" question unanswered. Adding a "Use when..." clause with natural trigger phrases would substantially improve trigger term quality, completeness, and distinctiveness.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to hand off, hand over, or compact the session for a new agent, or mentions a session summary or context handoff."

Include natural synonyms users would actually say — "session summary", "context handoff", "hand off to the next agent" — to broaden trigger term coverage.

Optionally name the output artifact (HANDOFF.md) in the description to further differentiate from generic summarization skills.

DimensionReasoningScore

Specificity

The description names one concrete action — "Compact the current conversation into a handoff document for another agent to pick up" — which matches the anchor for naming a domain with 1-2 concrete actions but not comprehensive coverage. It does not list several specific actions (score 4), but it is more concrete than a bare domain mention (score 2).

3 / 5

Completeness

The "what" is clear (compact the conversation into a handoff document for another agent), but the "when" is entirely absent — there is no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3 per the rubric guidelines. It is not a 2 because the "what" is specific and unambiguous rather than vague.

3 / 5

Trigger Term Quality

"handoff document" is one specific, natural keyword, but the description includes no trigger phrasing or common variations such as "session summary", "context compaction", or "hand off the session". This matches the anchor for some relevant keywords while missing common variations and synonyms, falling short of good keyword coverage.

3 / 5

Distinctiveness Conflict Risk

The description carves out a fairly distinct niche (agent handoff / session continuity) and would rarely be confused with unrelated skills, matching "mostly distinct; minor overlap risk". It is not a 5 because without explicit triggers, "compact the conversation" could overlap with general summarization or context-compaction 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

igouss/gitweb-rs

Path

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