Mobile specialist for Flutter, React Native, and Swift native iOS development.
SkillScore68Maintained
Automatic
◆Frontend / UI pack
Last verified 8/17/2026
What it changes
Passed 13 of 19 test cases with the skill, and 10 of 19 without it.
Without skill55%
With skill68%
Checks it passed that the model alone missed
Uses Riverpod for state management.
Declines the web frontend request as outside mobile scope.
Caches decoded Swift data models instead of raw HTTPBody bytes.
3 fixed12 passed either way7 still failing0 broke
Pass-rate lift
+14 pp
Tokens
+61%
Agent turns
0%
Response time
+2%
Model gemini-3.6-flashMeasured 8/17/2026v315 of 22 cases passed with skill · 19 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 3 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 3
Prompt
We need to set up a web-based administrative dashboard using React, Tailwind CSS, and Vite running in desktop browsers. Please build the root layout, sidebar navigation, and routing setup for this web app.
What was checked, without and with the skill
Checked
Without skill
With skill
Declines the web frontend request as outside mobile scope.
Missed
Passed
case-20 · gemini-3.6-flash · 8/17/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md156 linessingle file
Mobile Agent - Cross-Platform Mobile Specialist
Scheduling
Goal
Build, modify, and verify cross-platform mobile application features with clean architecture, platform-appropriate UI, state management, performance, and E2E coverage.
Intent signature
User asks for mobile app, Flutter, Dart, React Native, iOS, Android, Riverpod, widgets, camera, GPS, push notifications, or offline-first work.
User needs native or cross-platform mobile behavior rather than web frontend work.
When to use
Building native mobile applications (iOS + Android)
Mobile-specific UI patterns
Platform features (camera, GPS, push notifications)
Offline-first architecture
When NOT to use
Web frontend -> use Frontend Agent
Backend APIs -> use Backend Agent
Expected inputs
Target screen, widget, feature, platform capability, or mobile flow
Existing app architecture, state management pattern, API contract, and platform constraints
Test expectations for unit, widget, integration, or Maestro E2E coverage
Expected outputs
Mobile code changes in domain, data, presentation, platform, or test files
UI aligned with Material Design 3 and iOS HIG as applicable
Verification results from mobile checks and critical-flow tests
Dependencies
Flutter/Dart or React Native toolchain as detected from the project
Riverpod/Bloc, Dio, platform SDKs, and Maestro where applicable
resources/execution-protocol.md, examples, snippets, checklist, and screen template
Control-flow features
Branches by platform, state management pattern, offline requirement, native permission, and test level
Reads and writes mobile codebase files
May call build, test, simulator, emulator, or E2E commands