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

75%

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

Quality

Content

75%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, and concise read-only listing skill with a clear multi-step workflow and good conditionals. It consistently lands above the midpoint across all dimensions but stops short of the top anchors due to minor padding and the absence of explicit validation/error-recovery checkpoints.

Suggestions

Tighten or relocate the 'Announce at start' line and the Overview's 'Helps you decide...' sentence to earn the top conciseness anchor.

Add an explicit note for handling malformed/missing frontmatter in Step 2 to strengthen workflow clarity's error-recovery angle.

Make Step 2's parse guidance concrete (e.g., a one-line awk/yq snippet) to push actionability toward fully copy-paste ready.

DimensionReasoningScore

Conciseness

The body is efficient with executable commands and templates, but small additions like 'Announce at start' and 'Helps you decide...' are minor padding that could be trimmed.

4 / 5

Actionability

Provides concrete, executable `ls` commands, explicit frontmatter fields to extract, and ready-to-use table and empty-state templates, with only minor gaps in the parse step.

4 / 5

Workflow Clarity

A clear 4-step sequence (Scan, Parse, Display, Offer) with explicit conditional branches for the empty and active-handoff cases; read-only so the destructive-validation cap does not apply, but it lacks explicit error-handling checkpoints.

4 / 5

Progressive Disclosure

Well-organized into Overview, When to Use, Process, and Pairs With sections with no nested or buried references; self-contained with no bundle files, though slightly above the simple-skill line count.

4 / 5

Total

16

/

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 clear, third-person description that explicitly covers what the skill does and when to use it, with concrete enumerated fields. It sits solidly above the midpoint but lacks the multi-action breadth and synonym coverage needed for the top anchor.

Suggestions

Add 1-2 more concrete verbs beyond 'lists' (e.g., 'scans, parses, and displays') to push specificity toward a 5.

Include common synonyms or phrasings a user might say (e.g., 'handoff history', 'review past handoffs') to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Names the domain ('handoff documents') and a concrete action ('lists') with an enumerated field set (status, date, topic, branch); not quite a comprehensive multi-action list, so just below a 5.

4 / 5

Completeness

Explicitly answers both 'what' (lists active/archived handoffs with their fields) and 'when' ('Use when viewing available handoff documents'), but the trigger could be slightly more specific.

4 / 5

Trigger Term Quality

Natural phrases like 'viewing available handoff documents' and 'active and archived handoffs' align with what a user would say, though a few synonyms/variations are missing.

4 / 5

Distinctiveness Conflict Risk

The 'handoff documents' niche is clear and the listing purpose distinguishes it from sibling create/resume skills, with only minor overlap 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.

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.