oma-mobile

Implement Flutter, React Native, or native Swift apps. Use for mobile screens, widgets, platform integrations, and application data flows.

Quality

80%

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

Quality

Content

73%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 well-structured with a clear sequenced workflow, explicit verification, and concrete actionable guardrails. Its main weaknesses are abstract scaffolding padding (Scheduling/Scenes, SSL primitives) and a large inlined guardrail block that could be externalized to references.

Suggestions

Trim the abstract 'Scheduling/Scenes' framing and the 'SSL primitive' action table, which restate concepts Claude already knows; keep only the actionable workflow steps.

Move the lengthy 16-item guardrail block (especially the Swift/Flutter/React Native variant-specific rules) into the corresponding variant snippet/reference files, leaving a concise summary in SKILL.md.

Ensure the referenced files (resources/execution-protocol.md, variants/*/snippets.md, ../_shared/core/*) are actually bundled so the one-level-deep references resolve.

Dimension	Reasoning	Score
Conciseness	The guardrails are dense and efficient, but the abstract 'Scheduling/Scenes' framing and the 'SSL primitive' action table are conceptual scaffolding Claude does not need and could be tightened.	3 / 5
Actionability	Concrete `rg` commands and specific guardrails (Drift stale-while-revalidate, TanStack staleTime/gcTime, swift-openapi-generator, swipeBackDestination) give executable guidance, though most actual code lives in referenced snippet files rather than inline.	4 / 5
Workflow Clarity	A clear Entry -> PREPARE/ACQUIRE/ACT/VERIFY/FINALIZE -> Exit sequence includes an explicit VERIFY checkpoint and a Failure and recovery section with fix-before-handoff feedback loops.	5 / 5
Progressive Disclosure	The body is a well-signaled overview with one-level-deep references organized by variant, but the 16-rule guardrail block is bulk inlined in SKILL.md and the referenced files (resources/, variants/) are not present in the bundle.	4 / 5
	Total	16 / 20 Passed

Description

87%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 concise, concrete, and explicitly answers both what the skill does and when to use it, with natural trigger terms and a clear mobile niche. Minor gaps in coverage of testing and platform variants (iOS/Android) keep specificity and trigger quality just below maximum.

Dimension	Reasoning	Score
Specificity	Lists several concrete action areas ('mobile screens, widgets, platform integrations, and application data flows') but omits testing/state-management, so it is not fully comprehensive.	4 / 5
Completeness	A clear 'what' ('Implement Flutter, React Native, or native Swift apps...') is paired with an explicit 'Use for...' 'when' clause naming concrete triggers.	5 / 5
Trigger Term Quality	'Flutter, React Native, native Swift', 'mobile screens, widgets, platform integrations' are natural user phrases, but common variants like iOS, Android, and Dart are absent.	4 / 5
Distinctiveness Conflict Risk	Mobile-specific niche with Flutter/RN/Swift triggers is clearly distinct from web-frontend and backend skills, with minimal overlap risk.	5 / 5
	Total	18 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: first-fluke/oh-my-agent
Path: .agents/skills/oma-mobile/SKILL.md
Commit: 580da66

Reviewed: 4 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.