handoff-coordinator

Clean transitions between agents and sessions. Use when preparing handoffs, serializing state, bridging context between agents, or coordinating multi-agent workflows.

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/handoff-coordinator/SKILL.md

Quality

Content

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

The body is well-structured with executable Quick Start code and a clear workflow diagram, but it has two material defects: no validation feedback loop for a state-mutating handoff process (capping workflow_clarity), and two broken bundle-file references that defeat navigation. Conciseness and actionability are otherwise solid.

Suggestions

Add an explicit validation feedback loop to the handoff workflow (validate state → on failure, report and re-validate → only proceed when valid), as required for destructive/state-mutating operations to lift workflow_clarity above 3.

Fix or remove the dead references: either create references/AGENT-TRANSITIONS.md and scripts/handoff_protocol.py or drop them from the References and Scripts sections so all listed paths resolve.

Replace the large ASCII workflow diagram with a compact ordered list or table to reduce token cost while preserving the three-stage sequence.

Dimension	Reasoning	Score
Conciseness	Mostly lean with no padding of concepts Claude already knows, but the ~25-line ASCII workflow diagram consumes notable tokens to convey a simple three-stage flow that could be a short list.	4 / 5
Actionability	Provides concrete, executable Python snippets importing HandoffCoordinator with prepare_handoff/execute_handoff calls, plus a JSON package example; minor gaps remain (undefined project_dir, omitted method signatures).	4 / 5
Workflow Clarity	The three-stage Source/Coordinator/Target sequence is clear and lists a "Validate state consistency" step, but there is no validate→fix→retry feedback loop for this state-mutating operation, so per the rubric cap workflow_clarity cannot exceed 3.	3 / 5
Progressive Disclosure	Sections are well organized with one-level-deep References and Scripts listings, but two of six referenced bundle files (references/AGENT-TRANSITIONS.md and scripts/handoff_protocol.py) do not exist, breaking navigation for those paths.	3 / 5
	Total	14 / 20 Passed

Description

83%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 strong description that clearly states purpose and provides an explicit Use-when trigger clause with multiple concrete actions. Third-person voice is maintained throughout. The main weakness is the broad "coordinating multi-agent workflows" phrasing, which slightly dilutes specificity and distinctiveness.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ("preparing handoffs, serializing state, bridging context between agents, or coordinating multi-agent workflows"), but "coordinating multi-agent workflows" is broad, leaving minor coverage gaps versus the comprehensive anchor.	4 / 5
Completeness	Explicitly answers both what ("Clean transitions between agents and sessions") and when ("Use when preparing handoffs, serializing state, bridging context between agents, or coordinating multi-agent workflows") with concrete trigger phrases.	5 / 5
Trigger Term Quality	Good keyword coverage with natural phrases like "preparing handoffs" and "multi-agent workflows," though "serializing state" and "bridging context" lean technical and common synonyms are missing.	4 / 5
Distinctiveness Conflict Risk	Mostly distinct niche around handoffs and state transitions, but "coordinating multi-agent workflows" is broad and risks minor overlap with general agent-orchestration skills.	4 / 5
	Total	17 / 20 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
referenced_paths_exist	Referenced path issues: 2 missing	Warning

	Total	14 / 16 Passed

Repository: fernandezbaptiste/Skrillz
Path: skills/handoff-coordinator/SKILL.md
Commit: 93ed392

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.