CtrlK
BlogDocsLog inGet started
Tessl Logo

react-ui

Opinionated constraints for building better interfaces with agents.

79

1.41x
Quality

Does it follow best practices?

Impact

99%

1.41x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

87%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is an efficient, highly actionable constraint catalog that assumes competence and avoids teaching known concepts. It scores top marks on conciseness, actionability, and progressive disclosure; the only middle score is workflow clarity, which is inapplicable to a non-sequential reference skill.

DimensionReasoningScore

Conciseness

The body is lean MUST/SHOULD/NEVER bullets with no explaining of what Tailwind, Radix, or compositor props are; it assumes Claude's competence and every line earns its place.

3 / 3

Actionability

Directives are concrete and copy-paste ready (e.g. "NEVER use `h-screen`, use `h-dvh`", "MUST use `text-balance` for headings", "MUST add an `aria-label` to icon-only buttons"); per the instruction-only note, the absence of code is not penalized because the guidance is actionable.

3 / 3

Workflow Clarity

This is a constraint catalog, not a sequenced multi-step workflow, so there are no steps or validation checkpoints; the content is well-organized but has no process sequence to evaluate, matching the middle anchor.

2 / 3

Progressive Disclosure

The skill is a self-contained single file (~75 lines) with no bundle files and well-organized sections, with no nested or deep references; per the rubric, a skill with no need for external references scores 3 with well-organized sections.

3 / 3

Total

11

/

12

Passed

Description

50%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description names its domain and intent but is abstract and trigger-poor: it lists no concrete actions and omits any 'Use when...' guidance, so every dimension lands at the middle anchor. It is distinguishable as a UI skill yet generic enough to risk overlap.

Suggestions

Add an explicit trigger clause, e.g. 'Use when building or styling React UI, components, or frontend interfaces with an agent.'

Replace abstract phrasing with concrete actions, e.g. 'Enforces Tailwind, shadcn/ui, accessibility, and animation constraints for React interfaces.'

Include natural trigger terms users would say ('React', 'UI', 'components', 'frontend') so it surfaces for the right request.

DimensionReasoningScore

Specificity

Quotes the domain ("building better interfaces") and nature ("constraints") but names no concrete actions, matching the 'names domain and some actions' anchor; it is not 1 because a concrete domain is named, and not 3 because no list of specific actions is given.

2 / 3

Completeness

It states what the skill does ("constraints for building better interfaces") but provides no "Use when..." trigger guidance, which per the rubric caps completeness at 2; not 1 because the 'what' is present, not 3 because 'when' is missing.

2 / 3

Trigger Term Quality

"interfaces" and "building" are relevant keywords but common variations a user would actually say ("React", "UI", "frontend", "components") are absent; more natural than the jargon-only 1 anchor, but lacks the broad coverage of 3.

2 / 3

Distinctiveness Conflict Risk

The UI focus is a recognizable niche, but "better interfaces...with agents" is generic enough to overlap with general coding/design skills and lacks React-specific distinct triggers; not 3 (no clearly distinct triggers) and not 1 (clearly UI-domain rather than 'code and documents').

2 / 3

Total

8

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
Dicklesworthstone/pi_agent_rust
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.