react-ui
Opinionated constraints for building better interfaces with agents.
67
50%
Does it follow best practices?
Impact
99%
1.41xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./tests/ext_conformance/artifacts/agents-mikeastock/skills/react-ui/SKILL.mdQuality
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 too vague and abstract to be useful for skill selection. It fails to specify concrete actions, lacks natural trigger terms users would use, provides no 'when to use' guidance, and is indistinguishable from many potential overlapping skills. It reads more like a tagline than a functional skill description.
Suggestions
Replace abstract language with concrete actions, e.g., 'Enforces UI layout patterns, component hierarchy rules, and interaction guidelines for agent-based interfaces.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when building or reviewing UI for AI agents, chatbots, copilots, or conversational interfaces.'
Specify the domain more precisely to reduce conflict risk — clarify what type of interfaces (web UI, chat UI, dashboard) and what type of agents (AI agents, LLM-based tools) this applies to.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague, abstract language ('opinionated constraints', 'better interfaces') without listing any concrete actions. No specific capabilities like 'create', 'validate', 'generate' are mentioned. | 1 / 3 |
Completeness | The description weakly addresses 'what' (constraints for building interfaces with agents) and completely omits 'when' — there is no 'Use when...' clause or any explicit trigger guidance. | 1 / 3 |
Trigger Term Quality | The terms 'opinionated constraints', 'interfaces', and 'agents' are abstract and not natural keywords a user would say when seeking help. Users are more likely to say things like 'UI design', 'agent UI', or 'build a chatbot interface'. | 1 / 3 |
Distinctiveness Conflict Risk | The description is extremely generic — 'interfaces' and 'agents' could overlap with many skills related to UI development, agent frameworks, API design, or conversational design. There are no distinct triggers to differentiate it. | 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 excellent constraint-based skill file. It is maximally concise, using MUST/SHOULD/NEVER modifiers consistently to communicate priority. Every rule is specific and actionable with concrete utility names, library references, and thresholds. The sectional organization makes it easy to navigate and apply contextually.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every line is a constraint or rule that Claude wouldn't inherently know as project-specific opinion. No explanations of what Tailwind CSS is or how components work—just direct, opinionated rules. Every token earns its place. | 3 / 3 |
Actionability | The rules are concrete and specific: exact utility names (`text-balance`, `tabular-nums`, `h-dvh`), specific libraries (`motion/react`, `tw-animate-css`), exact CLI commands (`npx shadcn@latest add <component>`), and precise thresholds (`200ms`). These are directly actionable constraints, not vague guidance. | 3 / 3 |
Workflow Clarity | This is a constraint-based skill rather than a multi-step workflow skill. The single-purpose nature (apply these rules when building UI) is unambiguous, and the rules are clearly categorized into logical sections. No destructive or batch operations require validation checkpoints. | 3 / 3 |
Progressive Disclosure | Content is well-organized into clear thematic sections (Stack, Components, Interaction, Animation, Typography, Layout, Performance, Design) that are easy to scan. At under 80 lines with no need for external references, the flat structure is appropriate and well-organized. | 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.
- Repository
- Dicklesworthstone/pi_agent_rust
- Commit
47823e3
- 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.