design-handoff

Generate developer handoff specs from a design. Use when a design is ready for engineering and needs a spec sheet covering layout, design tokens, component props, interaction states, responsive breakpoints, edge cases, and animation details.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

100%

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

A well-structured, lean skill body that provides a concrete output template and clear category checklists without over-explaining known concepts. The malformed `**~~design tool**` connector syntax is a minor polish issue but does not materially weaken any dimension.

Suggestions

Fix the malformed connector syntax in 'If Connectors Available' (`**~~design tool**` / `**~~project tracker**`) so the conditional guidance renders and reads correctly.

Consider extracting the full output template into a referenced file if the body grows, to keep the overview scannable.

Dimension	Reasoning	Score
Conciseness	The body is lean and list-driven with no padding or explanation of concepts Claude already knows (e.g. it never defines 'design token' or 'breakpoint'); the inline output template earns its tokens as the actual deliverable format.	3 / 3
Actionability	It supplies a concrete, copy-paste-ready markdown output template with structured tables (tokens, components, states, breakpoints, animation) plus per-category checklists, giving executable guidance rather than vague direction.	3 / 3
Workflow Clarity	This is a single-purpose generation task with a clear structure (input source -> sections to cover -> output template); per the simple-skills note, no validation checkpoint is required for a non-destructive spec-generation task.	3 / 3
Progressive Disclosure	The skill is self-contained with well-organized sections and a single one-level external pointer (CONNECTORS.md); no bundle files exist and no nested references are introduced, so the single-file organization is appropriate.	3 / 3
	Total	12 / 12 Passed

Description

85%

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, third-person description with an explicit Use-when trigger and a comprehensive concrete list of what the spec covers. Its main weakness is limited variety of natural trigger terms, which could be broadened.

Suggestions

Broaden trigger term coverage with phrases users naturally say, e.g. 'design to dev', 'developer handoff', 'Figma to spec', or 'handoff documentation'.

Consider mentioning the Figma/screenshot input modality directly in the description so the trigger matches design-tool contexts.

Dimension	Reasoning	Score
Specificity	It enumerates multiple concrete deliverables ('layout, design tokens, component props, interaction states, responsive breakpoints, edge cases, and animation details'), conveying capability concretely rather than abstractly.	3 / 3
Completeness	It explicitly answers both what ('Generate developer handoff specs from a design') and when ('Use when a design is ready for engineering and needs a spec sheet...') with an explicit trigger clause.	3 / 3
Trigger Term Quality	It includes relevant natural terms ('design', 'handoff specs', 'spec sheet', 'ready for engineering') but lacks common variations like 'Figma', 'design to dev', or 'developer handoff' that a user might actually say.	2 / 3
Distinctiveness Conflict Risk	It occupies a clear niche (design-to-engineering handoff) with distinct triggers, making it unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 12 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
relative_links	Relative link issues: 1 suspicious	Warning

	Total	14 / 16 Passed

Repository: anthropics/knowledge-work-plugins
Commit: f96c57c

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.