react-ui
Opinionated constraints for building better interfaces with agents.
Install with Tessl CLI
npx tessl i github:Dicklesworthstone/pi_agent_rust --skill react-ui60
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 weak across all dimensions. It reads like a tagline or marketing phrase rather than a functional skill description. It provides no concrete actions, no trigger terms users would naturally use, and no guidance on when Claude should select this skill.
Suggestions
Replace abstract language with specific actions (e.g., 'Defines UI patterns for agent interactions, validates component layouts, generates accessible interface code').
Add a 'Use when...' clause with natural trigger terms (e.g., 'Use when building agent UIs, designing chatbot interfaces, or creating conversational components').
Clarify what 'agents' means in this context and specify the type of interfaces (web, mobile, conversational) to reduce conflict with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague, abstract language ('opinionated constraints', 'better interfaces') without naming any concrete actions. No specific capabilities like 'create', 'validate', 'generate' are mentioned. | 1 / 3 |
Completeness | Missing both 'what' and 'when'. The description doesn't explain what the skill actually does or when Claude should use it. No 'Use when...' clause or equivalent trigger guidance exists. | 1 / 3 |
Trigger Term Quality | Contains no natural keywords users would say. Terms like 'opinionated constraints' and 'interfaces with agents' are technical jargon that users wouldn't naturally use when seeking help. | 1 / 3 |
Distinctiveness Conflict Risk | Extremely generic - 'building better interfaces' could apply to countless skills. 'Agents' is ambiguous and could conflict with any agent-related, UI, or design skill. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an exemplary constraint-based skill file. It's maximally concise with clear MUST/SHOULD/NEVER modifiers, provides specific and actionable guidance (exact properties, values, tool names), and organizes rules into logical categories. The skill respects Claude's intelligence by avoiding explanations of basic concepts while providing precise, copy-paste-ready constraints.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. Every rule is a single line with clear MUST/SHOULD/NEVER modifiers. No unnecessary explanations of what Tailwind, React, or accessibility primitives are—assumes Claude's competence. | 3 / 3 |
Actionability | Highly actionable with specific tool names, exact CSS properties to use/avoid, concrete values (200ms, h-dvh), and CLI commands. Rules are directly applicable without interpretation. | 3 / 3 |
Workflow Clarity | This is a constraint-based skill rather than a multi-step workflow. The single-purpose rules are unambiguous and well-organized by category (Stack, Components, Animation, etc.), making application straightforward. | 3 / 3 |
Progressive Disclosure | Content is appropriately structured with clear section headers. For a constraint-based skill of this size (~80 lines), the flat organization with categorical groupings is ideal. External link to shadcn/ui docs is well-placed. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.