agentsclimarketplace

Appstore review readiness

Skill Xopoko/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/build-swift-apps --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

  • runs commandsInstructs the agent to run 1 command, including `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 "S`.

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

  1. Generate the helper plan unless the user requested one specific command.
  2. Run read-only readiness checks first: processed build state, normal validate, strict validate, and version-id validate when available.
  3. Repair blockers in the smallest owning surface: encryption, content rights, metadata, screenshots, IAP/subscriptions, or App Privacy.
  4. Submit only after dry-run output is clean and the user has clearly selected the build/version to send.
  5. 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/

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

Counted across 1,273 of the 2,403 authors here whose files we hold, read 2026-09-06

  • Ask one question at a timein 63 of 1273, across 62 files
  • Provide a recommended answer for each questionin 47 of 1273, across 45 files
  • Rank findings by severityin 44 of 1273
  • Use parameterized queries for database accessin 38 of 1273, across 20 files
  • Validate all user input with schemasin 33 of 1273, across 15 files
  • Store secrets in environment variablesin 32 of 1273, across 14 files
  • Explore the codebase to answer questionsin 31 of 1273, across 29 files
  • Store tokens in httpOnly cookiesin 30 of 1273, across 12 files
  • Implement rate limiting on API endpointsin 30 of 1273, across 12 files
  • Sanitize user-provided HTMLin 29 of 1273, across 11 files
  • Return generic error messages to usersin 28 of 1273, across 10 files
  • Cite file and line for every findingin 28 of 1273, across 25 files

Said here and by no other author read

  • Use asc validate for review commands
  • Run the helper script for a command plan
  • Perform read-only readiness checks first
  • Repair blockers in the smallest owning surface
  • Submit only after clean dry-run output
  • Monitor by app version or submission ID

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.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.