CtrlK
BlogDocsLog inGet started
Tessl Logo

expo-ui-swift-ui

expo-ui-swift-ui

44

Quality

46%

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

Quality

Content

82%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a well-crafted, concise skill that efficiently communicates how to use @expo/ui/swift-ui. It respects Claude's intelligence by leveraging existing SwiftUI knowledge and provides clear references for API confirmation. The main strength is its brevity and actionability; the main weakness is the reliance on external URLs for detailed API information without any local bundle support.

DimensionReasoningScore

Conciseness

Every line serves a purpose. No unnecessary explanations of what SwiftUI is or how React Native works. The skill assumes Claude's competence and provides only what's needed: installation, key rules, and references.

5 / 5

Actionability

Provides a concrete code example for RNHostView usage, specific installation commands, and clear URL patterns for fetching docs. Minor gap: no complete standalone example showing a full component usage beyond RNHostView, and the doc URLs are instructions to fetch rather than inline content.

4 / 5

Workflow Clarity

For a non-destructive, component-usage skill, the workflow is clear: install, rebuild, wrap in Host, use components, check docs for API confirmation, and extend if needed (with user confirmation). The sequence is logical and the confirmation step before extending is a good checkpoint. Minor gap: no explicit error handling or validation steps after building.

4 / 5

Progressive Disclosure

Good use of external doc references for component APIs, modifier APIs, and extending guides via URLs. The SKILL.md stays concise as an overview. Minor gap: no bundle files are provided, so the external references are all to remote URLs rather than local files, and there's no structured navigation section.

4 / 5

Total

17

/

20

Passed

Description

11%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.

This description is essentially a project name or identifier rather than a functional skill description. It provides no information about what the skill does, when it should be used, or what actions it performs. Claude would have almost no basis for selecting this skill appropriately from a list of available skills.

Suggestions

Rewrite the description as a complete sentence describing concrete actions, e.g., 'Creates and configures Expo modules with SwiftUI-based native UI components for React Native apps.'

Add an explicit 'Use when...' clause with trigger terms like 'Expo module', 'SwiftUI', 'native iOS component', 'React Native native view'.

Include natural keywords and synonyms users might say, such as 'Swift UI', 'expo-module', 'native iOS UI', 'custom native component'.

DimensionReasoningScore

Specificity

The description 'expo-ui-swift-ui' contains no concrete actions whatsoever. It appears to be a label or identifier rather than a description of capabilities.

1 / 5

Completeness

It answers neither 'what does this do' nor 'when should Claude use it'. There is no functional description and no usage guidance at all.

1 / 5

Trigger Term Quality

It contains some recognizable technology keywords ('expo', 'swift-ui') that a user might mention, but they are presented as a hyphenated slug rather than natural language, and there are no action-oriented trigger terms.

2 / 5

Distinctiveness Conflict Risk

While 'expo' and 'SwiftUI' together narrow the domain somewhat, the lack of any described actions or scope means it could overlap with any skill related to Expo, SwiftUI, or mobile UI development.

2 / 5

Total

6

/

20

Passed

Validation

81%

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

Validation9 / 11 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

9

/

11

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.