allout/ui
Any UI related work **MUST** reference this before you start.
56
Quality
56%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Discovery
0%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is critically deficient across all dimensions. It functions more as a directive ('MUST reference this') than a description of capabilities, providing no information about what the skill actually does or specific scenarios for its use. The vague 'UI related work' scope makes it impossible to distinguish from other potential UI-related skills.
Suggestions
Replace the directive with concrete actions: specify what UI tasks this skill handles (e.g., 'Creates React components, implements responsive layouts, applies design tokens').
Add a 'Use when...' clause with specific trigger terms users would naturally say (e.g., 'Use when building UI components, styling interfaces, working with CSS, or implementing designs').
Narrow the scope to a distinct niche - 'UI related work' is too broad. Specify the framework, design system, or type of UI work this skill specializes in.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. 'UI related work' is extremely vague and abstract - it doesn't specify what actions are performed (design, code, review, test, etc.). | 1 / 3 |
Completeness | Fails to answer 'what does this do' entirely - only states it must be referenced. No 'Use when...' clause or explicit trigger guidance. The 'when' is implied but extremely broad ('any UI related work'). | 1 / 3 |
Trigger Term Quality | Only contains 'UI' as a potential trigger term. Missing natural variations users would say like 'user interface', 'frontend', 'buttons', 'forms', 'layout', 'design', 'components', etc. | 1 / 3 |
Distinctiveness Conflict Risk | 'UI related work' is extremely generic and would conflict with many potential skills (frontend development, design systems, accessibility, component libraries, CSS styling, etc.). | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
79%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality, comprehensive UI skill with excellent actionability and conciseness. The code examples are executable and cover the full range of UI operations. However, the document would benefit from better progressive disclosure through splitting into multiple reference files, and workflow clarity could be improved with explicit validation patterns for complex UI sequences.
Suggestions
Split detailed reference content (Text_Settings fields, Button_Settings fields, Rect manipulation methods) into separate reference files and link to them from the main skill
Add a workflow section with explicit validation checkpoints for common multi-step UI patterns (e.g., creating a modal dialog, building a scrollable list)
Include error handling patterns or common pitfalls section with how to diagnose and fix UI issues
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is dense with actionable information and avoids explaining concepts Claude would already know. Every section provides specific code examples without unnecessary preamble or explanation of basic programming concepts. | 3 / 3 |
Actionability | Excellent executable code examples throughout - every concept is demonstrated with copy-paste ready CSL code. Specific values, asset paths, and complete function implementations are provided rather than pseudocode or vague descriptions. | 3 / 3 |
Workflow Clarity | While individual operations are clear, the skill lacks explicit validation checkpoints for multi-step UI workflows. The 'Best Practices' section provides guidelines but doesn't include verification steps or error recovery patterns for complex UI operations. | 2 / 3 |
Progressive Disclosure | The content is well-organized with clear section headers, but it's a monolithic document (~400 lines) that could benefit from splitting into separate reference files (e.g., Button_Settings reference, Rect manipulation reference). No external file references are provided for advanced topics. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (567 lines); consider splitting into references/ and linking | Warning |
Total | 10 / 11 Passed | |
Install with Tessl CLI
npx tessl i allout/uiReviewed
Table of Contents