Ios App Store Validator
Scannednpx machina-cli add skill gygantskiyMatilyock/ios-developer-agents/ios-app-store-validator --openclawiOS App Store Validator
Use this skill when preparing an iOS app for App Store submission. This validates against Apple's App Store Review Guidelines to catch rejection-worthy issues early.
When to Use
- Before submitting to App Store Connect
- When preparing for TestFlight external testing
- After significant app updates
- When adding new permissions or entitlements
- When concerned about potential rejection
How to Apply
Read the full agent prompt from agents/app-store-validator/app-store-validator.md in the ios-developer-agents repository.
Follow the validation process:
- Fetch Current Guidelines - Get latest from developer.apple.com
- Technical Configuration Scan
- Info.plist validation (usage descriptions, capabilities)
- Privacy Manifest (PrivacyInfo.xcprivacy)
- Entitlements check
- Code-level issues (private APIs, deprecated frameworks)
- Metadata Validation - App name, description, screenshots, age rating
- Privacy & Legal Compliance - Privacy policy, terms, GDPR/CCPA
- In-App Purchase Validation - If applicable
Output Format
Provide structured findings with:
- Submission Readiness status (READY / BLOCKED / NEEDS REVIEW)
- Blockers (will cause rejection)
- Warnings (may cause rejection)
- Metadata review table
- Technical configuration table
- Pre-submission checklist
Source
git clone https://github.com/gygantskiyMatilyock/ios-developer-agents/blob/master/.claude/skills/ios-app-store-validator/SKILL.mdView on GitHub Overview
The iOS App Store Validator checks your app against Apple’s App Store Review Guidelines before submission. It highlights blockers, warnings, and metadata gaps to minimize rejection risk.
How This Skill Works
It fetches the latest guidelines from Apple and the repository guidance, then runs a Technical Configuration Scan covering Info.plist entries, Privacy Manifest (PrivacyInfo.xcprivacy), entitlements, and code-level issues. It then performs Metadata Validation and Privacy/Legal Compliance checks, followed by In-App Purchase validation if applicable. The results are delivered as a structured report with Submission Readiness, Blockers, Warnings, and dedicated metadata and technical tables.
When to Use It
- Before submitting to App Store Connect
- When preparing for TestFlight external testing
- After significant app updates
- When adding new permissions or entitlements
- When concerned about potential rejection
Quick Start
- Step 1: Fetch the latest guidelines from developer.apple.com
- Step 2: Run the Technical Configuration Scan (Info.plist, Privacy Manifest, entitlements, and code checks)
- Step 3: Review metadata, privacy/legal compliance, and prepare the Output Format report
Best Practices
- Fetch the latest App Store Guidelines before each release
- Run the Technical Configuration Scan (Info.plist, Privacy Manifest, entitlements, code issues)
- Validate Info.plist usage descriptions and required capabilities
- Verify Privacy Manifest and GDPR/CCPA compliance, plus a privacy policy
- Review metadata (name, description, screenshots) and only enable IAP if applicable
Example Use Cases
- Before submitting a new version to App Store Connect
- During TestFlight external testing to catch rejection risks early
- After adding new permissions or entitlements
- When preparing for major app updates that change privacy or data usage
- Prior to release after significant code changes