create-handoff

Create handoff document for transferring work to another session

Quality

60%

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

Quality

Content

67%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 content is a well-structured, actionable instruction skill with a clear multi-step workflow and built-in validation checkpoints. Its main weakness is moderate redundancy in the goal/now and field-name warnings, which slightly hurts token efficiency.

Suggestions

Consolidate the repeated goal/now and "do not use alternative field names" warnings into one authoritative callout to trim redundant tokens.

Tighten the closing "Additional Notes" into concise imperatives, e.g. 'Include more detail when needed; prefer file:line references over large code blocks.'

Add an explicit verification checkpoint after mark_handoff (e.g., confirm the returned outcome matches the intended status) to fully close the database-write feedback loop.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete templates and commands, but repeats the goal/now requirement and "do not use alternative field names" warning across the intro, template comments, and field guide, plus some soft guidance ("more information, not less") that could be tightened.	3 / 5
Actionability	It provides a concrete bash fallback chain, an exact YAML template, named MCP tools with parameters, and explicit placeholder-substitution instructions, which is mostly executable with only minor templated-field gaps.	4 / 5
Workflow Clarity	A clear 4-step sequence with outcome-determination logic and a checkpoint for the blockers case, plus a guard against the stale "latest handoff" default; minor validation gaps remain in the MCP write flow.	4 / 5
Progressive Disclosure	A single self-contained file (no bundle directories present) with clear numbered section headers and a field guide; well-organized with no nested references, fitting the strong simple-skill structure anchor.	4 / 5
	Total	15 / 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 specific and distinct but lacks a "Use when" trigger clause and broader keyword coverage, which together cap most dimensions at the midpoint. Adding an explicit trigger phrase and synonyms (e.g., "hand off context", "resume") would raise completeness and trigger quality.

Suggestions

Add an explicit 'Use when...' trigger clause, e.g. 'Use when handing off work to a new session or transferring context to another agent.'

Include natural synonyms and trigger terms users would say, such as 'hand off work', 'context transfer', 'summarize session', or 'resume work'.

List one or two additional concrete actions (e.g., 'summarize context and mark session outcome') to push specificity toward comprehensive coverage.

Dimension	Reasoning	Score
Specificity	"Create handoff document for transferring work to another session" names the domain and one concrete action but offers no further specific actions, matching the anchor that lists 1-2 concrete actions without comprehensive coverage.	3 / 5
Completeness	The description gives a clear "what" (create a handoff document) but no "when" or "Use when..." trigger guidance, which the rubric caps at 3 for missing explicit trigger clauses.	3 / 5
Trigger Term Quality	Terms like "handoff", "session", and "transferring work" are relevant, but common synonyms and variations such as "context transfer", "summarize context", or "resume" are missing, so keyword coverage is partial rather than comprehensive.	3 / 5
Distinctiveness Conflict Risk	Creating handoff documents for inter-session transfer is a distinct niche with minor overlap risk against general summarize/notes skills, fitting the "mostly distinct" anchor.	4 / 5
	Total	13 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: stephenfeather/opc
Path: skills/create-handoff/SKILL.md
Commit: 948072f

Reviewed: 3 days 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.