expo-tailwind-setup

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

4.54x

Quality

68%

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 expo/skills

Quality

Content

65%Weight 40%Scale 1-3

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 config and code, but it is monolithic and somewhat verbose, with no progressive disclosure into reference files and no explicit verification checkpoint in the setup workflow.

Suggestions

Move the large component-wrapper implementations (index.tsx, image.tsx, animated.tsx) and the Apple system-colors reference into files under references/ and link to them from SKILL.md.

Add an explicit verification step after configuration (e.g., start the dev server and confirm a className-based style renders) to create a real validation checkpoint.

Remove the duplicated @media ios/android blocks in the Platform-Specific Styles section since they already appear in the Global CSS example.

Dimension	Reasoning	Score
Conciseness	Most content is concrete config and executable code that earns its place, but the ~480-line body includes redundancy (e.g., the Platform-Specific Styles section repeats the @media ios/android blocks already shown in Global CSS) and large inline component-wrapper code that could be tightened.	2 / 3
Actionability	It provides pinned install commands, complete copy-paste-ready config files (metro, postcss, global.css), and full component implementations, matching the fully-executable anchor.	3 / 3
Workflow Clarity	The setup is sequenced (Installation → Configuration → Components → Usage) but lacks an explicit verification checkpoint (e.g., "run the app and confirm styles apply"); the Troubleshooting feedback loops exist only after the fact rather than as in-flow checkpoints.	2 / 3
Progressive Disclosure	No bundle files exist (references/scripts/assets are empty) and the entire skill is a single ~480-line file; the substantial component-wrapper code and Apple-system-colors reference would benefit from being split into separate, clearly-signaled reference files.	2 / 3
	Total	9 / 12 Passed

Description

72%Weight 40%Scale 1-3

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 and distinct for a well-defined niche, with natural trigger terms, but it omits an explicit "Use when..." trigger clause that the rubric requires for full completeness.

Suggestions

Add an explicit trigger clause, e.g. "Use when setting up or migrating to Tailwind CSS v4 / NativeWind v5 in an Expo project."

Optionally enumerate concrete actions (configure Metro, add PostCSS, create CSS-wrapped components) to lift specificity to level 3.

Dimension	Reasoning	Score
Specificity	"Set up Tailwind CSS v4 in Expo" names the domain and one concrete action (setup) with a specific stack, but does not list multiple distinct actions, so it is not the comprehensive level-3 anchor.	2 / 3
Completeness	It answers "what" (set up Tailwind v4 in Expo with the named stack) but lacks any "Use when..." clause or equivalent explicit trigger guidance, which the rubric caps at 2.	2 / 3
Trigger Term Quality	Phrases like "Tailwind CSS v4", "Expo", "NativeWind v5", and "universal styling" are exactly the natural terms a user would say when needing this skill, with good coverage of the niche vocabulary.	3 / 3
Distinctiveness Conflict Risk	The combination of Expo + Tailwind v4 + react-native-css + NativeWind v5 is a clear, narrow niche unlikely to trigger for unrelated skills.	3 / 3
	Total	10 / 12 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: 11c74d6

Reviewed: 17 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.