CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ac-handoff-creator

Create handoff packages for session transitions. Use when ending sessions, preparing for continuation, saving session state, or creating resumable context.

Quality

76%

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/ac-handoff-creator/SKILL.md

The canonical home for this skill is ac-handoff-creator in fernandezbaptiste/Skrillz

SKILL.md
Quality
Evals
Security

Quality

Content

72%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, token-efficient overview that correctly defers implementation to the bundled script and documents the output schema. The main weakness is the Workflow section, which lists abstract phase names without executable commands or any validation step for the saved handoff.

Suggestions

Attach concrete commands or API calls to each Workflow step (e.g., 'Capture: creator._gather_progress(); Summarize: creator._generate_summary()'), or replace the phase list with a single end-to-end snippet.

Add a validation checkpoint: after saving, reload with 'await creator.load_current_handoff()' and confirm required fields (progress, context, next_actions) are present before considering the handoff complete.

Trim the duplicated opening sentence ('Create handoff packages for seamless session transitions.') since the Purpose section repeats it almost verbatim.

DimensionReasoningScore

Conciseness

The body is lean with no explanations of concepts Claude already knows, and the JSON example documents the output schema usefully. It misses 5 due to minor redundancy: the opening line 'Create handoff packages for seamless session transitions' is immediately restated by the Purpose section.

4 / 5

Actionability

The Quick Start gives concrete code that matches the real bundle API (HandoffCreator, async create_handoff — verified in scripts/handoff_creator.py), and the JSON example shows the exact output shape. It is not copy-paste ready: 'project_dir' is undefined, the bare 'await' lacks an async context, and the import path assumes a specific working directory.

4 / 5

Workflow Clarity

The five-step Workflow (Capture, Summarize, Extract, Plan, Save) provides a sequence but each step is a one-line abstraction with no commands or API calls attached, and no validation checkpoint exists (e.g., verifying the saved package reloads correctly). This matches the anchor 'steps listed but validation gaps; checkpoints missing or implicit' rather than 4, which requires most checkpoints with executable per-step commands.

3 / 5

Progressive Disclosure

The body is a concise overview with well-organized sections (Quick Start, Workflow, Integration, API Reference) and a single clearly signaled one-level-deep reference ('See scripts/handoff_creator.py for full implementation') that points to a real bundle file. Implementation detail is appropriately deferred to the script with no nested references.

5 / 5

Total

16

/

20

Passed

Description

70%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 solid description with an explicit what/when structure and natural trigger phrases. The main weakness is that the capability statement names only a single action, leaving the concrete work inside a handoff package unstated.

Suggestions

Expand the 'what' with the concrete sub-actions, e.g., 'Capture progress, summarize session context, extract decisions and blockers, and plan next actions into a resumable handoff package.'

Add natural trigger synonyms such as 'handoff', 'pausing work', or 'picking up where you left off' to broaden trigger coverage.

DimensionReasoningScore

Specificity

The description names the domain ("session transitions") and a single concrete action ("Create handoff packages"), matching the anchor for domain plus 1-2 concrete actions but not comprehensive coverage. It does not reach 4 because only one action is named — the sub-steps of what a handoff package involves (capture progress, summarize context, plan next actions) are absent.

3 / 5

Completeness

Both parts are present: a clear "what" ("Create handoff packages for session transitions") and an explicit "when" clause with four concrete trigger phrases. It sits between anchors 4 and 5 — the "when" is 5-level, but the "what" is a single undetailed action, so the "what" could be more explicit.

4 / 5

Trigger Term Quality

Natural trigger phrases like "ending sessions", "saving session state", and "creating resumable context" are phrases users would plausibly say, giving good keyword coverage. It falls short of 5 because common synonyms such as "handoff", "pause/resume work", or "pick up where you left off" are missing.

4 / 5

Distinctiveness Conflict Risk

The handoff-package/session-transition niche is mostly distinct with clear triggers. Minor overlap risk remains with closely related session/state management skills (e.g., session tracking or context compaction) whose triggers like "saving session state" could also apply.

4 / 5

Total

15

/

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

fernandezbaptiste/Skrillz

Path

.claude/skills/ac-handoff-creator/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.