CtrlK
BlogDocsLog inGet started
Tessl Logo

handoff

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

54

Quality

61%

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 ./skills/handoff/SKILL.md

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

SKILL.md
Quality
Evals
Security

Quality

Content

65%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 concise and well-organized for a simple instruction skill, but it lacks concrete executable specifics (e.g. how to resolve the OS temp dir) and has no sequenced workflow or validation checkpoint for the sensitive redaction step.

Suggestions

Add concrete guidance for locating the temp directory (e.g. '$TMPDIR on macOS/Linux, %TEMP% on Windows) so the save step is executable.

Sequence the steps explicitly (summarize -> redact secrets -> add suggested skills -> save to temp) and add a validation checkpoint confirming no secrets remain before saving.

Specify how to identify 'suggested skills' (e.g. list skills invoked in this session) so the section is actionable rather than open-ended.

DimensionReasoningScore

Conciseness

The body is lean, imperative, and assumes Claude's competence with no concept over-explanation; it is efficient with only minor phrasing that could be tightened, sitting just below the ideal-lean anchor.

4 / 5

Actionability

It gives clear high-level directives ('Save to the temporary directory', 'Include a suggested skills section', 'Redact any sensitive information') but provides no concrete commands, code, or specifics on locating the OS temp dir, leaving the execution details implicit.

3 / 5

Workflow Clarity

There is no sequenced step list; the directives are a flat set of instructions with implicit ordering and no validation checkpoint for risky actions like secret redaction, matching the 'steps listed but validation gaps' anchor and capping at 3 per the redaction/batch guidance.

3 / 5

Progressive Disclosure

This is a short single-purpose skill with no bundle files and no need for external references; the body is well-organized into clear imperative lines, which the simple-skill exception treats as a 5.

5 / 5

Total

15

/

20

Passed

Description

58%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 names a concrete, fairly distinct action, but it omits an explicit 'Use when...' trigger and leans on the argument-hint for context, capping completeness and trigger coverage.

Suggestions

Add an explicit trigger clause, e.g. 'Use when handing off work to a fresh agent or starting a new session mid-task'.

Include natural user-spoken synonyms like 'summarize this chat' or 'brief the next session' to improve trigger term coverage.

Optionally surface 1-2 more concrete sub-actions (e.g. 'lists suggested skills and redacts secrets') to lift specificity toward 5.

DimensionReasoningScore

Specificity

The description names the domain (handoff/compacting a conversation) and one concrete action ('Compact the current conversation into a handoff document'), but stops short of multiple specific sub-actions, placing it above the single-action anchor yet below comprehensive coverage.

4 / 5

Completeness

A clear 'what' is stated but the 'when' is only weakly implied via the argument hint; there is no explicit 'Use when...' trigger clause, which the rubric caps at 3.

3 / 5

Trigger Term Quality

It surfaces 'handoff', 'conversation', and 'next session', which are relevant but lacks common user-spoken synonyms like 'summarize this chat' or 'brief the next agent', and has no file-extension or alias coverage.

3 / 5

Distinctiveness Conflict Risk

The handoff/compaction niche is fairly distinct with limited overlap risk against other skills, though the broad 'summarize' framing could lightly overlap with general summarization skills.

4 / 5

Total

14

/

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.

Validation15 / 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
mayank-arora/agent-skills
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.