Name: expo-tailwind-setup
Rating: 54.400000000000006 (1 reviews)
Author: administrakt0r

Blog Docs Log in Get started

expo-tailwind-setup

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

Quality

61%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/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

65%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 content is highly actionable with complete, copy-paste-ready config and component code, but it inlines a lot of material that belongs in reference files and lacks explicit validation checkpoints in the setup workflow.

Suggestions

Add an explicit verification step after configuration (e.g., run the app and confirm a Tailwind class renders) with a fix-and-retry loop, ideally folding in the Troubleshooting items.

Move the large optional blocks (CSS component wrappers, Apple system colors, custom theme variables) into reference files under references/ and link to them from SKILL.md to improve progressive disclosure and conciseness.

Trim or mark the Apple system colors and custom theme variables sections as optional so the core setup path stays lean.

Dimension	Reasoning	Score
Conciseness	The core is efficient executable config with no concept over-explanation, but sizable optional sections (Apple system colors CSS, full custom theme variables) pad beyond minimal setup and could be trimmed or moved to a reference.	3 / 5
Actionability	Provides fully executable, copy-paste-ready material: a pinned install command, complete Metro/PostCSS/global.css configs, and complete TypeScript component wrapper files covering the common cases.	5 / 5
Workflow Clarity	Section order gives a clear sequence, but there is no explicit validation/verification checkpoint (e.g., 'run the app and confirm styles apply') and only a shallow Troubleshooting section with no real feedback loops for the fragile configuration setup.	3 / 5
Progressive Disclosure	Sections are well-organized with clear headers, but at ~480 lines with no bundle files, large inlined content (full component wrappers, Apple colors) that would naturally live in separate reference files is kept inline and there are no one-level-deep references.	3 / 5
	Total	14 / 20 Passed

Description

58%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 and distinct, naming concrete packages and a clear purpose, but it omits any explicit 'Use when...' trigger guidance. Adding a trigger clause would lift completeness and trigger-term quality.

Suggestions

Append an explicit 'Use when...' clause (e.g., 'Use when setting up Tailwind CSS styling in an Expo app, or when the user mentions NativeWind, react-native-css, or universal styling for iOS/Android/Web').

Add common natural synonyms and trigger phrases (e.g., 'React Native styling', 'cross-platform styles') to broaden trigger-term coverage.

Optionally enumerate a couple of concrete actions the skill performs (install, configure Metro/PostCSS, generate CSS component wrappers) to push specificity toward 5.

Dimension	Reasoning	Score
Specificity	Names the domain (Tailwind CSS v4 setup in Expo) and several concrete technologies (react-native-css, NativeWind v5), giving specific concrete detail beyond a single action, though 'set up' itself is one composite action rather than a list of distinct user-facing actions.	4 / 5
Completeness	Provides a clear 'what' (set up Tailwind v4 in Expo with named packages for universal styling) but no 'when' clause — there is no 'Use when...' guidance, which per the rubric caps completeness at 3.	3 / 5
Trigger Term Quality	Includes relevant natural keywords a user would say ('Tailwind CSS', 'Expo', 'NativeWind', 'universal styling') but misses common variations, synonyms, and lacks an explicit trigger phrase, leaving keyword coverage partial.	3 / 5
Distinctiveness Conflict Risk	The specific stack combination (Tailwind v4 + Expo + react-native-css + NativeWind v5) carves a distinct niche with only minor overlap risk against broader Tailwind-in-React-Native 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: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills/skills/expo-tailwind-setup/SKILL.md
Commit: 57c135b

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.