Add Expo Apple Targets
Plan native Apple targets in an Expo SDK 54 app, including widgets, App Clips, watch apps, share extensions, and notification extensions. Use when the user needs an Apple-only extension and wants to preserve Expo compatibility.
Install
$ agentstack add skill-khadinakbarlabs-expo-mobile-app-builder-add-expo-apple-targets ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-khadinakbarlabs-expo-mobile-app-builder-add-expo-apple-targets) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Add Apple targets to an Expo app
Use a native target only when its user benefit cannot be delivered by the main Expo app. A target changes the native project, signing surface, app identifiers, and test matrix.
Discovery
- Identify the exact target type, platform minimum, required entitlements, data boundary, and fallback in the main app.
- Verify the SDK 54 compatibility of the chosen config plugin or native-target tool before adding it. Keep the dependency name and version user-selected instead of assuming a private or newer-Expo setup.
- Explain whether the work requires generating native projects or editing existing
ios/files. Ask before a clean prebuild because it can replace generated native changes.
Safe target plan
- Keep every target's bundle identifier based on a generic owner-controlled suffix, such as
com.example.myapp.widget. - Add App Groups, keychain sharing, notification, or background entitlements only when the product needs them. Treat each as a data-sharing boundary.
- Share only display-safe data between target and main app. Never place secrets, session tokens, raw user content, or signing files in an App Group.
- Build a target-specific test checklist: clean install, extension unavailable, disabled permissions, no data, localized text, accessibility, and native signing validation.
Release boundary
Do not create credentials, modify a provider dashboard, start an EAS build, or upload an Apple binary until the user names the target account and confirms the action.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: khadinakbarlabs
- Source: khadinakbarlabs/expo-mobile-app-builder
- License: MIT
- Homepage: https://khadinakbar.com
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.