Content
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a well-organized conceptual guide to building dynamic terminal UIs with wsh, featuring useful visual pseudocode patterns and sound design principles. Its main weaknesses are the lack of executable code examples (patterns are illustrative rather than actionable) and moderate verbosity in philosophical/principle sections. The skill would benefit significantly from concrete API call examples and validation steps for the multi-step patterns.
Suggestions
Replace at least 2-3 pseudocode pattern examples with actual executable wsh_* tool calls or curl commands, showing the real API invocations needed to create overlays, panels, and named spans.
Add validation checkpoints to multi-step patterns (e.g., check screen dimensions before layout, verify overlay creation succeeded, handle input capture errors).
Trim the 'Composition Philosophy' and 'Design Principles' sections — much of this (terminal aesthetics, disposability) is contextual wisdom Claude can infer; focus on the non-obvious constraints like terminal size thresholds.
Consider splitting the detailed patterns (Dashboard, Browser, Dialog, Canvas, Wizard, etc.) into a separate PATTERNS.md reference file, keeping SKILL.md as a concise overview with the layer selection guide and 1-2 key examples.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is moderately verbose — the layered capability descriptions and design principles sections contain some unnecessary elaboration (e.g., explaining the philosophy of terminal aesthetics, 'the human chose to work in a terminal'). However, the patterns themselves are fairly lean with useful pseudocode layouts. Some tightening is possible, particularly in the introductory prose and the composition philosophy section. | 2 / 3 |
Actionability | The skill provides visual pseudocode representations of UI layouts rather than executable code or actual API calls. While the patterns are illustrative and give a clear mental model, they are not copy-paste ready — there are no actual wsh commands, tool invocations, or code snippets that Claude could directly execute. The introductory note about wsh_* tools or HTTP fallback adds some guidance but the patterns themselves remain abstract. | 2 / 3 |
Workflow Clarity | The skill presents clear design patterns with logical sequences (e.g., the wizard pattern shows step progression, alt screen mode shows enter/work/exit flow). However, there are no explicit validation checkpoints — no guidance on checking if overlays rendered correctly, handling errors when screen operations fail, or verifying terminal size before proceeding. The 'choose a layer' decision tree is helpful but lacks error recovery paths. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear headers and logical sections, but it's a monolithic document with no references to external files for detailed API usage, advanced patterns, or examples. The reference to 'wsh:tui' and 'skills/core/' in the preamble provides some cross-referencing, but the main body could benefit from splitting detailed patterns into separate reference files, especially given its length (~250 lines of content). | 2 / 3 |
Total | 8 / 12 Passed |