mobile-design

Mobile-first design thinking and decision-making for iOS and Android apps. Touch interaction, performance patterns, platform conventions. Teaches principles, not fixed values. Use when building React Native, Flutter, or native mobile apps.

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/mobile-design/SKILL.md

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.

The body is a richly actionable mobile design overview with executable RN/Flutter examples, concrete heuristics, a strong checkpoint/checklist workflow, and well-signaled reference navigation. Its weaknesses are verbosity from a duplicated reference table and heavy decoration, a validation script not integrated as a workflow checkpoint, and — most importantly — reference files that are cited throughout but missing from the bundle.

Suggestions

Ship the 12 missing reference .md files (or remove their citations) so the progressive-disclosure structure actually resolves; dangling links are the most impactful defect here.

De-duplicate the reference-file table (it appears in both the 'Read Reference Files' section and the closing 'Reference Files' section) and trim emoji/urgency header decoration to recover token budget.

Wire 'python scripts/mobile_audit.py' into the workflow as an explicit validation checkpoint (e.g. a mandatory step in the pre-release checklist) to close the workflow-clarity validation gap.

Dimension	Reasoning	Score
Conciseness	Content is largely dense, scannable tables of mobile-specific guidance, but it includes padding that could be tightened: the reference-file table is duplicated verbatim (read-files section and closing 'Reference Files' section), headers are heavily decorated with emoji/urgency markers, and 'Why It's Wrong' columns re-explain basics Claude already knows (e.g. why ScrollView over-renders).	3 / 5
Actionability	Provides copy-paste-ready executable code (RN FlatList with keyExtractor/getItemLayout/useCallback, Flutter const constructors), concrete pixel values (44pt/48dp), and a runnable audit script ('python scripts/mobile_audit.py <project_path>'); minor gaps remain where several topics (navigation, typography, color, backend, testing, debugging) offer only references with no inline executable guidance.	4 / 5
Workflow Clarity	Clear multi-step sequence (read references -> ask before assuming -> complete checkpoint -> build -> run pre-dev/per-screen/release checklists) with an explicit checkpoint template, a feedback loop ('Can't fill the checkpoint? GO BACK AND READ THE SKILL FILES'), and checklists; the validation script is offered but not tightly wired into the workflow as an explicit checkpoint step, leaving a minor validation gap.	4 / 5
Progressive Disclosure	Structure and signaling are excellent — a concise overview with clearly-labeled, one-level-deep reference tables organized by universal vs platform-specific use — but 12 of the 13 referenced files (mobile-design-thinking.md, touch-psychology.md, mobile-performance.md, etc.) are absent from the bundle (only scripts/mobile_audit.py exists), so the disclosed depth content is unreachable and navigation is partially broken.	3 / 5
	Total	14 / 20 Passed

Description

70%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 is well-constructed with an explicit 'Use when' trigger, strong natural framework/platform keywords, and a clear mobile niche. Its main weakness is that the 'what' is expressed as abstract topics ('design thinking', 'principles') rather than concrete actions, which limits specificity and completeness from reaching the top band.

Suggestions

Replace abstract framing ('design thinking and decision-making', 'Teaches principles') with concrete verbs, e.g. 'Design touch interactions, optimize RN/Flutter performance, apply iOS HIG and Material conventions'.

Add a few more natural trigger synonyms users might say (e.g. 'mobile app UI', 'app design') to push trigger term coverage toward comprehensive.

Sharpen the 'what' so it reads as a list of concrete capabilities rather than topical areas, which would lift both specificity and completeness.

Dimension	Reasoning	Score
Specificity	Names the mobile domain plus three capability areas ('Touch interaction, performance patterns, platform conventions'), but the framing is topical and abstract ('design thinking and decision-making', 'Teaches principles') rather than concrete verbs, so it sits at the 'names domain and a few concrete actions, not comprehensive' level.	3 / 5
Completeness	Both 'what' (mobile-first design thinking, touch interaction, performance patterns, platform conventions) and an explicit 'when' ('Use when building React Native, Flutter, or native mobile apps') are present with concrete trigger phrases, but the 'what' is more topical than action-oriented so it is not a full 5.	4 / 5
Trigger Term Quality	Strong natural keywords users would actually say — 'iOS and Android apps', 'React Native, Flutter, or native mobile apps', 'touch interaction' — with good coverage; a few natural synonyms (e.g. 'mobile app design', 'app UI') are missing, stopping short of comprehensive.	4 / 5
Distinctiveness Conflict Risk	Clearly scoped to a mobile niche with framework-specific triggers (iOS/Android, RN/Flutter/native) that minimize conflict with non-mobile skills; only minor overlap risk remains with general UI/design skills, keeping it just below a 5.	4 / 5
	Total	15 / 20 Passed

Validation

81%

Warnings & errors only

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

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 24 missing	Warning

	Total	13 / 16 Passed

Repository: vudovn/ag-kit
Path: .agents/skills/mobile-design/SKILL.md
Commit: 211561c

Reviewed: 8 days ago

Table of Contents

Discovery Implementation Validation

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.