agentsclimarketplace
Sign in

Appstore release director

Skill Xopoko/plug-n-skills/plugins/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/plug-n-skills --skill appstore-release-director

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

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/

references/

scripts/

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

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

  • Document a rollback plan before deploymentin 41 of 779, across 22 files
  • Update the changelogin 21 of 779, across 19 files
  • Run the test suitein 20 of 779
  • Create an annotated git tagin 20 of 779
  • Clean up feature flags after full rolloutin 18 of 779, across 10 files
  • Verify deployment health after launchin 18 of 779, across 10 files
  • Test both feature flag statesin 17 of 779, across 9 files
  • Verify the working tree is cleanin 17 of 779
  • Make database migrations backward-compatiblein 16 of 779, across 8 files
  • Set up error monitoring before launchin 15 of 779, across 7 files
  • Monitor metrics at each rollout stagein 14 of 779, across 5 files
  • Create a GitHub releasein 14 of 779

Said here and by no other author read

  • Discover release truth from repository state
  • Verify Apple account and signing configuration
  • Archive and export an App Store IPA
  • Validate and upload the archive
  • Link build and resolve metadata issues
  • Generate final release evidence

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 326,144. 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.