agentsclimarketplace

Appstore release director

Skill Xopoko/build-swift-apps/skills/appstore-release-director

End-to-end iOS App Store publishing from local repo to App Store Connect readiness, upload, TestFlight, App Review submission/resubmission, or review issue triage, including signing, metadata, privacy, icons, screenshots, subscriptions, and release evidence.From its SKILL.md

Install
npx -y skills add Xopoko/build-swift-apps --skill appstore-release-director

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

2 things to look at

  • reads credentialsReads from 1 credential source: `.codex-private/apple/`.
  • fetches URLsInstructs the agent to fetch 1 URL, including https://www.apple.com/legal/internet-services/itunes/dev/stdeula/.

SKILL.md

3.5 KB, 721 tokens by cl100k_base, as published. Nobody here has run it

App Store Release Director

Broad release orchestration. For focused asc work, delegate to appstore-connect-cli, appstore-id-resolver, appstore-archive-uploader, appstore-release-planner, appstore-review-readiness, appstore-metadata-sync, appstore-metadata-localizer, appstore-screenshot-pipeline, and appstore-signing-setup.

Workflow

  1. Discover release truth:
    • git root, workspace/project, scheme, bundle ID, version/build, deployment target, entitlements, generator ownership;
    • existing handoff/docs: apple-publishing-handoff.md, manifest JSON, release, appstore, testflight, fastlane, ExportOptions.plist.
  2. Verify Apple account/signing:
    • team, Team ID, API key, identities, Bundle ID resource/capabilities, distribution cert, provisioning profile;
    • keep .p8, .p12, profiles, passwords, and decoded plists out of git; prefer .codex-private/apple/ or a secret store.
  3. Prepare App Store Connect:
    • app record, platform, bundle, app info, categories, pricing/availability, age rating, privacy/support URLs, screenshots, App Privacy, review details, release option;
    • for subscriptions, verify products and Terms/EULA link. Standard EULA: https://www.apple.com/legal/internet-services/itunes/dev/stdeula/.
  4. Compliance preflight:
    • production runtime config, legal URLs return 2xx/3xx, encryption/export compliance, privacy/tracking claims match code/SDKs.
  5. Build/test/archive/export/upload:
    • choose unique build number from live ASC state;
    • run required tests/smoke checks;
    • archive for generic/platform=iOS, export App Store IPA, validate, upload, wait for processing.
  6. Link build and submit/readiness:
    • attach processed build, resolve metadata-only issues before new binaries, cancel/complete old submissions if blocking.
  7. Finish evidence:
    • handoff/manifest: version/build, archive/IPA paths, SHA-256, delivery UUID, ASC build state, review submission ID, legal URLs, screenshots, remaining risks.

References

Load only the current stage:

  • references/end-to-end-workflow.md
  • references/signing-and-provisioning.md
  • references/app-store-connect-api.md
  • references/metadata-compliance.md
  • references/build-upload-submit.md
  • references/troubleshooting.md

Helpers:

  • scripts/make_export_options.py
  • scripts/appstore_preflight.py

Run helper scripts with python3 and inspect --help.

Rules

  • Operate from live repo/ASC/App Review state, not memory.
  • Never commit Apple secrets/profiles unless explicitly requested and the repo is intended for them.
  • Do not overwrite user changes or release docs without reading them.
  • Apple requirements change; verify current screenshots, privacy, subscriptions, and review behavior.
  • For legal text, draft only practical copy and state which business/legal facts need owner confirmation.
  • If blocked by Apple web-only UI, permissions, legal answers, or 2FA, stop with evidence and the smallest required user action.

Final Report

Report build/version, validation/upload status and delivery UUID, ASC build/review status, legal/privacy/screenshot/subscription/encryption state, files/artifacts changed, tests run, and anything not verified.

What ships with it: 9 files

34.1 KB alongside SKILL.md, 2 of them executable

agents/

Gives 0 of the 12 instructions most ship operate skills give in 721 tokens

Counted across 1,077 of the 1,713 authors here whose files we hold, read 2026-09-06

  • Create GitHub releasein 44 of 1077, across 43 files
  • Run the test suitein 30 of 1077, across 25 files
  • Create and push git tagin 27 of 1077, across 26 files
  • Push commits and tagsin 27 of 1077
  • Create annotated tagin 25 of 1077, across 22 files
  • Ensure working tree is cleanin 24 of 1077
  • Check for product marketing context firstin 23 of 1077, across 6 files
  • Commit version bump changesin 22 of 1077, across 21 files
  • Update CHANGELOG.mdin 21 of 1077, across 20 files
  • Structure launch marketing across three channel typesin 20 of 1077, across 5 files
  • Commit and tag the releasein 20 of 1077, across 18 files
  • Update the CHANGELOG for new releasesin 19 of 1077

Said here and by no other author read

  • Discover release truth from repository
  • Verify Apple account and signing
  • Prepare App Store Connect records
  • Run compliance preflight checks
  • Archive and upload IPA
  • Submit build for review

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.