Developing Mobile Apps
telagod/code-abyss
Mobile development knowledge reference covering iOS (SwiftUI), Android (Jetpack Compose), React Native, and Flutter.
Implement Flutter, React Native, or native Swift apps. An agent skill from first-fluke/oh-my-agent.
Install Oma Mobile
$ npx skills add first-fluke/oh-my-agent --skill oma-mobile -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install first-fluke/oh-my-agent oma-mobile --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/first-fluke/oh-my-agent.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/oma-mobile .claude/skills/oma-mobile && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "oma-mobile" agent skill from https://github.com/first-fluke/oh-my-agent/tree/main/skills/oma-mobile into .claude/skills/oma-mobile/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "oma-mobile", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/first-fluke/oh-my-agent/tree/main/skills/oma-mobileType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add first-fluke/oh-my-agent --skill oma-mobile -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install first-fluke/oh-my-agent oma-mobile --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/first-fluke/oh-my-agent.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/oma-mobile .agents/skills/oma-mobile && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "oma-mobile" agent skill from https://github.com/first-fluke/oh-my-agent/tree/main/skills/oma-mobile into .agents/skills/oma-mobile/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "oma-mobile", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add first-fluke/oh-my-agent --skill oma-mobile -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install first-fluke/oh-my-agent oma-mobile --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/first-fluke/oh-my-agent.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/oma-mobile .cursor/skills/oma-mobile && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "oma-mobile" agent skill from https://github.com/first-fluke/oh-my-agent/tree/main/skills/oma-mobile into .cursor/skills/oma-mobile/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "oma-mobile", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/first-fluke/oh-my-agent.git --path skills/oma-mobile--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add first-fluke/oh-my-agent --skill oma-mobile -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install first-fluke/oh-my-agent oma-mobile --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/first-fluke/oh-my-agent.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/oma-mobile .gemini/skills/oma-mobile && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "oma-mobile" agent skill from https://github.com/first-fluke/oh-my-agent/tree/main/skills/oma-mobile into .gemini/skills/oma-mobile/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "oma-mobile", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install first-fluke/oh-my-agent oma-mobileInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add first-fluke/oh-my-agent --skill oma-mobile -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/first-fluke/oh-my-agent.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/oma-mobile .github/skills/oma-mobile && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "oma-mobile" agent skill from https://github.com/first-fluke/oh-my-agent/tree/main/skills/oma-mobile into .github/skills/oma-mobile/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "oma-mobile", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add first-fluke/oh-my-agent --skill oma-mobile -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install first-fluke/oh-my-agent oma-mobile --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/first-fluke/oh-my-agent.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/oma-mobile .opencode/skills/oma-mobile && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "oma-mobile" agent skill from https://github.com/first-fluke/oh-my-agent/tree/main/skills/oma-mobile into .opencode/skills/oma-mobile/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "oma-mobile", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
oma-mobile- GitHub stars
- 1.3k
- Token cost
- ~2.4k tokens
- SKILL.md length
- 1,092 words
- Files
- 23
- Skills in repo
- 57
- Repo updated
- First seen
- Licence
- MIT
At a glance
Implement Flutter, React Native, or native Swift apps. An agent skill from first-fluke/oh-my-agent.
- Works in 3 steps: Identify target platform(s),… → Inspect existing mobile patterns and… → Determine test level and verification…
- Platform integrations
- SKILL.md covers Scheduling, Structural Flow, Logical Operations and References
- Runs Dart, Swift and TypeScript scripts from its folder
What it does
Oma Mobile is an agent skill from first-fluke/oh-my-agent. Implement Flutter, React Native, or native Swift apps. Use for mobile screens, widgets, platform integrations, and application data flows.
Its SKILL.md is about 2.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 26 other files (for example `resources/checklist.md`, `resources/error-playbook.md` and `resources/execution-protocol.md`).
It sits in Mobile, covering Cross-platform mobile apps, Mobile UI design and iOS development. It works with Flutter, React Native and iOS. The repository describes itself as: Mechanical verification for AI coding agents — skills pack or full harness (stop-hook gates, artifact checks, independent judges). The licence is MIT.
When your agent uses it
- Platform integrations
- Application data flows
Example prompts
- “/oma-mobile”
Requirements
- Node.js
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Identify target platform(s), screen/feature, architecture layer, and state boundary.
- Inspect existing mobile patterns and dependencies.
- Determine test level and verification environment.
What it can do on your machine
Read from SKILL.md and the folder at commit b364119. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships script files (Dart, Swift and TypeScript, from the files we listed), which the agent can run.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Oma Mobile loads about 2.4k tokens when it runs. Until then it costs about 37 tokens; SKILL.md has 1,092 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from first-fluke/oh-my-agent at commit b364119, republished under its MIT licence (© first-fluke). 1,092 words, ~2,379 tokens.
Download SKILL.mdSave it as
.claude/skills/oma-mobile/SKILL.md (or your agent's skills folder). This skill also uses 22 other files; get the full folder from GitHub.- name
- oma-mobile
- description
- Implement Flutter, React Native, or native Swift apps. Use for mobile screens, widgets, platform integrations, and application data flows.
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
Structural Flow
Entry
- Identify target platform(s), screen/feature, architecture layer, and state boundary.
- Inspect existing mobile patterns and dependencies.
- Determine test level and verification environment.
Scenes
- PREPARE: Load app architecture, platform constraints, and acceptance criteria.
- ACQUIRE: Read existing widgets/screens, providers/blocs, API clients, and tests.
- ACT: Implement mobile UI, state, platform integration, offline handling, and tests.
- VERIFY: Run relevant unit/widget/integration/E2E checks.
- FINALIZE: Report behavior, platforms covered, and verification results.
Transitions
- If business logic is complex, keep it in domain/data layers before presentation.
- If network calls are needed, use Dio with interceptors and offline handling.
- If a critical user flow changes, add or update Maestro E2E coverage.
- If backend contracts are missing, coordinate with backend/API work.
Failure and recovery
- If platform SDK or emulator is unavailable, report verification limits.
- If a permission or native capability is missing, add explicit platform configuration or document blocker.
- If tests fail, fix before handoff or report the failing check.
Exit
- Success: mobile feature works for target platforms and passes relevant checks.
- Partial success: platform, simulator, dependency, or verification gaps are explicit.
Logical Operations
Actions
| Action | SSL primitive | Evidence |
|---|---|---|
| Inspect mobile architecture | READ | Domain/data/presentation files |
| Select state and platform strategy | SELECT | Riverpod/Bloc and platform constraints |
| Implement mobile code | WRITE | Widgets, screens, providers, clients |
| Validate lifecycle and permissions | VALIDATE | Dispose, permissions, offline behavior |
| Call verification tools | CALL_TOOL | Tests, builds, Maestro |
| Report result | NOTIFY | Final summary |
Tools and instruments
- Flutter/Dart or React Native stack
- Riverpod/Bloc, Dio, platform SDKs, Maestro
- Unit, widget, integration, and E2E test commands
Canonical workflow path
Use the configured code-intelligence provider to locate files and inspect symbols
or content. For Serena, use find_file, search_for_pattern,
get_symbols_overview, and find_symbol. Native search is limited to the
provider exclusions and non-code paths permitted by the project's search policy.
Then run the project's mobile verification commands, typically unit/widget tests and Maestro E2E for critical flows.
Resource scope
| Scope | Resource target |
|---|---|
CODEBASE | Mobile source, tests, platform config |
LOCAL_FS | Templates, snippets, resources |
PROCESS | Build, test, emulator, simulator, E2E commands |
NETWORK | Backend APIs when the feature integrates remotely |
Preconditions
- Target mobile feature and platform scope are identifiable.
- Required SDKs, permissions, and API contracts are available or assumptions are stated.
Effects and side effects
- Mutates mobile source, tests, and platform configuration.
- May affect permissions, app lifecycle, offline data, or performance.
Show full SKILL.md (496 more words)Show less
Guardrails
Apply framework, library, architecture, and data-model defaults only when the target project has no established choice. Scoped edits do not authorize a stack migration or unrelated infrastructure.
- Clean Architecture: domain -> data -> presentation
- Riverpod/Bloc for state management (no raw setState for complex logic)
- Material Design 3 (Android) + iOS HIG (iOS)
- All controllers disposed in
dispose()method - Use the platform transport with auth/retry/logging interception and offline handling: Flutter uses Dio, React Native uses axios behind TanStack Query, and Swift uses generated
Clientmiddleware. - 60fps target; verify supported target platforms (Swift iOS needs iOS only)
- Use Maestro for E2E testing of critical user flows
- Swift native: SwiftUI +
@MainActor @Observableview models (Observation framework, iOS 17+) — non-isolated VMs mutating observed state from aTaskare a Swift 6 strict-concurrency error - Swift native: use the existing API layer. When the project adopts OpenAPI generation, use its generated Client for covered endpoints; a UI-only edit does not introduce a generator.
- Swift native: when response caching is required, use the existing Repository cache; for a new hyperoslo/Cache implementation, use a ResponseCache actor — cache DECODED models (never
HTTPBody), serve stale-while-revalidate on reads, invalidate keys on writes; view models depend on a protocol seam, not the concrete service (seevariants/swift-ios/snippets.md§10) - Swift native: follow
App/Core/Features/Sharedproject layout - Swift native: iOS Human Interface Guidelines for all UI decisions
- Swift native: XCTest or Swift Testing for units, XCUITest for critical flows; cancel work via structured
.task {}(auto-cancels on disappear) — never indeinit, which is nonisolated and cannot touch@MainActorstate under Swift 6 (isolated deinit requires Swift 6.2+) - Swift native: restore edge swipe-back at the route layer — nav-bar-hidden screens (
.toolbar(.hidden, for: .navigationBar)) lose it, so register push routes via aswipeBackDestinationwrapper, not per-screen (seevariants/swift-ios/snippets.md§9) - Flutter: when offline response caching is required, use the existing repository cache; if adding Drift, read cached entities then revalidate (stale-while-revalidate), and invalidate/refresh affected rows on every write; cache decoded entities at the data layer, never at the Dio transport (see
variants/flutter/snippets.md§3, §10) - React Native: preserve the existing server-state layer; for TanStack Query with explicit
staleTime/gcTime— invalidate affected query keys on every mutation, persist account-scoped cache to MMKV only when offline persistence is required; screens consume query/mutation hooks, never call axios directly (seevariants/react-native/snippets.md)
References
- Execution steps (follow for the selected task):
resources/execution-protocol.md - Code snippets (Swift):
variants/swift-ios/snippets.md - Code snippets (Flutter):
variants/flutter/snippets.md - Code snippets (React Native):
variants/react-native/snippets.md - Checklist (run before handoff):
resources/checklist.md - Error recovery:
resources/error-playbook.md - Tech stack index (all platforms):
resources/tech-stack.md - Tech stack (Swift):
variants/swift-ios/tech-stack.md - Tech stack (Flutter):
variants/flutter/tech-stack.md - Tech stack (React Native):
variants/react-native/tech-stack.md - Screen template (Flutter):
resources/screen-template.dart - Screen template (Swift):
resources/screen-template.swift - Screen template (React Native):
resources/screen-template.tsx - API service template (Swift):
variants/swift-ios/api-template.swift - API service template (Flutter):
variants/flutter/api-template.dart - API service template (React Native):
variants/react-native/api-template.ts - Variant registry:
variants/README.md - Context loading:
../_shared/core/context-loading.md - Clarification:
../_shared/core/clarification-protocol.md - Context budget:
../_shared/core/context-budget.md - Lessons learned:
../_shared/core/lessons-learned.md(matching prior failure or requested retrospective) - Observability handoff:
../oma-observability/SKILL.md§Integrations — offline queuing, crash analytics, battery-aware sampling
© first-fluke, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 22 other files in skills/oma-mobile of first-fluke/oh-my-agent.
- SKILL.md
- resources/checklist.md
- resources/error-playbook.md
- resources/execution-protocol.md
- resources/screen-template.dart
- resources/screen-template.swift
- resources/screen-template.tsx
- resources/tech-stack.md
- variants/README.md
- variants/flutter/api-template.dart
- variants/flutter/snippets.md
- variants/flutter/stack.yaml
- variants/flutter/tech-stack.md
- variants/react-native/api-template.ts
- variants/react-native/snippets.md
- variants/react-native/stack.yaml
- variants/react-native/tech-stack.md
- … and 6 more
Open the folder on GitHubat commit b364119
Used in 1 other repository
We found 2 copies of this SKILL.md (exact, near-identical or edited) in other folders. This page covers the copy in first-fluke/oh-my-agent, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Oma Mobile next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Oma Mobile this skillfirst-fluke/oh-my-agent | 1.3k | — | ~2.4k | Automated safety check: Pass | MIT | |
| Developing Mobile Appstelagod/code-abyss | 243 | — | ~258 | Automated safety check: Pass | MIT | |
| Mobile Apps Createforcedotcom/sf-skills | 1.1k | — | ~1.4k | Automated safety check: Pass | Apache-2.0 | |
| Apple Designvrcm-team/VRCM | 179 | 1 repos | ~6.2k | Automated safety check: Pass | MIT | |
| Mobile DesignxenitV1/Antigravity-Workflows | 130 | 2 repos | ~3.7k | Automated safety check: Notes | MIT | |
| SimdeckNativeScript/SimDeck | 152 | — | ~3.6k | Automated safety check: Pass | MIT |
Similar skills
Mobile Apps Create
forcedotcom/sf-skills
The entry point for building any Salesforce native mobile app on iOS or Android.
Apple Design
vrcm-team/VRCM
Cross-platform UI/UX design reviewer grounded in Apple's Human Interface Guidelines (122 pages pulled from developer.apple.com, including 57 component pages) plus a design-craft lens for…
Mobile Design
xenitV1/Antigravity-Workflows
Mobile-first design thinking and decision-making for iOS and Android apps.
Simdeck
NativeScript/SimDeck
A skill your agent uses for simulator lifecycle, app install/launch, live viewing, UI inspection, touch/keyboard automation, screenshots, recordings, logs, pasteboard, hardware controls, and…
Mobile Design
agent-skills-hub/agent-skills-hub
Mobile-first design and engineering doctrine for iOS and Android apps.
More from first-fluke/oh-my-agent
All 57 skills in this repoOMA Multi-Agent Orchestration
first-fluke/oh-my-agent
Decomposes a complex feature into tasks, dispatches parallel specialist agents with durable state, and supervises verification, QA review and retries.
OMA Multi-Agent Orchestrator
first-fluke/oh-my-agent
Splits a complex feature into prioritized tasks, spawns specialist CLI subagents in parallel, tracks them through shared memory and verifies each result.
Architecture Decisions and ADRs
first-fluke/oh-my-agent
Evaluates system boundaries and tradeoffs and writes architecture recommendations, option comparisons or ADRs, with a Mermaid diagram when structure changes.
OMA Backend Agent
first-fluke/oh-my-agent
Backend specialist for APIs, database work, authentication and migrations that follows clean architecture with router, service and repository layers.
oma Bootstrap
first-fluke/oh-my-agent
Installs or checks the oma CLI and its runtimes (bun, uv, serena) in a fresh workspace so that oma-* skills can run their commands.
Design-First Brainstorm
first-fluke/oh-my-agent
Explores intent, constraints and alternative approaches before any planning, working through questions one at a time and saving an approved design for later steps.
Related
Works with
Categories
Questions about Oma Mobile
What does Oma Mobile do?
Implement Flutter, React Native, or native Swift apps. An agent skill from first-fluke/oh-my-agent. Oma Mobile is an agent skill from first-fluke/oh-my-agent. Implement Flutter, React Native, or native Swift apps.
When should I use Oma Mobile?
Oma Mobile fits situations like: platform integrations; application data flows.
How do I install Oma Mobile in Claude Code?
Run `npx skills add first-fluke/oh-my-agent --skill oma-mobile -a claude-code`. Or copy the skill folder (skills/oma-mobile in first-fluke/oh-my-agent) into .claude/skills/oma-mobile in your project. Claude Code loads it when a task matches its description.
How do I install Oma Mobile in Codex?
Run `npx skills add first-fluke/oh-my-agent --skill oma-mobile -a codex`. Or copy the skill folder (skills/oma-mobile in first-fluke/oh-my-agent) into .agents/skills/oma-mobile in your project. Codex loads it when a task matches its description.
Can I use Oma Mobile in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add first-fluke/oh-my-agent --skill oma-mobile -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/oma-mobile, .gemini/skills/oma-mobile, .github/skills/oma-mobile and .opencode/skills/oma-mobile in your project.
What does Oma Mobile need to run?
Going by SKILL.md and its folder, Oma Mobile needs Dart, Swift and TypeScript for the scripts in its folder. Our summary lists: Node.js.
Does Oma Mobile access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Oma Mobile safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Oma Mobile use?
Oma Mobile is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Oma Mobile use?
About 2.4k tokens (SKILL.md is roughly 9.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Oma Mobile?
Skills that share tags, products or a category with Oma Mobile: Developing Mobile Apps (telagod/code-abyss, 243 stars), Mobile Apps Create (forcedotcom/sf-skills, 1.1k stars), Apple Design (vrcm-team/VRCM, 179 stars) and Mobile Design (xenitV1/Antigravity-Workflows, 130 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Oma Mobile?
first-fluke (a GitHub organization) maintains it in first-fluke/oh-my-agent, which has 1,338 GitHub stars. The repository holds 57 skills in this directory. The repository was last updated on October 9, 2026.
Source: first-fluke/oh-my-agent on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.