Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Distribute iOS and macOS beta builds with TestFlight, tester management, and CI/CD automation.
Distribute iOS and macOS beta builds with TestFlight, tester management, and CI/CD automation.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
User needs to distribute beta builds via TestFlight. Agent handles App Store Connect setup, tester groups, build uploads, and CI/CD integration.
TopicFileCI/CD automationci-cd.md
Before uploading: Bundle ID registered in Developer Portal App created in App Store Connect App-specific password or API key configured
Every TestFlight build needs: Unique build number (CFBundleVersion) - increment ALWAYS Valid provisioning profile (App Store distribution) No missing compliance declarations
GroupPurposeLimitInternalTeam members with App Store Connect access100ExternalBeta testers, requires review10,000 Internal builds available immediately. External requires Apple review (24-48h first time).
MethodBest ForXcodeManual, one-off uploadsxcrun altoolScripts, CI without fastlaneFastlaneFull automation, multiple appsXcode CloudApple-native CI/CDTransporterGUI for non-developers
TestFlight builds expire after 90 days. Plan releases accordingly.
Build number not incremented - rejected immediately, must bump and rebuild Missing export compliance - stuck in "Processing" until answered in App Store Connect External testers on first build - requires full beta review, use internal first Expired provisioning profile - upload fails silently, check before archiving App-specific password in CI - use App Store Connect API key instead (more secure, no 2FA issues)
App Store Connect > Users > Keys > App Store Connect API Generate key with "App Manager" role Download .p8 file (only shown ONCE) Note: Issuer ID, Key ID
# In Fastfile lane :beta do build_app(scheme: "MyApp") upload_to_testflight( api_key_path: "fastlane/api_key.json", skip_waiting_for_build_processing: true ) end
xcrun altool --upload-app \ --type ios \ --file "MyApp.ipa" \ --apiKey "KEY_ID" \ --apiIssuer "ISSUER_ID"
Data that leaves your machine: IPA/app binary uploaded to Apple servers Build metadata (version, bundle ID, team) Data that stays local: API keys and certificates (keep in Keychain) Source code (not uploaded) This skill does NOT: Store Apple credentials in plain text Share builds outside Apple's infrastructure
Install with clawhub install <slug> if user confirms: ios — iOS development patterns xcode — Xcode workflows flutter — cross-platform builds
If useful: clawhub star testflight Stay updated: clawhub sync
Messaging, meetings, inboxes, CRM, and teammate communication surfaces.
Largest current source with strong distribution and engagement signals.