CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

create-handoff

Create handoff document for transferring work to another session

Quality

68%

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/create_handoff/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 delivers a tight, executable workflow: concrete commands, an exact template, an explicit user gate, and failure-path notes. Remaining polish is minor — undefined terminology ("ledger"), one malformed heading, redundant emphasis of the field-name constraint, and no self-validation of the written handoff.

DimensionReasoningScore

Conciseness

The body is nearly all project-specific instruction (exact paths, an exact YAML template, copy-paste commands) with no explanation of concepts Claude already knows; minor trimming is possible since the "use exactly goal:/now:" constraint is stated three times ("CRITICAL: Use EXACTLY this YAML format", "they MUST be named exactly this", "The statusline parser looks for EXACTLY goal: and now:") and the Additional Notes partially restate the intro.

4 / 5

Actionability

Every step is backed by executable material: copy-paste bash for deriving the folder name and for indexing/marking, an exact YAML template, exact AskUserQuestion options, and a final response template. Minor gaps remain — "session: {session-name from ledger}" references an undefined "ledger" (step 1 derives the name from handoff folders), and the opc/scripts/ commands assume an unexplained project layout.

4 / 5

Workflow Clarity

Four clearly numbered steps with a user-response gate before marking and a note explaining the failure path ("Database marking was not available"); it is not 5 because there is no validation of the written YAML itself and no recovery loop if artifact_mark.py fails. The destructive/batch cap does not apply since this is a single-file write plus index, not a batch or destructive operation.

4 / 5

Progressive Disclosure

A well-sectioned single-file skill with no bundle files; the YAML template and commands genuinely belong inline and nothing warrants splitting into references. It is not 5 because at ~137 lines it exceeds the simple-skill threshold, the final heading is malformed ("##."), and repeated warning blocks could be consolidated for easier navigation.

4 / 5

Total

16

/

20

Passed

Description

48%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 names a concrete, fairly distinct capability but is minimal: one action, no explicit "Use when..." trigger guidance, and sparse natural-language trigger terms. Adding trigger phrases and a capability summary would move it firmly into the good-example range.

Suggestions

Add an explicit trigger clause, e.g., "Use when ending a session and transferring work to a new session, or when the user asks to hand off work or create a handoff document."

Enumerate the concrete actions the skill performs, e.g., "Creates a structured YAML handoff capturing goals, completed tasks, blockers, decisions, and next steps; asks the user to grade the session outcome and indexes it; supports resuming via /resume_handoff."

Include natural trigger synonyms such as "hand off work", "session transfer", and "context transfer" so the description matches how users actually phrase the request.

DimensionReasoningScore

Specificity

"Create handoff document" names the domain with a single minimal action, mirroring the anchor example "Processes PDF files"; it lists no secondary capabilities (outcome marking, indexing, resume support) so it does not reach the 1-2 concrete actions anchor, but it is above the entirely-vague anchor because the domain is concrete.

2 / 5

Completeness

The description clearly answers "what" ("Create handoff document for transferring work") but contains no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines; the purpose phrase only weakly implies "when".

3 / 5

Trigger Term Quality

Terms like "handoff document", "transferring work", and "another session" are phrases a user might naturally say, but common variations and synonyms ("hand off", "session summary", "context transfer", "resume") are missing, matching the "some relevant keywords but missing common variations" anchor.

3 / 5

Distinctiveness Conflict Risk

"handoff document" for "transferring work to another session" carves a mostly distinct niche with only minor overlap risk against session-summary or memory skills; it falls short of the clear-niche anchor because the terse description offers no distinctly differentiating trigger phrases.

4 / 5

Total

12

/

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

referenced_paths_exist

Referenced path issues: 2 missing, 2 deeper-than-1-level

Warning

Total

15

/

16

Passed

Repository

parcadei/Continuous-Claude-v3

Path

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