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

62

Quality

73%

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

Quality

Content

68%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 skill body with a clear multi-step process. Its main weakness is the lack of validation/verification around the destructive archive-and-mark step, which limits workflow clarity.

Suggestions

Add an explicit validation step after archiving (e.g., confirm the file moved to docs/handoffs/_archive/ and frontmatter now shows restored: true) with a fix-and-retry loop.

Provide executable code or a precise command for the frontmatter update in Step 4 rather than describing the change in prose.

Tighten the "Announce at start" directive or fold it into the overview to remove a small amount of non-essential scaffolding.

DimensionReasoningScore

Conciseness

The body is efficient and assumes Claude's competence without explaining known concepts; only minor phrasing could be trimmed (e.g., the standalone "Announce at start" line).

4 / 5

Actionability

Provides concrete bash commands and a copy-paste presentation template, but the frontmatter mutation step ("Set restored: true, Add restored_at: ...") is described rather than given as executable code.

4 / 5

Workflow Clarity

The 5-step process is clearly sequenced, but the destructive archive-and-mark operation (move file + mutate frontmatter) has no validation or feedback loop, capping this dimension at 3 per the rubric.

3 / 5

Progressive Disclosure

Well-organized with clear section headers and a self-contained overview; the only references are one-level-deep pointers to sibling skills, with minor organization gaps.

4 / 5

Total

15

/

20

Passed

Description

78%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 description that clearly states both the trigger condition and the concrete actions taken, with natural user-facing language. It is specific enough to be distinguishable from sibling handoff skills.

DimensionReasoningScore

Specificity

Names the domain and 1-2 concrete actions ("reads the latest unrestored handoff document", "restores session context") but coverage is not comprehensive, matching the score-3 anchor.

3 / 5

Completeness

Explicitly answers both what (reads/restores the handoff) and when ("Use when starting a new session and wanting to continue from a previous handoff") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural phrases a user would say ("starting a new session", "continue from a previous handoff") with good keyword coverage, just missing a few synonyms.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (unrestored handoff resume) with distinct triggers, but has minor overlap risk with sibling skills like handoff-list and handoff creation.

4 / 5

Total

16

/

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.

Validation16 / 16 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.