handoff-list
Use when viewing available handoff documents — lists active and archived handoffs with their status, date, topic, and branch
67
80%
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-list/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 is well-structured with an explicit 'Use when' trigger clause and clearly defines its niche around handoff document listing. Its main weakness is that it describes only a single action (listing) and could benefit from richer trigger terms to capture more natural user phrasings. The specificity of the metadata fields (status, date, topic, branch) helps distinguish it but the overall capability scope feels narrow.
Suggestions
Add more natural trigger term variations such as 'show handoffs', 'handoff list', 'project handover', 'what handoffs exist' to improve discoverability.
If the skill supports additional actions beyond listing (e.g., filtering, searching, or opening handoffs), mention them to increase specificity of capabilities.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names a specific domain (handoff documents) and describes the action (lists active and archived handoffs with status, date, topic, and branch), but it only describes one action (listing/viewing) rather than multiple concrete actions. | 2 / 3 |
Completeness | The description explicitly answers both 'what' (lists active and archived handoffs with their status, date, topic, and branch) and 'when' (Use when viewing available handoff documents), with a clear 'Use when...' clause at the beginning. | 3 / 3 |
Trigger Term Quality | Includes some relevant terms like 'handoff documents', 'active', 'archived', 'status', 'branch', but misses common variations a user might say such as 'show handoffs', 'handoff list', 'project handoffs', or 'handover'. The term 'handoff' is somewhat niche and may not cover all natural phrasings. | 2 / 3 |
Distinctiveness Conflict Risk | The description targets a very specific niche — viewing/listing handoff documents with specific metadata fields. This is unlikely to conflict with other skills due to the unique 'handoff documents' domain. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured skill for a straightforward task. It provides concrete commands, clear output formatting, and good workflow sequencing. Minor verbosity in the 'When to Use' section and the announcement directive slightly reduce token efficiency, but overall the skill is actionable and easy to follow.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient but includes some unnecessary sections like 'When to Use' which lists obvious scenarios Claude can infer. The 'Announce at start' directive and 'Pairs With' section add modest value but the overall content could be tighter. | 2 / 3 |
Actionability | Provides concrete bash commands for scanning directories, specific frontmatter fields to extract, exact table format for output, and clear fallback messaging when no handoffs exist. The guidance is copy-paste ready and leaves no ambiguity about what to do. | 3 / 3 |
Workflow Clarity | The four steps are clearly sequenced (scan → parse → display → offer next action) with explicit output formats for both success and empty states. This is a read-only, non-destructive operation so validation checkpoints aren't critical, and the workflow is unambiguous. | 3 / 3 |
Progressive Disclosure | For a simple, single-purpose skill under 50 lines with no need for external references, the content is well-organized with clear sections. The 'Pairs With' section provides appropriate one-level-deep navigation to related skills. | 3 / 3 |
Total | 11 / 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.