expo-ui-swift-ui

`@expo/ui/swift-ui` package lets you use SwiftUI Views and modifiers in your app.

Quality

67%

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/expo/skills/expo-ui-swift-ui/SKILL.md

Quality

Content

85%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 skill body is tight, well-structured, and highly actionable, with executable examples and clear confirm-before-use checkpoints. The only weakness is the hardcoded SDK/version pinning that bakes time-sensitive information into the main flow.

Dimension	Reasoning	Score
Conciseness	The body is largely lean and free of concepts Claude already knows, but it pins time-sensitive version info ('SDK 55 only', v55.0.0 in doc URLs) outside a deprecated/old-patterns section, which the rubric penalizes.	2 / 3
Actionability	Provides executable install commands, exact import paths, doc URLs to fetch, and a complete copy-paste-ready JSX example for wrapping components in Host/RNHostView.	3 / 3
Workflow Clarity	As a simple single-purpose skill it is unambiguous (install -> rebuild -> import -> use) and includes explicit checkpoints ('fetch its docs to confirm the API', 'Confirm with the user before extending').	3 / 3
Progressive Disclosure	Under 50 lines with well-organized Installation/Instructions sections and clearly signaled one-level-deep external references (doc URLs), with no bundle files needed.	3 / 3
	Total	11 / 12 Passed

Description

50%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 identifies a clear technical domain and one action but reads more as a tagline than a trigger-rich skill description. It lacks any 'Use when' guidance and concrete action list, leaving every dimension at the midpoint.

Suggestions

Add an explicit 'Use when...' clause naming the situations that should trigger this skill (e.g., when the user wants SwiftUI components/modifiers in an Expo/React Native app).

Replace the generic 'lets you use' with concrete actions, e.g. 'render SwiftUI Views and apply SwiftUI modifiers inside React Native via @expo/ui'.

Include natural trigger variations users might say (e.g., 'SwiftUI', 'expo-ui', 'SwiftUI components', 'SwiftUI modifiers') to broaden keyword coverage.

Dimension	Reasoning	Score
Specificity	Names the concrete domain ('SwiftUI Views and modifiers') but the only action is the generic 'lets you use', so it does not list multiple specific concrete actions.	2 / 3
Completeness	It states what the package does ('lets you use SwiftUI Views and modifiers') but has no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 2 per the rubric.	2 / 3
Trigger Term Quality	Contains relevant keywords a user would say ('SwiftUI', '@expo/ui/swift-ui', 'modifiers') but offers no common variations or phrasings beyond the technical package name.	2 / 3
Distinctiveness Conflict Risk	The SwiftUI/Expo UI niche is fairly specific, but without explicit 'Use when' triggers it could still overlap with sibling Expo UI skills, so it is not clearly distinct.	2 / 3
	Total	8 / 12 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: openai/plugins
Path: plugins/expo/skills/expo-ui-swift-ui/SKILL.md
Commit: 11c74d6

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