CtrlK
BlogDocsLog inGet started
Tessl Logo

ce-handoff

Create a session handoff for another agent, or resume, find, and read any user-selected continuity source. Use when work or conversation must continue without access to the current session history.

70

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

85%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 well-structured, actionable instruction skill with clear routing, explicit stop/validation checkpoints, and clean one-level-deep progressive disclosure. The main improvement room is trimming a few philosophical framing sentences and making the copyable command example concrete.

Suggestions

Replace the placeholder fenced block with one concrete rendered example (e.g. '/ce-handoff resume /tmp/ce-handoff/last.md') so the copyable command is ready to use.

Tighten the opening 'deliberately open at their edges' paragraph into a single sentence stating the default-vs-restriction rule.

DimensionReasoningScore

Conciseness

Mostly lean, policy-driven prose that assumes Claude's competence; a few framing sentences ('deliberately open at their edges', restating default-vs-restriction) could be trimmed without losing the instruction.

4 / 5

Actionability

Concrete directives throughout ('Read references/create.md before writing anything', 'redact secrets', 'End the creation response with one fenced, copyable command'); the copyable command block is a placeholder rather than a ready example, a minor gap keeping it below 5.

4 / 5

Workflow Clarity

Clear routing into Create/Resume with explicit checkpoints: 'Creation is complete only after confirming the destination contains the handoff' and two 'MUST stop' gates that act as validation/feedback boundaries.

5 / 5

Progressive Disclosure

Body is a concise overview that signals two real one-level-deep references ('Read references/create.md', 'Read references/resume.md') as non-optional loads; content is appropriately split and easy to navigate.

5 / 5

Total

18

/

20

Passed

Description

87%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.

A strong, third-person description that clearly states capabilities and an explicit 'Use when' trigger, with a distinct niche. It could push specificity and trigger-term breadth higher by naming concrete destinations, formats, or more synonyms.

Suggestions

Add a concrete destination or format cue (e.g. 'to a managed /tmp store or a user-named path') to lift specificity toward 5.

Include one or two more natural synonyms (e.g. 'hand off', 'pick up where another agent left off') to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Names several concrete actions ('Create a session handoff', 'resume, find, and read any user-selected continuity source') with good coverage; falls short of a 5 because the actions stay somewhat abstract (no destination/formats named).

4 / 5

Completeness

Explicitly answers both what ('Create a session handoff... resume, find, and read...') and when ('Use when work or conversation must continue without access to the current session history') with a concrete trigger clause.

5 / 5

Trigger Term Quality

Good natural-term coverage ('session handoff', 'resume', 'continue', 'session history') that users would plausibly say; a 5 would require more synonyms/variations, which are thin here.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (cross-agent session continuity without session history) with distinct triggers; minimal realistic overlap with other skills.

5 / 5

Total

18

/

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
EveryInc/compound-engineering-plugin
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.