CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

common-mobile-ux-core

Enforce universal mobile UX principles for touch-first interfaces including touch targets, safe areas, and mobile-specific interaction patterns. Use when building mobile screens, handling touch interactions, or validating safe area compliance.

Quality

86%

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

An exceptionally lean, well-structured review checklist with concrete thresholds and platform-specific API names. The two minor gaps are the absence of failure-handling guidance in the workflow and slightly underspecified later steps (platform conventions) alongside fragment-level code examples.

DimensionReasoningScore

Conciseness

Telegraphic, dense bullets with zero padding ("Min 44x44pt (iOS) / 48x48dp (Android). Add padding if needed.") — nothing explains concepts Claude already knows and every token earns its place. Not 4 because there are no over-explanation instances left to trim.

5 / 5

Actionability

Concrete numeric thresholds, API names (`SafeArea`, `WindowInsets`, `InputType`), and a correct/avoid code pair make the guidance mostly executable. Not 5 because steps like "Verify platform conventions separately" lack specifics and the code example is a one-line fragment rather than a complete executable snippet.

4 / 5

Workflow Clarity

The Review Workflow gives a clear four-step sequence with concrete pass criteria ("Test the smallest interactive element against 44pt iOS / 48dp Android") and a completion gate ("before calling the screen complete"). Not 5 because there is no error-recovery guidance for what to do when a check fails; not 3 because checkpoints are explicit rather than implicit.

4 / 5

Progressive Disclosure

The skill is under 50 lines with no bundle files and no need for external references, and its sections (Guidelines, Code Examples, Review Workflow, Anti-Patterns, Related Topics) are cleanly organized, so the simple-skill guideline applies. Not 4 because nothing here belongs in a separate file and navigation is trivial.

5 / 5

Total

18

/

20

Passed

Description

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

A strong third-person description with an explicit and specific Use-when clause covering the mobile UX niche. Its main weakness is trigger coverage that stops short of platform synonyms (iOS, Android, Flutter) and concrete capability areas like typography and keyboards that the body actually covers.

DimensionReasoningScore

Specificity

Names the domain and enumerates several concrete areas ("touch targets, safe areas, and mobile-specific interaction patterns"), matching the anchor for several specific actions with minor gaps. Not 5 because the action verbs are limited (enforce/validating) and the description omits coverage areas present in the body such as typography and keyboard handling.

4 / 5

Completeness

Explicitly answers both what ("Enforce universal mobile UX principles for touch-first interfaces including...") and when, with a concrete "Use when building mobile screens, handling touch interactions, or validating safe area compliance" clause containing three trigger conditions. Not 4 because the when-clause is specific and multi-condition rather than merely serviceable.

5 / 5

Trigger Term Quality

Natural phrases users would say — "building mobile screens", "handling touch interactions", "validating safe area compliance" — give good keyword coverage. Not 5 because common synonyms and platform terms (iOS, Android, Flutter, .dart/.swift) are absent from the description itself.

4 / 5

Distinctiveness Conflict Risk

"Touch-first interfaces", "safe areas", and "mobile screens" carve a clear niche with distinct triggers; mostly distinct with only minor overlap risk against responsive-web or accessibility skills. Not 5 because those adjacent skills could plausibly compete for the same triggers.

4 / 5

Total

17

/

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

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository

HoangNguyen0403/agent-skills-standard

Path

.agents/skills/common/common-mobile-ux-core/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.