Automated summary
Deploys JavaScript/UI changes via EAS Update without requiring a native rebuild (OTA).
Strengths
- Enables fast updates without native rebuild
- Targets UI, business logic, and JS dependency changes
- Uses dev branch by default for safe deployment
- Non-interactive for automated workflows
Limitations
- Only works for pure JavaScript changes
- Does not replace native rebuild for native modules or configuration
- Requires internet connection and an configured EAS project
Use this skill to quickly deploy UI or logic changes without waiting for a native rebuild.
Do not use for native changes like permissions, icons, or native modules; prefer a full rebuild instead.
Security analysis
SafeThe skill runs a well-known Expo CLI command ('npx eas update') with a fixed branch and message. No destructive, exfiltrating, or obfuscated actions. It operates within the app directory and does not involve sensitive data exposure or system compromise.
No concerns found
How this analysis is madeExamples
Deploy the updated login screen styles via OTA.Run an OTA update for the new API call changes.Use EAS Update to deploy my latest JS changes without rebuilding.name: ota description: Deploy JavaScript/UI changes via EAS Update without native rebuild (OTA = Over-The-Air). Use for UI components, styling, screen layouts, navigation, business logic, API calls, text/strings, or pure JS dependencies. Use when the user mentions "ota", "EAS Update", "OTA deploy", "JS update", "UI update", or wants to deploy code changes without rebuilding. user-invocable: true
/ota - OTA Update Deployment
Run EAS Update to deploy JavaScript/UI changes without native rebuild (OTA = Over-The-Air).
Execution Requirements
IMPORTANT: Execute npx commands from the app root directory (APPNAME directory, not the .git root).
Command
cd APPNAME # Move to app directory from project root
npx eas update --branch dev --message "OTA update from Claude Code" --non-interactive
Use This For
JavaScript-only changes that don't require native rebuild:
- UI components, styling
- Screen layouts, navigation
- Business logic (TypeScript/JavaScript)
- API calls, text/strings
- Pure JS dependencies
When NOT to Use
For native changes, use /dist-dev-client instead:
- Intent handlers / deep links
- Permissions
- Native modules
- Package name changes
- App icon or splash screen
- Build configuration (app.json affecting native)
Instructions for Claude
When this skill is invoked:
- Verify current directory: Ensure you're in the app root (APPNAME directory)
- Run EAS Update:
cd APPNAME npx eas update --branch dev --message "OTA update from Claude Code" --non-interactive - Inform the user: Explain that the update was deployed and users need to restart the app to see changes
- Verify success: Check command output for successful deployment confirmation
Success Indicators
- "Published" message in output
- Update ID shown
- No error messages
Common Issues
- Not in app directory: Remind user that command must be run from APPNAME directory
- Not logged in: Run
eas loginfirst - No EAS project: Run
eas initfirst
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/ota-update-deployment-with-eas-mmio71b7/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/ota-update-deployment-with-eas-mmio71b7' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/ota-update-deployment-with-eas-mmio71b7/download' --output '.skill-downloads/ota-update-deployment-with-eas-mmio71b7/SKILL.md.part' && mv '.skill-downloads/ota-update-deployment-with-eas-mmio71b7/SKILL.md.part' '.skill-downloads/ota-update-deployment-with-eas-mmio71b7/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/ota-update-deployment-with-eas-mmio71b7/SKILL.md' && test -s '.skill-downloads/ota-update-deployment-with-eas-mmio71b7/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/ota' && cp -R '.skill-downloads/ota-update-deployment-with-eas-mmio71b7' '.claude/skills/ota'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/ota-update-deployment-with-eas-mmio71b7'openskills read 'ota-update-deployment-with-eas-mmio71b7'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/ota-update-deployment-with-eas-mmio71b7/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.