CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

create-handoff

Create handoff document for transferring work to another session

Quality

74%

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

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.

A strong, highly actionable skill: the exact YAML format, concrete commands, and named MCP tools leave nothing abstract. The main improvements are cosmetic (a malformed header, a stray horizontal rule) and removing a couple of duplicated emphasis lines.

DimensionReasoningScore

Conciseness

The body is dense with executable templates, exact bash commands, and precise MCP tool names, with no explanations of concepts Claude already knows. Minor over-explanation could be trimmed: the requirement that goal:/now: be named exactly is stated twice ('The statusline parser looks for EXACTLY goal: and now: - nothing else works' duplicates the earlier 'they MUST be named exactly this'), and the 'IMPORTANT: Replace {session_name}...' note restates placeholders already shown in the parameters.

4 / 5

Actionability

Fully executable guidance throughout: copy-paste bash commands for the session-name fallback chain, an exact YAML template with concrete example file paths, the exact MCP tool names (mcp__opc-memory__index_artifacts, mcp__opc-memory__mark_handoff) with parameter blocks, and a ready-to-use confirmation message. It is not 4 because no concrete step requires the reader to fill in significant gaps; the only placeholders are inherently data-dependent.

5 / 5

Workflow Clarity

Four clearly sequenced steps (filepath/metadata, write YAML, mark outcome, confirm) with an explicit outcome decision tree (blockers/questions -> SUCCEEDED/PARTIAL_PLUS/ask user) and cross-validation of now: against done_this_session:. Not 5 because checkpoints are missing in places: no guidance if an MCP call fails, and the outcome value to pass for the non-prompt default cases is only implied via the '<USER_CHOICE>' placeholder.

4 / 5

Progressive Disclosure

For a single-purpose, self-contained skill the content is appropriately placed in four numbered sections plus a short notes section, with the bulk being the essential template. Minor organization gaps: the '##. Additional Notes & Instructions' header at line 164 is invalid markdown heading syntax, and the stray '---' at line 106 renders as a rule mid-section; these slightly hurt navigation but structure is otherwise good.

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 states a clear, concrete purpose but is minimal: no use-when trigger guidance and sparse keyword coverage mean it relies on the user already saying 'handoff'. One added sentence with trigger phrases would move it from adequate to strong.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to hand off work, wrap up a session, or transfer context to a new session.'

Include natural trigger variations and synonyms in the description: 'hand off', 'handoff', 'session summary', 'context transfer', 'wrap up'.

Broaden the 'what' to cover the skill's full behavior, e.g. '...records completed tasks, blockers, and decisions in a structured YAML file and marks the session outcome (SUCCEEDED/PARTIAL/FAILED).'

DimensionReasoningScore

Specificity

'Create handoff document for transferring work to another session' names one concrete action (create a handoff document) and its target, matching the anchor for naming a domain with 1-2 concrete actions. It is not 4 because coverage is thin — the skill also marks session outcomes and indexes handoffs into memory, none of which the description conveys.

3 / 5

Completeness

The 'what' is clear (create a handoff document for transferring work), but there is no 'Use when...' clause or any trigger guidance — the 'when' is entirely absent, which per the judging guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

Relevant terms are present ('handoff document', 'transferring work', 'another session') but common natural variations users would say are missing: 'hand off work', 'wrap up the session', 'session summary', 'context transfer'. This matches 'some relevant keywords but missing common variations', not 4's 'good keyword coverage'.

3 / 5

Distinctiveness Conflict Risk

'Handoff... another session' carves a distinct niche that is unlikely to trigger for unrelated skills, matching 'mostly distinct; minor overlap risk'. It is not 5 because it could overlap with closely related session-continuation skills such as the paired /resume_handoff workflow the body references.

4 / 5

Total

13

/

20

Passed

Validation

100%

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

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.