CtrlK
BlogDocsLog inGet started
Tessl Logo

handoff-list

Use when viewing available handoff documents — lists active and archived handoffs with their status, date, topic, and branch

64

Quality

76%

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

Quality

Content

77%

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

This is a solid, well-structured skill for a straightforward read-only listing task. The workflow is clearly sequenced with concrete commands and example output formats. Minor verbosity in the 'When to Use' section and the announcement line could be trimmed, but overall the skill is actionable and easy to follow.

Suggestions

Remove or condense the 'When to Use' section — these triggers are self-evident from the skill description and add tokens without new information.

Consider dropping the 'Announce at start' directive, as it's a stylistic preference that doesn't add actionable guidance for the task itself.

DimensionReasoningScore

Conciseness

Mostly efficient but includes some unnecessary sections like 'When to Use' which lists obvious triggers, and the 'Announce at start' line adds marginal value. The 'Pairs With' section is useful but could be more compact.

2 / 3

Actionability

Provides concrete bash commands for scanning directories, specific frontmatter fields to extract, a complete example table output format, and clear fallback messaging when no handoffs exist. Copy-paste ready commands and output templates.

3 / 3

Workflow Clarity

Clear four-step sequential process: scan directories, parse frontmatter, display table, offer next action. Each step is well-defined with specific commands and expected outputs. For this non-destructive read-only operation, validation checkpoints aren't necessary, and the workflow is unambiguous.

3 / 3

Progressive Disclosure

Content is well-organized with clear sections and headers, but everything is inline in a single file. For a skill of this complexity (~60 lines), this is borderline acceptable, but the 'Pairs With' references to related skills provide some navigation. No bundle files exist to reference.

2 / 3

Total

10

/

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 is functional with a clear 'Use when' trigger and a well-defined niche around handoff document listing. Its main weakness is that it describes only a single action (listing) and could benefit from richer trigger terms. The specificity of the domain (handoff documents) makes it distinctive but the capability description is narrow.

Suggestions

Add more natural trigger term variations such as 'show handoffs', 'handoff list', 'project handover', or 'what handoffs exist'

If the skill supports additional actions beyond listing (e.g., filtering, searching, or opening handoffs), mention those to improve specificity of capabilities

DimensionReasoningScore

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 specificity of 'handoff documents' as a concept.

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.