CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

oma-mobile

Implement Flutter, React Native, native Swift, or native Kotlin Android 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
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/oma-mobile/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%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 an unusually well-structured orchestration skill: a clear sequenced workflow with validation checkpoints and error-recovery loops, concrete stack-detection and guardrail guidance, and efficient use of tokens. The main defect is that its extensive, clearly-labeled reference system points at files absent from the evaluated bundle, breaking progressive disclosure in practice.

Suggestions

Ship the referenced bundle files (resources/execution-protocol.md, resources/checklist.md, resources/error-playbook.md, variants/*/tech-stack.md, variants/*/snippets.md, variants/stack.schema.json) alongside SKILL.md, or inline the minimal content needed when they are unavailable.

Move the shared-core and cross-skill dependencies (../_shared/core/*, ../oma-observability/SKILL.md §Integrations) into the bundle or summarize their key rules inline so navigation stays one level deep.

Include one or two example verification commands (e.g. a representative `verify:` block entry) so step 5 is actionable even before the stack reference is loaded.

DimensionReasoningScore

Conciseness

The body is dense and prescriptive — stack detection heuristics ("Package.swift (Swift iOS)", "pubspec.yaml (Flutter)"), guardrail rulings, and exit criteria with almost no explanation of concepts Claude already knows. Not 5 because guardrails 8–20 carry explanatory asides (e.g. the Swift 6 deinit/isolated-deinit rationale in item 13, "Ktor is an engine-agnostic layer, not an OkHttp replacement" in item 18) that could be tightened; not 3 because nearly every token is a non-obvious, project-specific ruling rather than padding.

4 / 5

Actionability

Concrete, specific guidance throughout: exact detection files per platform, named tools and commands ("/stack-set", "oma verify agent mobile", "stack/stack.yaml"), per-platform state/transport/caching patterns, and pointer anchors into variant snippets ("see variants/swift-ios/snippets.md §10"). Not 5 because there is no copy-paste-ready code or example verification command — the actual commands live in external files and "the project's mobile verification commands" is left abstract; not 3 because the guidance is consistently concrete and executable in intent for an instruction-only skill.

4 / 5

Workflow Clarity

A 6-step canonical workflow with explicit ordering, a prioritized stack-detection procedure, a dedicated failure-and-recovery section with feedback loops ("If a check that ran fails, fix it before handoff or report the failing check"), explicit exit and partial-success criteria, and a checklist checkpoint before handoff (step 6). This matches anchor 5's clear sequence + explicit validation + error-recovery feedback + checklist pattern better than anchor 4, which allows minor validation gaps that are not present here.

5 / 5

Progressive Disclosure

The References section is well organized with one-level-deep, purpose-annotated pointers, but the actual bundle contains only SKILL.md — none of the referenced files (resources/execution-protocol.md, resources/checklist.md, variants/*/tech-stack.md and snippets.md, ../_shared/core/*, ../oma-observability/SKILL.md) exist in the bundle, so navigation dead-ends and the cross-skill §Integrations reference adds another dependency level. Not 4 because the guideline says to score against the actual bundle structure, where the references do not resolve; not 2 because SKILL.md itself is clearly sectioned and the references are explicitly signaled rather than buried or inlined.

3 / 5

Total

16

/

20

Passed

Description

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

A strong description that clearly answers both what and when with good natural trigger terms and a distinct mobile niche. Its main weakness is specificity: a single generic verb ("Implement") with scope categories rather than a set of concrete, differentiated actions.

Suggestions

Replace the generic verb with several distinct concrete actions, e.g. "Implement and modify Flutter, React Native, Swift, or Kotlin Android apps: build screens and widgets, wire up camera/GPS/push platform integrations, and manage application data flows."

Add missing natural trigger terms users say, such as "iOS", "mobile app", or "Dart", to the 'Use for' clause.

DimensionReasoningScore

Specificity

"Implement Flutter, React Native, native Swift, or native Kotlin Android apps" names the domain clearly, but the single generic verb "Implement" plus scope categories ("mobile screens, widgets, platform integrations, and application data flows") stops short of several distinct concrete actions. It sits between anchor 3 (domain + limited concrete actions) and anchor 4 — not 4 because no distinct concrete actions like build, test, or fix are enumerated; not 2 because the platforms and work areas are specifically named.

3 / 5

Completeness

Both parts are present: what ("Implement Flutter, React Native, native Swift, or native Kotlin Android apps") and an explicit when ("Use for mobile screens, widgets, platform integrations, and application data flows"). Not 5 because the 'when' clause lists work categories rather than concrete user trigger phrases ("when the user mentions..."); not 3 because the 'when' is explicitly stated via "Use for", not merely implied.

4 / 5

Trigger Term Quality

"Flutter, React Native, native Swift, or native Kotlin Android" plus "mobile screens, widgets, platform integrations" gives good natural keyword coverage users would actually say. Not 5 because common variations like "iOS", "mobile app", "Dart", or "Jetpack Compose" are missing; not 3 because the platform names themselves are strong, natural trigger terms.

4 / 5

Distinctiveness Conflict Risk

"Implement Flutter, React Native, native Swift, or native Kotlin Android apps" carves a clear mobile-native niche with four precisely named platform stacks, and "mobile screens, widgets, platform integrations" are unambiguously mobile triggers. Minimal conflict risk with web, backend, or document skills — fits the anchor-5 example's clear-niche pattern better than anchor 4's minor-overlap profile.

5 / 5

Total

16

/

20

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.

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

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.