expo-tailwind-setup

Set up Tailwind CSS v4 in Expo with react-native-css and NativeWind v5 for universal styling

4.54x

Quality

66%

Does it follow best practices?

Impact

100%

4.54x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/expo/skills/expo-tailwind-setup/SKILL.md

The canonical home for this skill is expo-tailwind-setup in administrakt0r/AI-Agents-Safe-Coding-Skills

Quality

Content

76%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 complete, executable code and a sensible installation sequence. Its weaknesses are missing build-validation checkpoints and a monolithic structure that inlines reference-grade material instead of splitting it into bundle files.

Suggestions

Add a verification step after configuration, e.g. 'Run `npx expo start` and confirm a styled component renders on iOS/Android/Web before proceeding.'

Move the full component wrappers and the Apple system colors CSS into files under references/ (e.g. references/tw-components.tsx, references/sf-colors.css) and link to them from the body so the main file stays an overview.

Trim the duplicated platform-specific @media blocks (global.css and 'Platform-Specific Styles' repeat the same ios/android rules) to reduce tokens.

Dimension	Reasoning	Score
Conciseness	Most sections are efficient and code-forward with minimal over-explanation of concepts Claude knows, though the inlined component wrappers and full CSS blocks are somewhat lengthy and could partly live in reference files.	4 / 5
Actionability	It provides fully executable, copy-paste-ready install commands, config files, and complete component wrappers covering the common cases with concrete file paths.	5 / 5
Workflow Clarity	The setup is laid out as a clear sequenced path (install -> resolutions -> Metro -> PostCSS -> global CSS -> wrappers -> usage) with a troubleshooting section, though it lacks explicit validation checkpoints for verifying the build works.	4 / 5
Progressive Disclosure	There is good section structure, but no bundle files exist and large reference-worthy blocks (full component wrapper source, Apple system color CSS) are inlined rather than split into separate files with one-level-deep navigation.	3 / 5
	Total	16 / 20 Passed

Description

56%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 about the target stack and niche, but it omits any explicit 'Use when' trigger guidance, which limits completeness. Trigger terms are good and conflict risk is low.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when setting up Tailwind CSS v4 styling in an Expo app or when migrating from NativeWind v4 / Tailwind v3.'

List 1-2 more concrete actions beyond 'set up', such as 'configure Metro and PostCSS, wrap components with useCssElement, and define custom theme variables'.

Dimension	Reasoning	Score
Specificity	It names the domain (Tailwind CSS v4 in Expo) and lists the concrete stack (react-native-css, NativeWind v5) for 'universal styling', but states only a single high-level action with no enumerated concrete operations.	3 / 5
Completeness	The 'what' is stated clearly (set up Tailwind v4 in Expo with the named stack), but there is no 'Use when...' clause or any explicit 'when' trigger, which caps completeness at 3 per the guidelines.	3 / 5
Trigger Term Quality	Natural terms like 'Tailwind CSS v4', 'Expo', 'NativeWind', and 'universal styling' match what a user would say, with solid coverage; minor synonyms or phrasings (e.g. 'React Native styling') are absent.	4 / 5
Distinctiveness Conflict Risk	The combination of Tailwind v4 + Expo + NativeWind v5 + react-native-css is a fairly distinct niche with minor overlap risk against generic CSS or React Native styling skills.	4 / 5
	Total	14 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: openai/plugins
Path: plugins/expo/skills/expo-tailwind-setup/SKILL.md
Commit: d416fd5

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.