Content
71%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.
A lean, well-structured instruction-only skill with a genuine validation feedback loop and appropriate externalization of the component contract to a reference file. Its main gap is the total absence of a worked example of the openui output format, which forces Claude to assemble the format from scattered rules.
Suggestions
Add one minimal annotated `openui` fenced code block (e.g., a root component with two children and a computed binding) so the abstract rules have a concrete template to follow.
Make the generation workflow order explicit (choose format, define root, add bindings, run self-check, replace if defective) instead of leaving it implied by section order.
Trim duplicated computation-related constraints in the 'Protocol and interaction' section into a single rule set.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and assumes Claude's competence without explaining known concepts, but sentences like "Do not approximate an unsupported computation with a result that appears live but does not update correctly" restate constraints already covered and could be trimmed. | 4 / 5 |
Actionability | Concrete micro-rules exist ("fenced code block whose language is exactly `openui`", "Children are arrays even when there is only one child", "Use a Deck root for presentations"), but the body contains no example of an actual openui block or component tree, leaving key execution details missing. | 3 / 5 |
Workflow Clarity | The "Output self-check" section provides an explicit validate-then-fix feedback loop ("correct their underlying cause and emit one complete replacement") and construction order is stated ("Define the root first and referenced content afterwards"), but the overall sequence is implicit across sections rather than explicitly ordered. | 4 / 5 |
Progressive Disclosure | The skill is under 50 lines with well-organized sections and a single clearly signaled, one-level-deep reference ([components.md](references/components.md)) that exists on disk as the generated component-contract reference, matching the simple-skill pattern for a top score. | 5 / 5 |
Total | 16 / 20 Passed |