CtrlK
BlogDocsLog inGet started
Tessl Logo

mobile-development

Mobile development patterns for React Native and Flutter including navigation, state management, and responsive design

60

Quality

68%

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

Quality

Content

80%

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 strong, actionable pattern catalog with lean, executable code examples and no concept-padding. Its main weakness is structure: it is a single inline monolith rather than an overview pointing to separate reference files, and it is a reference catalog rather than a sequenced workflow.

Suggestions

Split substantial standalone sections (e.g., Flutter widget patterns, platform-specific code) into referenced files and keep SKILL.md as a concise overview, to improve progressive disclosure.

If this skill is meant to guide a build/debug process, add a short sequenced workflow with explicit validation checkpoints (e.g., verify builds on both iOS and Android) rather than only a pattern catalog.

DimensionReasoningScore

Conciseness

The body is lean: complete code examples with minimal prose and no re-explanation of what React Native, Flutter, or libraries are, so every token earns its place.

3 / 3

Actionability

Provides fully executable, copy-paste-ready code across multiple languages with concrete knobs (windowSize, maxToRenderPerBatch, Platform.select, useWindowDimensions), plus an Anti-Patterns list and a Checklist.

3 / 3

Workflow Clarity

Content is well-organized into clear sections and includes a checklist, but it is a reference catalog of patterns rather than a sequenced multi-step process with explicit validation checkpoints.

2 / 3

Progressive Disclosure

Sections are clearly labeled and there is no nested referencing, but all content is inline in a ~215-line SKILL.md with no external bundle files or signaled one-level-deep references.

2 / 3

Total

10

/

12

Passed

Description

57%

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 identifies a specific mobile-development niche and lists relevant sub-areas, but it lacks an explicit trigger clause and concrete action verbs, which caps specificity and completeness at 2. Trigger terms are present but could cover more natural variations like "iOS" and "Android".

Suggestions

Add an explicit 'Use when...' clause stating when Claude should invoke this skill (e.g., when building or debugging React Native or Flutter apps).

Replace pattern-area phrasing with concrete actions, e.g., 'Build, navigate, and style React Native and Flutter apps: stack/tab navigation, state management, and responsive layouts.'

Broaden trigger terms to include natural user phrasing such as 'iOS app', 'Android app', and 'cross-platform mobile app'.

DimensionReasoningScore

Specificity

Names the domain ("React Native and Flutter") and sub-areas ("navigation, state management, and responsive design"), but describes patterns/areas rather than concrete actions like build, configure, or wire up.

2 / 3

Completeness

Clearly states what the skill covers, but provides no "Use when..." trigger guidance, so per the rubric completeness is capped at 2.

2 / 3

Trigger Term Quality

Includes natural terms users would say ("React Native", "Flutter", "mobile development", "navigation", "responsive design"), but omits common variations like "iOS", "Android", "app", or "cross-platform".

2 / 3

Distinctiveness Conflict Risk

The mobile-specific React Native/Flutter framing is a clear niche with distinct triggers and is unlikely to fire for unrelated skills.

3 / 3

Total

9

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
rohitg00/awesome-claude-code-toolkit
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.