Content
35%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides a well-structured multi-step workflow for extracting design systems from UI images, with clear sequencing and file organization conventions. However, it suffers from significant verbosity—redundantly describing template contents, including generic best practices Claude already knows, and explaining concepts rather than providing executable specifics. The lack of validation checkpoints in a complex multi-step workflow involving subagent delegation is a notable gap.
Suggestions
Remove the 'Template Assets' section entirely or reduce it to a simple file listing—the workflow steps already describe how each template is used, making the summaries redundant.
Cut the 'Best Practices' section drastically; most items are generic advice Claude already knows (e.g., 'Be systematic', 'Engage user interactively'). Keep only project-specific constraints.
Add explicit validation checkpoints after Steps 2, 3, and 4—e.g., verify design system covers all required sections, confirm PRD with user before proceeding, validate final prompt has all substitutions completed.
Make Step 2 more actionable by showing the exact Task tool invocation pattern with a concrete example of how to attach images and reference the template, rather than describing it abstractly.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is very verbose, with extensive sections that describe what templates contain rather than providing actionable content. The 'Template Assets' section redundantly summarizes each template file. 'Best Practices' and 'Notes' sections contain generic advice Claude already knows (e.g., 'Be systematic', 'Engage user interactively'). The content could be cut by 40-50% without losing information. | 1 / 3 |
Actionability | The workflow steps provide a reasonable structure with specific file paths and tool usage patterns, and Step 5 includes executable bash commands. However, most steps describe what to do abstractly ('Use Task tool with general-purpose subagent, providing...') rather than giving concrete, copy-paste-ready examples. The template substitution instructions reference variables but don't show actual content or format. | 2 / 3 |
Workflow Clarity | The 6-step workflow is clearly sequenced with logical dependencies (Step 3 conditional on existing PRD, Step 4 combines outputs of Steps 2-3). However, there are no validation checkpoints—no step verifies the design system extraction quality, PRD completeness, or final prompt correctness before proceeding. For a multi-step workflow involving subagent delegation and file generation, validation/feedback loops are notably absent. | 2 / 3 |
Progressive Disclosure | The skill references three template assets in `assets/` and describes their contents, which is good structure. However, no bundle files were provided, so we can't verify the references resolve. The 'Template Assets' section inlines summaries of each file that are redundant with the workflow steps, and the 'Best Practices' section contains content that could be trimmed or moved to a separate reference file rather than bloating the main skill. | 2 / 3 |
Total | 7 / 12 Passed |