CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

64

Quality

77%

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

Quality

Content

65%

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

The body is highly actionable with executable code and concrete anti-pattern tables, but it is verbose and structurally redundant. Progressive disclosure is undermined by missing referenced files and a monolithic inline layout, and the workflow is reference-style rather than a tight validation loop.

Suggestions

Create the referenced .md files (or remove the dangling links) so the progressive-disclosure structure actually resolves; today only scripts/mobile_audit.py exists in the bundle.

De-duplicate the content: the reference-file table appears twice and the anti-pattern list is repeated in the release checklist — consolidate to one canonical location.

Trim re-explanations of concepts Claude already knows (Fitts' Law, thumb zone, FlatList internals) and replace the 'just run' audit note with an explicit validate→fix→re-audit feedback loop.

DimensionReasoningScore

Conciseness

The body contains valuable concrete guidance but is verbose: the reference-file table is duplicated (top and bottom), anti-patterns are re-listed inside the pre-release checklist, and concepts Claude already knows (Fitts' Law, thumb zone, what FlatList does) are re-explained. It is mostly efficient but could be tightened, matching the score-2 anchor.

2 / 3

Actionability

It provides fully executable RN and Flutter code (FlatList with keyExtractor/getItemLayout/removeClippedSubviews, const constructors, ValueListenableBuilder), a runnable audit command ('python scripts/mobile_audit.py <project_path>'), and concrete do/don't tables — copy-paste ready guidance.

3 / 3

Workflow Clarity

A checkpoint template and pre-development/per-screen/release checklists provide sequence, but the body reads as a reference compendium rather than a crisp validate→fix→retry workflow; the audit script is mentioned as 'just run' without an explicit feedback loop tying results back to fixes.

2 / 3

Progressive Disclosure

References are signaled and organized in tables, but the referenced .md files (touch-psychology.md, mobile-performance.md, etc.) do not exist in the bundle — only scripts/mobile_audit.py is present — and the ~390-line body keeps large amounts of inline content that should live in those separate files, matching the 'content that should be separate is inline' anchor.

2 / 3

Total

9

/

12

Passed

Description

90%

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 clearly communicates a mobile-first design niche with explicit use-when triggers and negative scope, making it highly complete and distinctive. It is slightly less specific on concrete actions, leaning on domain descriptions rather than enumerated capabilities.

DimensionReasoningScore

Specificity

Phrases like 'design thinking and decision-making', 'Touch interaction, performance patterns, platform conventions' name the domain and some action areas but describe capabilities abstractly rather than listing multiple concrete actions, matching the 'Names domain and some actions, but not comprehensive' anchor.

2 / 3

Completeness

It answers both what ('Mobile-first design thinking... Touch interaction, performance patterns, platform conventions') and when via an explicit 'Use when building React Native, Flutter, or native mobile apps' clause, plus negative scope 'NOT for web apps'.

3 / 3

Trigger Term Quality

It includes natural terms users would say — 'iOS and Android apps', 'React Native, Flutter, or native mobile apps', 'Touch interaction', 'platform conventions' — giving good coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

The mobile-first niche with platform/framework triggers and an explicit 'NOT for web apps' exclusion makes it clearly distinguishable and unlikely to trigger for the wrong skill.

3 / 3

Total

11

/

12

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.

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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