CtrlK
BlogDocsLog inGet started
Tessl Logo

heroui-native

HeroUI Native component library for React Native (Tailwind v4 via Uniwind). Use when building mobile UIs with HeroUI Native — creating Buttons, Cards, TextFields, Dialogs; installing heroui-native; configuring dark/light themes; or fetching component docs. Keywords: HeroUI Native, heroui-native, React Native UI, Uniwind, mobile components.

72

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

75%Weight 40%Scale 1-5

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

The body is highly actionable with executable code and concrete script references organized into clear sections, but loses conciseness to repeated install blocks and fetch-docs reminders. Progressive disclosure is solid with real one-level-deep script references.

Suggestions

Collapse the three installation sections (curl, npm quick install, Expo setup) into a single sequenced install path to remove redundancy.

State the "always fetch component docs before implementing" guidance once in the documentation-access section instead of repeating it three times.

Consider moving the semantic-variants table and theming details into a reference file referenced from SKILL.md to tighten the overview.

DimensionReasoningScore

Conciseness

Mostly efficient with code, tables, and lists, but contains noticeable redundancy: three installation blocks (curl, npm quick install, Expo setup) and the reminder "Always fetch component docs before implementing" / "Always fetch Native docs" repeated three times.

3 / 5

Actionability

Fully executable, copy-paste-ready guidance: concrete npm install commands, provider setup code, compound component examples, theme code, and specific script invocations (e.g. "node scripts/get_component_docs.mjs Button Card TextField") covering the common cases.

5 / 5

Workflow Clarity

The Expo setup is a clear numbered sequence (install → create global.css → wrap providers) with concrete commands; no explicit validation checkpoints, but the operation is non-destructive setup so the missing-feedback cap does not apply.

4 / 5

Progressive Disclosure

Well-sectioned body with clearly signaled, one-level-deep references to real scripts (list_components.mjs, get_component_docs.mjs, get_theme.mjs, get_docs.mjs) and concrete MDX URLs; minor gap is that theming/component-pattern detail is inlined rather than split into reference files.

4 / 5

Total

16

/

20

Passed

Description

100%Weight 40%Scale 1-5

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 is specific, trigger-rich, and explicitly pairs a clear "what" with a concrete "when" clause, while carving out a distinct niche from the web HeroUI library. Third-person voice is used correctly throughout.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "creating Buttons, Cards, TextFields, Dialogs; installing heroui-native; configuring dark/light themes; or fetching component docs" — giving comprehensive coverage of what the skill does.

5 / 5

Completeness

Explicitly answers both what ("component library for React Native ... creating Buttons, Cards, TextFields, Dialogs; ... configuring dark/light themes") and when ("Use when building mobile UIs with HeroUI Native — ...") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive natural terms including synonyms and the package name: "HeroUI Native, heroui-native, React Native UI, Uniwind, mobile components", plus concrete component names a user would say.

5 / 5

Distinctiveness Conflict Risk

Clear niche — React Native mobile UI via Uniwind, distinct from web HeroUI — with the package name and platform making trigger collisions unlikely.

5 / 5

Total

20

/

20

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
heroui-inc/heroui
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.