CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ui-mobile

Mobile UI patterns - React Native, iOS/Android, touch targets

49

Quality

62%

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

Quality

Content

53%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 a rich, highly actionable catalog of React Native UI patterns with concrete code throughout, but it suffers from significant duplication (touch targets and accessibility covered twice) and is a monolithic ~940-line file with no progressive disclosure into reference files, no workflow sequencing, and no validation checkpoints.

Suggestions

Split the body into one-level-deep reference files (e.g., references/component-patterns.md, references/animations.md, references/navigation.md) and keep SKILL.md as a concise overview with clearly signaled links.

Deduplicate the touch-target and accessibility sections — remove the repeated "Touch Targets" and "VoiceOver / TalkBack" sections or merge them with the mandatory-standards block.

Fix the executable gaps: define or import the missing pieces (CloseIcon, withRepeat/withTiming/withSequence imports in the skeleton loader) so code examples are copy-paste ready.

DimensionReasoningScore

Conciseness

The body is mostly efficient, dense reference code, but contains clear padding: touch-target sizing is fully duplicated ("MANDATORY: Mobile Accessibility Standards > 1. Touch Targets" and again "## Touch Targets"), accessibility-label markup is duplicated (section 4 and "VoiceOver / TalkBack"), and the Platform.select shadow example appears twice. Not a 2 because the code itself is tight and free of conceptual over-explanation; not a 4 because the redundancy is substantial across a ~940-line body.

3 / 5

Actionability

Most guidance is concrete, executable React Native code (button styles, safe-area insets, skeleton loader, tab bar sizing) with only minor gaps: undefined components ("CloseIcon"), missing imports for "withRepeat/withTiming/withSequence" in the skeleton loader, and a literal "source={...}" placeholder — matching anchor 4 rather than 5's fully copy-paste-ready coverage.

4 / 5

Workflow Clarity

The body is a pattern catalog organized by topic rather than a sequenced workflow — there are no ordered steps and no validation checkpoints, though the "Premium Feel Checklist" provides a partial verification list. This fits anchor 3 (sequence/checkpoints missing or implicit); it avoids the destructive-operation cap issue since the skill modifies no data.

3 / 5

Progressive Disclosure

This is a ~940-line monolithic SKILL.md with no bundle files (no references/, scripts/, or assets/ directories exist) and no external references at all; component patterns, navigation, animation, and loading-state reference material that clearly belongs in separate files is fully inlined — matching anchor 2 ('content that clearly belongs in separate files is inlined'), not 1 because section headers keep it navigable.

2 / 5

Total

12

/

20

Passed

Description

56%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 correctly identifies a distinctive niche (React Native mobile UI) with natural trigger keywords, but it is a topic list rather than a statement of capabilities — it names no concrete actions and omits any 'use when' trigger guidance, both of which limit its usefulness for skill selection.

Suggestions

Rewrite the description as concrete actions in third person, e.g., "Provides mobile UI design patterns for React Native: touch targets, safe areas, platform-specific styling, and accessibility labels."

Add an explicit trigger clause to the description: "Use when building or styling React Native components, mobile app screens, or iOS/Android UI."

Include natural synonym trigger terms such as "mobile app", "app design", and relevant file patterns to broaden matching beyond "React Native".

DimensionReasoningScore

Specificity

The description "Mobile UI patterns - React Native, iOS/Android, touch targets" names the domain and one concrete concern ("touch targets") but lists no actions whatsoever — it is a topic list, matching anchor 2 ('names the domain but actions are minimal or generic') rather than anchor 3, which requires 1-2 concrete actions.

2 / 5

Completeness

The description conveys a recognizable 'what' (mobile UI design patterns for React Native/iOS/Android) but contains no 'Use when...' clause or equivalent explicit trigger guidance, capping completeness at 3 per the judging guidelines; it is not a 4 because the 'when' is entirely absent rather than merely imprecise.

3 / 5

Trigger Term Quality

"Mobile UI", "React Native", "iOS/Android", and "touch targets" are phrases users would naturally say, giving good keyword coverage; a few natural terms are missing (e.g., "mobile app", "app design", "Flutter"), so it falls short of the comprehensive-synonyms anchor 5.

4 / 5

Distinctiveness Conflict Risk

"React Native, iOS/Android, touch targets" carves out a clear mobile-native niche that is mostly distinct from web UI or desktop skills, with only minor overlap risk against general front-end/UI skills — matching anchor 4 rather than 5, which demands fully distinct triggers with explicit 'use when' phrasing.

4 / 5

Total

13

/

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.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (955 lines); consider splitting into references/ and linking

Warning

frontmatter_unknown_keys

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

Warning

Total

14

/

16

Passed

Repository

alinaqi/maggy

Path

skills/ui-mobile/SKILL.md

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.