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
72%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/handoff-resume/SKILL.mdQuality
Discovery
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 adequately communicates both what the skill does and when to use it, with a clear niche that reduces conflict risk. However, it could benefit from more concrete action descriptions and broader trigger term coverage to help users who might phrase their need differently (e.g., 'resume where I left off').
Suggestions
Add more natural trigger terms users would say, such as 'resume', 'pick up where I left off', 'continue previous work', or 'restore previous session'.
Make the actions more concrete by specifying what 'restores session context' means — e.g., 'loads previous goals, progress, and open tasks from the handoff document'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | It names the domain (handoff/session continuity) and describes some actions ('reads the latest unrestored handoff document and restores session context'), but the actions are not very concrete — it doesn't specify what 'restoring session context' entails or what a handoff document contains. | 2 / 3 |
Completeness | The description explicitly answers both what ('reads the latest unrestored handoff document and restores session context') and when ('when starting a new session and wanting to continue from a previous handoff'), providing clear trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes relevant terms like 'handoff', 'session', 'context', and 'previous' which users might say, but misses common variations like 'resume', 'pick up where I left off', 'continue work', or 'restore state'. The term 'unrestored' is technical jargon unlikely to be used by users. | 2 / 3 |
Distinctiveness Conflict Risk | The concept of reading handoff documents and restoring session context is a clear, distinct niche. It's unlikely to conflict with other skills since 'handoff document' and 'session restoration' are very specific concepts. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
70%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 sequencing and good branching logic for different scenarios. Its main weakness is that some key operations (frontmatter parsing, file archiving) are described abstractly rather than with executable commands. Minor verbosity in the 'When to Use' section could be trimmed.
Suggestions
Add executable code for parsing YAML frontmatter and filtering by 'restored: false' instead of describing it abstractly
Include a concrete command or code snippet for updating the frontmatter fields (restored, restored_at) and moving the file to _archive/
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient but includes some unnecessary sections like 'When to Use' with obvious cases and 'Don't use when' that Claude could infer. The 'Pairs With' section adds minor value. The core process steps are reasonably lean though. | 2 / 3 |
Actionability | Provides concrete bash commands and a clear process, but key operations like updating YAML frontmatter and moving files to archive lack executable code examples. The 'filter for restored: false' step is described abstractly rather than with concrete commands. | 2 / 3 |
Workflow Clarity | The 5-step process is clearly sequenced with explicit branching logic (one handoff vs multiple vs none). Step 5 includes a well-ordered sub-workflow for context restoration with a clear priority sequence (read files first, then review state, then check git, then note failures, then continue). | 3 / 3 |
Progressive Disclosure | For a skill of this size and scope, the content is well-organized with clear sections. References to companion skills (handoff, handoff-list) are one level deep and clearly signaled. No monolithic walls of text or deeply nested references. | 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- lucianghinda/superpowers-ruby
- Commit
c037ce3
- 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.