CtrlK
BlogDocsLog inGet started
Tessl Logo

building-native-ui

Complete guide for building beautiful apps with Expo Router. Covers fundamentals, styling, components, navigation, animations, patterns, and native tabs.

48

Quality

52%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./config/claude/skills/building-native-ui/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%

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

This is a strong skill file that serves as an effective overview for building Expo Router apps. Its greatest strengths are the highly actionable code examples (context menus, sheets, tab layouts) and excellent progressive disclosure via well-organized reference files. The main weaknesses are some verbosity in the Expo Go section and a lack of explicit validation/feedback loops in multi-step workflows.

Suggestions

Condense the 'Running the App' section — the 'When Expo Go Works' list of supported features is unnecessary context for Claude and could be reduced to a single sentence.

Add a validation step or feedback loop to the route structure workflow, e.g., 'Run npx expo start to verify routes resolve correctly before adding more screens.'

DimensionReasoningScore

Conciseness

Generally efficient but includes some unnecessary explanations (e.g., the lengthy 'When Expo Go Works' section listing things Claude would know, and the detailed explanation of when custom builds are required). The Expo Go section could be condensed significantly. However, most other sections are lean and well-structured.

2 / 3

Actionability

Provides concrete, executable code examples throughout — context menus, link previews, sheet configuration, stack setup, tab layout with NativeTabs, shadow styling, and complete route structure examples. Library preferences are specific with clear old→new mappings. Code is copy-paste ready.

3 / 3

Workflow Clarity

The 'Running the App' section has a clear sequence (try Expo Go first → check features → custom build only if needed), but lacks validation checkpoints. The common route structure section shows file organization but doesn't provide a step-by-step workflow for creating a new app. No explicit feedback loops for error recovery in any workflow.

2 / 3

Progressive Disclosure

Excellent progressive disclosure with a clear references section at the top pointing to 11 specific reference files with descriptive summaries. The main SKILL.md serves as an overview with essential information inline and detailed topics delegated to one-level-deep reference files. Navigation is well-signaled and organized.

3 / 3

Total

10

/

12

Passed

Description

32%

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 its domain (Expo Router) but reads more like a table of contents than a skill description. It lacks concrete actions, explicit trigger conditions, and sufficient natural keywords to reliably distinguish it from other mobile/web development skills. Adding a 'Use when...' clause and replacing category labels with specific capabilities would significantly improve it.

Suggestions

Add an explicit 'Use when...' clause with trigger terms like 'Expo Router', 'React Native navigation', 'mobile app routing', 'tab navigation', 'stack navigator', or 'file-based routing'.

Replace vague category labels ('fundamentals', 'patterns') with specific concrete actions such as 'configure file-based routing', 'implement animated screen transitions', 'set up bottom tab navigation with native styling'.

Include related natural keywords users might say, such as 'React Native', 'mobile app', 'deep linking', 'screen navigation', and 'app.json' to improve trigger term coverage.

DimensionReasoningScore

Specificity

It names the domain (Expo Router apps) and lists several topic areas (styling, components, navigation, animations, patterns, native tabs), but these are categories rather than concrete actions. It doesn't describe specific actions like 'configure tab navigation', 'implement animated transitions', or 'set up file-based routing'.

2 / 3

Completeness

It describes what the skill covers at a high level but completely lacks any 'Use when...' clause or explicit trigger guidance. Per the rubric, a missing 'Use when...' clause should cap completeness at 2, and since the 'what' is also somewhat vague (listing topic areas rather than concrete capabilities), this falls to 1.

1 / 3

Trigger Term Quality

Includes some relevant keywords like 'Expo Router', 'navigation', 'animations', 'native tabs', and 'styling' that users might mention. However, it's missing common variations and related terms like 'React Native', 'mobile app', 'screen transitions', 'stack navigation', 'deep linking', or file extensions.

2 / 3

Distinctiveness Conflict Risk

The mention of 'Expo Router' specifically provides some distinctiveness, but terms like 'styling', 'components', 'animations', and 'patterns' are very broad and could overlap with general React Native skills, web development skills, or UI/UX skills.

2 / 3

Total

7

/

12

Passed

Validation

90%

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

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

10

/

11

Passed

Repository
freekmurze/dotfiles
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.