Content
26%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The body is structurally clean but substantively empty: every section restates the same vague description and the only pointer to real content is an external GitHub link. An agent reading this skill gains no actionable instruction — the 'Instructions' section describes what the skill would provide without providing it.
Suggestions
Replace the repeated description in the Instructions section with the actual concrete constraints and rules the skill enforces (the 'opinionated constraints' themselves), stated as directives an agent can follow.
Remove the redundant restatement across the Overview, 'When to Use', and Instructions sections and use that token budget for at least one concrete example of applying a constraint to a real interface element.
Instead of (or alongside) the external repository link, bundle the detailed guidance into local reference files (e.g., references/constraints.md) and link to them from the body, so the skill is self-contained and one level deep.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is short and explains nothing Claude already knows, but the same vague sentence ("opinionated, evolving constraints to guide agents when building interfaces") is restated in three sections (Overview, When to Use, Instructions), which is unnecessary repetition that could be tightened. It is not anchor 2 because there are no padded explanatory sections, only redundant restatement in an otherwise minimal body. | 3 / 5 |
Actionability | The Instructions section states only "This skill provides guidance and patterns for opinionated, evolving constraints to guide agents when building interfaces" — it describes the skill without providing a single concrete rule, command, code example, or specific directive. This matches anchor 1: entirely abstract, only describes rather than instructs. | 1 / 5 |
Workflow Clarity | There are no steps, no sequence, and no identifiable single action to perform — the skill's actual guidance is entirely absent from the body. The simple-skill exception cannot apply because no unambiguous action is stated anywhere. This matches anchor 1 (steps missing or incoherent). | 1 / 5 |
Progressive Disclosure | The body is under 50 lines with clear section headers (Overview, When to Use, Instructions), and no bundle files exist to reference, so structure itself is adequate. It falls short of 5 only because the substantive content lives behind an external link ("see the [source repository](https://github.com/ibelick/ui-skills)") rather than in bundled, one-level-deep reference files, leaving the skill with no navigable detail. | 4 / 5 |
Total | 9 / 20 Passed |