Is appstore-review-readiness safe to install?

SaferSkills independently audited appstore-review-readiness (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.

CategoryWeightCategory scoreContribution

Securityprompt, exec, net, exfil, eval

35%

100

35.0 pts

Supply chainhash, typosquat, maintainer, lockfile

20%

100

20.0 pts

Maintenancestaleness, pinning, CI

15%

100

15.0 pts

TransparencySKILL.md, perms, README

15%

100

15.0 pts

Communityinstalls, verify, response

15%

100

15.0 pts

Findings & checks · 0 flagged

Securityscore 100 · 0 findings

✓—All security checks passedNo findings in this category for the latest scan.pass

Supply chainscore 100 · 0 findings

✓—All supply chain checks passedNo findings in this category for the latest scan.pass

Maintenancescore 100 · 0 findings

✓—All maintenance checks passedNo findings in this category for the latest scan.pass

Transparencyscore 100 · 0 findings

✓—All transparency checks passedNo findings in this category for the latest scan.pass

Communityscore 100 · 0 findings

✓—All community checks passedNo findings in this category for the latest scan.pass

The primary manifest — the file an agent reads to learn what this artifact does.

plugins/build-swift-apps/skills/appstore-review-readiness/SKILL.md · 1 file

plugins/build-swift-apps/skills/appstore-review-readiness/SKILL.md4.0 KB · Markdown

name: appstore-review-readiness

description: Validate App Store submission readiness, submit prepared versions, monitor or cancel review status, and repair common ASC blockers with current `asc` commands.

App Store Review Readiness

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

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.

Readiness

asc builds info --build-id "BUILD_ID"
asc validate --app "APP_ID" --version "1.2.3" --platform IOS --output table
asc validate --app "APP_ID" --version "1.2.3" --platform IOS --strict --output table
asc validate --app "APP_ID" --version-id "VERSION_ID" --platform IOS --output table

Check processingState=VALID, encryption, content rights, localizations, screenshots, app-info/privacy URL, digital goods, IAP/subscriptions, and App Privacy.

Common repairs:

asc encryption declarations list --app "APP_ID"
asc encryption declarations create --app "APP_ID" --app-description "Uses standard HTTPS/TLS" \
  --contains-proprietary-cryptography=false --contains-third-party-cryptography=true \
  --available-on-french-store=true
asc encryption declarations assign-builds --id "DECLARATION_ID" --build "BUILD_ID"
asc encryption declarations exempt-declare --plist "./Info.plist"

asc apps content-rights view --app "APP_ID"
asc apps content-rights edit --app "APP_ID" --uses-third-party-content=false

asc metadata pull --app "APP_ID" --version "1.2.3" --platform IOS --dir "./metadata"
asc metadata validate --dir "./metadata" --output table
asc metadata push --app "APP_ID" --version "1.2.3" --platform IOS --dir "./metadata" --dry-run --output table

asc screenshots list --version-localization "LOC_ID" --output table
asc screenshots validate --path "./screenshots" --device-type "IPHONE_65" --output table
asc validate iap --app "APP_ID" --output table
asc validate subscriptions --app "APP_ID" --output table

App Privacy publish state is not fully verifiable through the public API; use experimental web flow or confirm manually:

asc web privacy pull --app "APP_ID" --out "./privacy.json"
asc web privacy plan --app "APP_ID" --file "./privacy.json"
asc web privacy apply --app "APP_ID" --file "./privacy.json"
asc web privacy publish --app "APP_ID" --confirm

Submit

asc review submit --app "APP_ID" --version "1.2.3" --build "BUILD_ID" --dry-run --output table
asc review submit --app "APP_ID" --version "1.2.3" --build "BUILD_ID" --confirm

asc publish appstore --app "APP_ID" --ipa "./App.ipa" --version "1.2.3" --submit --dry-run --output table
asc publish appstore --app "APP_ID" --ipa "./App.ipa" --version "1.2.3" --submit --confirm

Add --wait when build processing should be awaited.

Multi-item submissions:

asc review submissions-create --app "APP_ID" --platform IOS
asc review items-add --submission "SUBMISSION_ID" --item-type appStoreVersions --item-id "VERSION_ID"
asc review items-add --submission "SUBMISSION_ID" --item-type gameCenterChallengeVersions --item-id "GC_CHALLENGE_VERSION_ID"
asc review submissions-submit --id "SUBMISSION_ID" --confirm

For non-renewing IAPs that must be selected with the next version and public APIs reject the path, use asc web review iaps attach --app "APP_ID" --iap-id "IAP_ID" --confirm and document that it is unofficial.

Monitor / Retry

asc status --app "APP_ID"
asc submit status --id "SUBMISSION_ID"
asc submit status --version-id "VERSION_ID"
asc review submissions-list --app "APP_ID" --paginate
asc submit cancel --id "SUBMISSION_ID" --confirm
asc review submissions-cancel --id "SUBMISSION_ID" --confirm

For state errors, re-check valid build attachment, export compliance, content rights, localizations/screenshots, review details, pricing/availability, and App Privacy. macOS uses the same review flow with --platform MAC_OS.

appstore-review-readiness— agent skill

Is appstore-review-readiness safe to install?

App Store Review Readiness

Readiness

Submit

Monitor / Retry

Audit the pieces. Scan the whole. Decide.