Appstore review readiness

Skill Xopoko/plug-n-skills/plugins/build-swift-apps/skills/appstore-review-readiness

Validate App Store submission readiness and execute prepared review actions with current `asc` commands. Use after appstore-release-planner chooses the review path, or when the user directly asks to validate, stage, submit, monitor, cancel, or repair ASC review blockers.From its SKILL.md

Install

npx -y skills add Xopoko/plug-n-skills --skill appstore-review-readiness

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

9 stars9 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.3 KB, 440 tokens by cl100k_base, as published. Nobody here has run it

App Store Review Readiness

Use asc validate and current review commands. Do not use legacy submit-preflight or submit-create shortcuts.

For go/no-go planning, first-submission strategy, or choosing which release skill owns a blocker, use appstore-release-planner first. This skill owns command execution once the review-readiness path is selected.

Preconditions: auth configured; app/version/build IDs resolved; build processing complete unless using --wait; metadata, app info, screenshots, review details, content rights, encryption, pricing, availability, and App Privacy expected complete.

Command Plan Helper

For a deterministic dry-run command plan, run the helper from the plugin root:

python3 "$PLUGIN_ROOT/skills/appstore-review-readiness/scripts/review_readiness_plan.py" \
  --app "APP_ID" --version "1.2.3" --platform IOS --build "BUILD_ID" \
  --version-id "VERSION_ID" --submission-id "SUBMISSION_ID" \
  --metadata-dir "./metadata" --include-submit

The helper prints commands only; it does not call ASC, mutate review state, or read credentials. Pass --json for machine-readable output. Pass --confirming-actions only after manually verifying that generated --confirm commands are intended.

Workflow

Generate the helper plan unless the user requested one specific command.
Run read-only readiness checks first: processed build state, normal validate, strict validate, and version-id validate when available.
Repair blockers in the smallest owning surface: encryption, content rights, metadata, screenshots, IAP/subscriptions, or App Privacy.
Submit only after dry-run output is clean and the user has clearly selected the build/version to send.
Monitor by app, version ID, or submission ID; cancel only when the active submission is identified and the user intends cancellation.

For macOS App Store review, use the same flow with --platform MAC_OS.

References

references/appstore-review-readiness.md for detailed ASC repair, submit, multi-item submission, monitor, and retry commands.

What ships with it: 1 file

10.1 KB alongside SKILL.md, 1 of them executable

scripts/

review_readiness_plan.pyruns10.1 KB

Gives 0 of the 12 instructions most review quality skills give in 440 tokens

Counted across 1,048 of the 1,783 authors here whose files we hold, read 2026-08-07

Ask questions one at a timein 81 of 1048, across 64 files
Provide a recommended answer for each questionin 73 of 1048, across 50 files
Explore the codebase instead of asking answerable questionsin 66 of 1048, across 42 files
Resolve dependencies between decisions one-by-onein 42 of 1048, across 17 files
Interview the user relentlessly about the planin 38 of 1048, across 13 files
Order findings by severityin 31 of 1048
Resolve each branch of the decision treein 27 of 1048, across 5 files
Run a grilling sessionin 26 of 1048, across 5 files
Update CONTEXT.md immediately when a term is resolvedin 26 of 1048, across 11 files
Propose precise canonical terms for vague languagein 25 of 1048, across 7 files
Create documentation files lazilyin 24 of 1048, across 5 files
Assign severity to every findingin 24 of 1048

Said here and by no other author read

use current asc commands
do not use legacy submit shortcuts
use release planner for go/no-go planning
run the command plan helper
run read-only readiness checks first
repair blockers in the smallest owning surface

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.