Verify candidate builds, distribution eligibility, review materials, platform processing and actual installation for TestFlight internal testing, external testing and App Store submission.
For Apple app owners, testers and release staff. To prepare internal or external TestFlight testing or an App Store submission, use the authorized stage, team, app record, Bundle ID, candidate package and signing material. Deliver channel checks and evidence for the same build.
How to verify the work
Read the version, build, signing and bundled assets from the archive. Confirm processing, group assignment or review for the channel. Where in scope, verify a tester actually installed and launched it, or check the public version in the target region.
When to hand it over
Give the responsible owner the verified build, evidence and first unchecked stage. Hold the relevant upload, review submission or release if the team, signing, review material or authorization is missing.
What to measure
Log actual installations or the visible version by channel. Count returns due to mismatched builds, signing or review material.
What it does
Link the Apple candidate, signing, review material and platform evidence to the same build.
What it helps with
Verify eligibility for internal testing, external testing or the store separately from actual tester installs.
Why it matters
Keep release approvals, materials and evidence traceable to reduce misreading review or distribution status.
PDF · Chinese
Guide
Core guidance, examples and a revision worksheet. PDF in Chinese.
Start with the intended channel. Match the team, App record, bundle ID, version, build, signing and review materials to one candidate. Keep evidence for each stage through installation by the intended tester or verification of the public product page in the target region.
What to prepare
Authorized stage, Apple team, App record, bundle ID, candidate version and build
Archive and signing evidence, bundled assets, third-party SDKs, privacy and asset permissions, and test and review materials
What you receive
A checklist linking candidate package, signing, channel eligibility and materials to one build
Separate receipts for upload, processing, group assignment or review, and actual installation or public availability
The first pending stage, the evidence needed and the person responsible
Who it is for
Preparing TestFlight internal or external testing or an App Store submission
Handing off an unsigned archive or a development-signed package and identifying the next evidence needed
How the work progresses
01
Identify the intended stage and confirm the team and App record
02
Inspect the archive, signing, entitlements and bundled assets, then check privacy, rights and test materials against the actual package
03
Verify upload, processing, group assignment or review for that build on the selected channel
04
Verify installation and launch from the real test channel or check the visible version in the target region, and record pending work
Getting started
Download and extract the complete ZIP. Read the README if included, or start with SKILL.md. Install the complete folder containing SKILL.md in your AI tool’s skills directory under the skill name. In a multi-version repository, choose the version you need and retain its supporting files. Try a small task with the required inputs and review the result.
The Skill and training PDF are in Chinese. The website describes them in seven languages.
Verify unsigned archives, development installs and eligibility for the target channel separately. Use the platform record for the intended team and build.
Account, group, upload, review submission and release actions follow the current authorization.
Verify candidate builds, distribution eligibility, review materials, platform processing and actual installation for TestFlight internal testing, external testing and App Store submission.