CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

handoff-list

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

Quality

90%

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

SKILL.md
Quality
Evals
Security

Quality

Content

100%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.

An exemplary micro-skill: every section is functional, commands and output formats are exact, and edge cases (empty directories, archived vs. active ordering) are handled explicitly. Nothing material needs improvement for a skill of this scope.

DimensionReasoningScore

Conciseness

The body is lean — a one-sentence overview, three when-to-use bullets, and four terse steps — with no explanations of concepts Claude already knows; the table template, empty-state message, and next-action offer all earn their tokens.

5 / 5

Actionability

Guidance is copy-paste ready: executable scan commands ("ls docs/handoffs/*.md 2>/dev/null"), the exact frontmatter fields to extract (created, topic, branch, trigger, restored), exact table formats, and exact empty-state and offer text cover the active, archived, and no-handoff cases.

5 / 5

Workflow Clarity

The four steps (scan, parse frontmatter, display with an explicit sort order, offer next action) are clearly sequenced with a defined branch for the empty state; the skill is read-only, so no validation checkpoints are required and the simple-skill clarity exception applies.

5 / 5

Progressive Disclosure

This is a small single-file skill with no bundle files and no content that warrants separate references; the sections (Overview, When to Use, The Process, Pairs With) are well-organized, matching the under-50-lines exception for a top score.

5 / 5

Total

20

/

20

Passed

Description

75%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 solid description with an explicit Use-when clause and concrete enumeration of what the listing shows. Its main limitation is a single self-referential trigger phrase: naming the actual user situations (starting a session, reviewing handoff history) and a few more natural phrasings would lift completeness and trigger coverage.

Suggestions

Expand the when-clause with concrete user situations, e.g. "Use when starting a session and unsure if handoffs exist, when reviewing handoff history, or before resuming a handoff".

Add natural trigger synonyms such as "handoff history", "list handoffs", or "show available handoffs" so the description matches more phrasings a user would actually say.

Mention the pairing with handoff-resume in the description to sharpen the boundary between viewing/listing and resuming.

DimensionReasoningScore

Specificity

"lists active and archived handoffs with their status, date, topic, and branch" names the domain plus concrete output fields across two categories, which is more specific than anchor 3's bare action list but rests on a single verb rather than the multiple concrete actions of anchor 5.

4 / 5

Completeness

Both parts are explicit: the what ("lists active and archived handoffs with their status, date, topic, and branch") and the when ("Use when viewing available handoff documents"), but the when-clause is a single, somewhat circular trigger rather than the concrete user situations exemplified at anchor 5.

4 / 5

Trigger Term Quality

Natural terms like "handoff documents", "handoffs", "active", and "archived" give good keyword coverage, but common variations users might say ("handoff history", "list handoffs", "session handoff") are missing, so it falls short of anchor 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

The listing niche is clearly scoped and distinct from unrelated skills, but "viewing available handoff documents" carries minor overlap risk with the closely related sibling skills the bundle itself names (rubypowers:handoff, handoff-resume), matching anchor 4 rather than anchor 5's minimal conflict risk.

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

lucianghinda/superpowers-ruby

Path

skills/handoff-list/SKILL.md

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.