handoff

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

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.github/skills/handoff/SKILL.md

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.

The body is admirably concise and provides a concrete executable command plus clear behavioral rules, but it omits a handoff-document structure/template and explicit sequencing. A short structure outline or checklist would round out actionability and workflow clarity.

Suggestions

Add a brief handoff-document skeleton (e.g. sections for Goal, Current state, Next steps, Open questions, Relevant artifacts) so the output is concrete and copy-paste ready.

Express the steps as a short ordered list with an explicit verification checkpoint (e.g. confirm the temp path is writable and the referenced artifacts exist) to raise workflow clarity.

Add minimal section headers (e.g. '## What to include', '## What to avoid') to give the short body clearer structure for navigation.

Dimension	Reasoning	Score
Conciseness	The body is lean with zero padding and no explanation of concepts Claude already knows; every sentence is actionable instruction, matching the 'lean and efficient; every token earns its place' anchor.	5 / 5
Actionability	It gives an executable command (`mktemp -t handoff-XXXXXX.md`) and concrete directives ('read the file before you write to it', 'Reference them by path or URL'), but offers no template or structure for the handoff document itself, leaving a minor gap that keeps it just below fully-executable anchor 5.	4 / 5
Workflow Clarity	As a simple single-purpose skill the action is largely unambiguous and loosely sequenced (generate path → read → write → suggest skills → reference artifacts), but it lacks an explicit numbered sequence or validation checkpoint, fitting 'clear sequence with most checkpoints present; minor gaps' rather than anchor 5.	4 / 5
Progressive Disclosure	At under 50 lines with no external references needed, content is appropriately placed in one short file, but the body uses no section headers to organize the discrete instructions, so it sits at 'good structure; minor organization gaps' rather than the well-organized-sections anchor 5.	4 / 5
	Total	17 / 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, third-person, and clearly communicates the skill's purpose, but it lacks an explicit 'when to use' trigger clause and only names a single concrete action. Adding a Use-when clause with natural trigger phrases would lift completeness and trigger-term quality.

Suggestions

Append an explicit trigger clause, e.g. 'Use when ending a session that another agent will continue, or when the user asks for a handoff/summary for the next session.'

Add a second concrete action verb (e.g. 'summarize and hand off') and natural synonyms like 'handoff', 'summary', 'context transfer' to broaden trigger coverage.

Consider naming the output artifact type more explicitly to further sharpen distinctiveness from generic summary skills.

Dimension	Reasoning	Score
Specificity	Names the domain ('handoff document') and one concrete action ('Compact the current conversation into a handoff document'), but lists only a single action rather than several, matching the '1-2 concrete actions, not comprehensive' anchor and falling below the multi-action anchor 4.	3 / 5
Completeness	It clearly answers 'what' (compact conversation into a handoff document) but provides no explicit 'Use when…' trigger guidance, so per the missing-trigger-clause rule completeness is capped at 3 and does not reach the both-what-and-when anchor 4.	3 / 5
Trigger Term Quality	It contains relevant terms ('handoff document', 'conversation', 'agent') but lacks common synonyms or variations a user might naturally say, fitting the 'some relevant keywords but missing common variations' anchor rather than the broader-coverage anchor 4.	3 / 5
Distinctiveness Conflict Risk	'Handoff document for another agent to pick up' carves a clear niche with distinct triggers and only minor overlap risk with general summary/planning skills, fitting 'mostly distinct; minor overlap risk' better than the fully-comprehensive anchor 5.	4 / 5
	Total	13 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: microsoft/fabric-task-flows
Path: .github/skills/handoff/SKILL.md
Commit: 3764df9

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.