CtrlK
BlogDocsLog inGet started
Tessl Logo

handoff-resume

Use when starting a new session and wanting to continue from a previous handoff — reads the latest unrestored handoff document and restores session context

60

Quality

68%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/handoff-resume/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

62%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured workflow skill with clear step sequencing and good handling of edge cases (multiple handoffs, no handoffs, archived handoffs). The main weaknesses are that some operations lack executable code (frontmatter parsing, file moving) and there's mild verbosity in sections like 'When to Use' that explain obvious contexts. Overall a solid instructional skill that could be tightened.

Suggestions

Add executable code for key operations: parsing YAML frontmatter to check 'restored: false', updating frontmatter fields, and moving files to archive (e.g., using sed/awk or a script invocation).

Trim the 'When to Use' / 'Don't use when' section — these cases are largely inferrable from the overview and add tokens without adding clarity.

DimensionReasoningScore

Conciseness

Mostly efficient but includes some unnecessary sections like 'When to Use' with obvious cases and 'Don't use when' that Claude could infer. The 'Announce at start' line and some explanatory text could be trimmed.

2 / 3

Actionability

Provides concrete steps and bash commands, but key operations like parsing YAML frontmatter, updating frontmatter fields, and moving files lack executable code. The filtering for 'restored: false' is described abstractly rather than with concrete commands (e.g., grep or a script).

2 / 3

Workflow Clarity

Clear 5-step sequential process with explicit branching logic for different scenarios (one handoff, multiple, none). Step 5 has a well-ordered sub-sequence for context restoration. The workflow handles edge cases and provides a logical progression.

3 / 3

Progressive Disclosure

The skill references companion skills (handoff, handoff-list) at the end which is good, but all content is inline in a single file. The 'Pairs With' section provides useful navigation. However, there are no bundle files and no external references for deeper details, though the skill's complexity may not strictly require them.

2 / 3

Total

9

/

12

Passed

Description

75%

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 has good completeness with an explicit 'Use when' clause and a clear niche that minimizes conflict risk. However, it could be more specific about what concrete actions are performed during restoration, and could include more natural trigger term variations that users might use when wanting to resume work.

Suggestions

Add more natural trigger term variations users might say, such as 'resume', 'pick up where I left off', 'restore previous session', or 'load previous context'.

List more specific concrete actions beyond 'restores session context' — e.g., 'loads previous task state, pending items, and conversation history from the handoff document'.

DimensionReasoningScore

Specificity

It names the domain (handoff/session continuity) and describes some actions ('reads the latest unrestored handoff document and restores session context'), but doesn't list multiple concrete actions or detail what 'restoring session context' entails specifically.

2 / 3

Completeness

It explicitly answers both 'what' (reads the latest unrestored handoff document and restores session context) and 'when' ('Use when starting a new session and wanting to continue from a previous handoff'), with a clear trigger clause at the beginning.

3 / 3

Trigger Term Quality

Includes relevant terms like 'handoff', 'session', 'continue', and 'previous', which are somewhat natural. However, it misses common variations users might say such as 'resume', 'pick up where I left off', 'restore state', or 'load context'.

2 / 3

Distinctiveness Conflict Risk

The concept of 'handoff document restoration' is a very specific niche. The terms 'handoff', 'unrestored handoff document', and 'restores session context' are distinctive and unlikely to conflict with other skills.

3 / 3

Total

10

/

12

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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
lucianghinda/superpowers-ruby
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.