CtrlK
BlogDocsLog inGet started
Tessl Logo

expo-ui-swift-ui

expo-ui-swift-ui

40

Quality

39%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/expo-ui-swift-ui/SKILL.md

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

SKILL.md
Quality
Evals
Security

Quality

Content

71%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 well-organized and actionable, providing concrete commands, import paths, and a runnable example with sensible checkpoints like fetching docs and confirming before extending. Its main weakness is embedded version-pinned details that age the content.

DimensionReasoningScore

Conciseness

The body is mostly lean and assumes SwiftUI knowledge, but time-sensitive tokens ('SDK 55 only', version-pinned 'v55.0.0' doc URLs) are not isolated in a deprecated section, incurring the version-number penalty.

3 / 5

Actionability

It gives a concrete install command, exact import paths, doc-fetch URLs, and a complete copy-paste Host/VStack/RNHostView example, with only minor gaps such as not automating the doc-fetch step.

4 / 5

Workflow Clarity

The sequence (install -> native rebuild -> wrap in Host, fetch docs to confirm API, confirm with user before extending) is clear with most checkpoints present, though validation is implicit rather than enumerated.

4 / 5

Progressive Disclosure

This is a short (<50 line) single-file skill with no bundle files and clear Installation/Instructions sections; external doc references are one level deep and clearly signaled, satisfying the simple-skill exception.

5 / 5

Total

16

/

20

Passed

Description

7%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 frontmatter description is a placeholder that merely repeats the skill name, providing no capabilities, triggers, or usage guidance. It fails to convey what the skill does or when to invoke it.

Suggestions

Replace the placeholder description with a real one stating concrete capabilities, e.g. "Use SwiftUI Views and modifiers in Expo apps via @expo/ui/swift-ui. Use when the user wants SwiftUI components, modifiers, or Host/RNHostView bridging in an Expo (SDK 55) app."

Add an explicit 'Use when...' clause listing natural trigger terms such as 'SwiftUI in Expo', 'expo ui swift-ui', 'Host', and 'RNHostView'.

Keep the description in third person and concise, avoiding buzzwords, while covering both the 'what' (wrap SwiftUI trees in Host, use modifiers) and the 'when' (Expo apps needing SwiftUI APIs).

DimensionReasoningScore

Specificity

The description is the bare string "expo-ui-swift-ui" with no verb or concrete action — it names the package but describes no capabilities, matching the 'entirely vague; no concrete actions' anchor.

1 / 5

Completeness

It answers neither 'what does this do' nor 'when should Claude use it', and lacks any 'Use when...' trigger clause, matching the 'missing both what and when' anchor.

1 / 5

Trigger Term Quality

"expo-ui-swift-ui" is a technical package identifier rather than a phrase a user would naturally say; it offers no natural trigger keywords, fitting the 'only technical jargon' anchor.

1 / 5

Distinctiveness Conflict Risk

The package name is specific enough to avoid broad conflicts, but as a bare label with no trigger phrases it could still overlap with general Expo or SwiftUI skills, fitting the 'somewhat specific but could still overlap' anchor.

3 / 5

Total

6

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

description_field

'description' is very short (16 chars), consider making it more detailed

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
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.