CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

mobile-ux-foundations

Aplica fundamentos de UX mobile, navegacao e estados. Trigger em: "thumb zone", "zona do polegar", "navegacao inferior", "bottom nav", "dark mode", "modo escuro", "tema escuro", "OLED", "skeleton", "spinner", "loading", "tempo de carregamento", "app parece lento", "passkey", "passwordless", "login sem senha", "webauthn", "biometria", "onboarding", "tutorial inicial", "pedir permissao", "permission priming", "haptic", "feedback tatil", "dynamic type", "escala de fonte", "texto ampliado", "momento aha", "ativacao do usuario", "product tour", "checklist de onboarding", "tela de boas-vindas".

Quality

72%

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

Quality

Content

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

A strong, opinionated decision-rule skill: nearly every rule carries a measured threshold, and the checklists, anti-patterns, and completion evidence make it easy to act on and verify. Its weaknesses are length — it re-explains fundamentals Claude already knows — and progressive disclosure: a 400-line monolith that invokes a contrast script missing from the bundle while deferring only one guide document.

Suggestions

Trim or move the background explanations Claude already knows (passkey cryptography, WCAG ratio basics, why linear easing looks wrong) and keep only the synthesized thresholds — this could cut a third of the body without losing actionability.

Ship scripts/check-contrast.mjs in the bundle (or remove the checklist invocation) so the 'Checkpoint de contraste' is actually executable, and verify docs/skill-guides/mobile-ux-foundations.md exists.

Move the full inline tables (haptic mapping, semantic color pairs, onboarding pattern matrix, anti-pattern list) into the referenced guide, keeping one-line summaries inline, so SKILL.md works as the overview the guide complements.

DimensionReasoningScore

Conciseness

The body is dense with earned specifics (75% polegar, 80-120px, 100ms/1s/10s, 4.5:1, 30 dias de warm handover), but at ~400 lines it also explains concepts Claude already knows — passkey public/private-key crypto, WCAG AA ratios, why 'linear' looks mechanical — plus narrative asides (Duolingo/Slack, 'e a ansiedade de quem espera'). This matches 'Mostly efficient but includes some unnecessary explanation or could be tightened'; not 4 because the known-concept explanations are recurring rather than isolated.

3 / 5

Actionability

Guidance is highly concrete and executable for an instruction-only skill: gesture thresholds (80-120px, 200-250px/s, 25 graus), haptic and easing mapping tables, a copy-paste CSS token block, a NIST do/don't password table, a numbered permission-priming sequence, and autocomplete/one-time-code specifics. Minor gaps keep it below 5: hedged instructions ('observe no dispositivo quando essa evidencia for necessaria') and the invoked 'node scripts/check-contrast.mjs' is absent from the bundle.

4 / 5

Workflow Clarity

A coherent implicit workflow runs from Quando Usar/Nao Usar through per-topic decision rules to a per-topic Checklist, a contrast checkpoint with an explicit script + caveats, Evidencia de Conclusao, and Handoff — most checkpoints are present. It is not 5 because there is no explicit sequencing across the five topic areas and no validate-fix-retry loop anywhere.

4 / 5

Progressive Disclosure

Sectioning is good and the one external reference is clearly signaled and scoped ('consultar docs/skill-guides/mobile-ux-foundations.md apenas quando necessario'), but the bundle ships no scripts/, references/, or assets/ — the checklist's 'node scripts/check-contrast.mjs' points at a file that does not exist as provided — and extensive threshold/pattern tables that the guide is meant to hold 'complete' versions of remain fully inline in a ~400-line file. Between anchors 3 and 4: structure present, but content that should be separate is inline and a reference is unverifiable.

3 / 5

Total

14

/

20

Passed

Description

72%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 pairs a vague one-line capability statement with an exceptionally strong, bilingual trigger list that clearly signals when to use the skill. The explicit 'Trigger em' clause satisfies the completeness requirement, but the generic 'Aplica fundamentos' verb leaves the skill's concrete capabilities undersold.

Suggestions

Replace 'Aplica fundamentos de UX mobile, navegacao e estados' with 2-3 concrete actions, e.g. 'Decide posicionamento de navegacao por zona do polegar, define tokens de tema escuro com contraste verificado, especifica fluxos de passkey e onboarding' — this would lift both specificity and completeness.

Add a short qualifier to broad triggers like 'dark mode' and 'onboarding' (e.g. 'dark mode (mobile)') to reduce overlap with the neighboring ui-ux-design and accessibility skills named in the body.

State the platform scope (iOS/Android/PWA) in the description so the 'what' matches the trigger list's specificity.

DimensionReasoningScore

Specificity

The 'what' is a single generic action — "Aplica fundamentos de UX mobile, navegacao e estados" — which names the domain but offers no concrete capability (no equivalent of 'extracts text' or 'fills forms'). It matches the anchor 'Names the domain but actions are minimal or generic'; it is not a 3 because navegacao/estados are topic areas, not concrete actions.

2 / 5

Completeness

Both parts are present: a 'what' ("Aplica fundamentos de UX mobile, navegacao e estados") and an explicit 'when' ("Trigger em: ..." with ~30 concrete trigger phrases). It exceeds anchor 4 (whose 'when' is weak) but falls short of anchor 5 because the 'what' is generic compared to the anchor's 'Extract text and tables... fill forms, merge documents'.

4 / 5

Trigger Term Quality

The trigger list is comprehensive with natural user phrasings and full synonyms in two languages: "thumb zone"/"zona do polegar", "dark mode"/"modo escuro"/"tema escuro", "passkey"/"passwordless"/"login sem senha", "app parece lento", "permission priming"/"pedir permissao". This matches the anchor 'Comprehensive coverage of natural terms including synonyms'.

5 / 5

Distinctiveness Conflict Risk

Distinctive triggers like "thumb zone", "permission priming", "dynamic type", and "skeleton" carve a clear niche, but broad terms such as "dark mode", "loading", and "onboarding" overlap with the closely related UI-design and accessibility skills this very body names as neighbors. Mostly distinct with minor overlap risk — anchor 4, not 5.

4 / 5

Total

15

/

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.

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

metadata_version

'metadata.version' is missing

Warning

referenced_paths_exist

Referenced path issues: 1 possibly missing (scripts/check-contrast.mjs)

Warning

Total

13

/

16

Passed

Repository

felvieira/claude-skills-fv

Path

skills/57-mobile-ux-foundations/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.