rudrankriyam/app-store-connect-cli-skills
22 skills42.1k installs18.6k starsGitHub
Install
npx skills add https://github.com/rudrankriyam/app-store-connect-cli-skillsSkills in this repo
1Asc Cli Usageasc-cli-usage is an agent skill that teaches procedural knowledge for the asc command-line interface against Apple App Store Connect. It is aimed at solo and indie mobile builders who automate release work from Claude Code, Cursor, or similar agents and need consistent, scriptable commands instead of ad-hoc guesses from old blog posts. Use it whenever you or your agent must run, design, or document asc workflows: discovering command paths, inspecting bundled API schemas, checking capability coverage gaps, listing and uploading builds, editing availability, submitting for review, publishing releases, and polling long-running processing states. The skill stresses help-driven discovery, preferred modern verbs over deprecated aliases, explicit output format selection, safe authentication patterns, pagination for large result sets, and confirmation gates before destructive operations. That matters because App Store mistakes are slow and costly—wrong IDs, stale aliases, and unparsed JSON in CI create review delays and flaky pipelines. Pair this skill with the asc binary and App Store Connect API credentials in your repo or CI environment; it does not replace Apple’s web-only workflows fl2.5kinstalls2Asc Xcode Buildasc-xcode-build teaches coding agents to prepare Apple platform releases using the App Store Connect CLI’s Xcode helpers instead of fragile raw xcodebuild one-liners. It targets indie iOS developers shipping with Claude Code, Cursor, or Codex who need a repeatable archive → export flow and synchronized marketing version and build numbers. The skill walks through viewing and bumping versions, fetching the next acceptable build number from App Store Connect for a given app ID and platform, then archiving and exporting for upload. Preconditions assume Xcode, valid signing, and configured ASC credentials. Use in Ship when you are creating an IPA or PKG for upload or right before you invoke asc upload or submission skills in the same repo family.2.4kinstalls3Asc Release Flowasc-release-flow is an agent skill for indie iOS builders using the App Store Connect CLI (`asc`) when the question is whether an app can be submitted now and how to complete the current public release path. It enforces a strict answer order: state readiness immediately, list blockers, separate fixes available through the public API from those requiring web session or manual App Store Connect steps, and output the next precise command. Preconditions require resolving identifiers up front, configuring auth via `asc auth login` or `ASC_*` variables, and keeping canonical metadata under `./metadata` when staging from files. The skill spans validation, build attachment, review details, content rights, encryption declarations, IAP and subscription readiness, Game Center items, and App Privacy publish state—calling out where `asc web` commands are optional experimental escape hatches. It is for operators who want a disciplined release checklist rather than guessing which portal screen is still red.2.4kinstalls4Asc Submission Healthasc-submission-health is an agent skill for solo and indie iOS builders who ship with the App Store Connect CLI. It walks you through pre-submission checks—confirming the build finished processing, running the supported `asc validate` command (not retired shortcuts), and handling encryption compliance before you submit a version for Apple review. The workflow assumes auth, app/version/build IDs, and that listing assets are largely complete, with optional `--wait` when you need processing to finish first. It is aimed at builders who want fewer preventable rejections and a repeatable way to monitor review state while shipping or debugging a submission. Use it at the end of your mobile release path when the binary is ready and the store record must pass Apple's gates.2.4kinstalls5Asc Metadata Syncasc-metadata-sync teaches solo and indie iOS builders how to treat App Store metadata as repo-owned JSON synced through the App Store Connect CLI. You pull canonical app-info and version localization fields into metadata/app-info/<locale>.json and metadata/version/<version>/<locale>.json, edit name, subtitle, description, keywords, URLs, and what’s new locally, then validate and apply back to App Store Connect. The skill steers you away from drifting fastlane-only workflows unless you truly need .strings files or migration from legacy fastlane trees. That matters when you ship frequently, localize several markets, or want agents to change listing copy in a reviewable diff instead of clicking around Connect. It pairs with asc CLI app and version commands so copyright and version identity stay correct before you push metadata.2.3kinstalls6Asc Testflight Orchestrationasc-testflight-orchestration is an agent skill for solo and indie iOS builders who already use the App Store Connect CLI (asc) and need repeatable TestFlight operations instead of clicking through App Store Connect. It walks through exporting the current TestFlight configuration to YAML (optionally including builds and testers), managing internal and external groups, adding and inviting testers, associating builds with groups, and maintaining localized What to Test copy. The skill emphasizes deterministic IDs, pagination for large tester lists, and pairing with an ID resolver skill when human-readable names are ambiguous. Use it when you are shipping a beta cohort, rotating builds across groups, or standardizing release notes for testers. It does not replace code signing or upload pipelines—it assumes builds exist and focuses on distribution orchestration on the Apple side.2.2kinstalls7Asc Id Resolverasc-id-resolver is a procedural guide for the asc App Store Connect CLI when downstream commands need opaque IDs. Solo iOS builders rarely memorize UUIDs for apps, builds, App Store versions, TestFlight groups, testers, pre-release versions, or review submissions; this skill standardizes the list and info patterns—filter by bundle ID or name, fetch latest builds, paginate long tenant catalogs, and set ASC_APP_ID for repeat workflows. It emphasizes deterministic sorting and full pagination so agents do not pick stale or missing identifiers. Use it as a prerequisite step in mobile release scripts, Codex or Cursor release checklists, and human-readable table exports for debugging ASC state before you ship or resubmit.2.2kinstalls8Asc Build Lifecycleasc build lifecycle is an agent skill for indie iOS developers who manage releases through the App Store Connect CLI rather than clicking through Xcode Organizer alone. It catalogs commands to discover the latest build for a version, compute the next safe build number, list recent uploads, and inspect processing status while Apple finishes ingestion. Distribution sections favor end-to-end publish invocations for TestFlight and App Store with wait, poll, and submit flags so agents can block until processing completes. Cleanup guidance covers dry-run expiration of builds older than a threshold and targeted expire on a single build id—useful for quota and audit hygiene. The skill explicitly notes that raw upload prepares operations while publish orchestrates the full flow, including long-running --timeout handling. Pair it with signing and archive skills when you are shipping mobile updates on a solo cadence.2.2kinstalls9Asc Signing Setupasc signing setup is an agent skill for indie iOS and macOS developers who manage App Store Connect signing through the asc CLI instead of clicking through Xcode panes alone. It prescribes a concrete sequence: authenticate, list or create bundle identifiers, attach capabilities (with optional settings payloads), create or renew distribution certificates using an existing CSR or generated key material, then wire provisioning profiles and encrypted sync when teammates need the same signing assets. The skill fits onboarding a brand-new app, rotating certificates before expiry, or standardizing how a two-person team shares keys safely. It assumes you already know your bundle ID and target platform and that Apple API credentials are configured via login or ASC_* environment variables. Outputs are operational—correct IDs, certs, and profiles ready for archive and upload—not product marketing. Pair it with your broader release checklist before you cut a production build.2.2kinstalls10Asc Ppp Pricingasc-ppp-pricing is an agent skill for indie and solo iOS builders who manage App Store Connect through the asc CLI and need consistent, territory-level prices instead of a single global tier. It teaches when to use high-level setup commands for new subscriptions or IAPs versus dedicated pricing summary, import, and schedule commands when you are only changing regional amounts. The workflow assumes you have already chosen a base territory (typically USA), a baseline price, and whether you are applying purchasing-power-parity math or a custom regional strategy. Preconditions are explicit: authenticated asc sessions, a resolved app identifier, and clarity on product references before running verified setup or schedule updates. The skill fits builders shipping subscription SaaS on mobile, consumable IAPs, or hybrid models who want procedural steps the agent can repeat without guessing ASC subcommand names. It does not replace App Store marketing or tax advice; it operationalizes localized price tables through commands your coding agent can execute in validate and build contexts, then revisit in grow when you tune regions after launch signals.2.2kinstalls11Asc Shots Pipelineasc-shots-pipeline is an agent skill for solo iOS builders who need repeatable App Store screenshots without manual simulator clicking. It wires Xcode CLI build and launch, AXe accessibility-driven UI steps from a JSON plan, Koubou-based framing through the asc CLI, and upload to App Store Connect. You start by authoring `.asc/shots.settings.json` (bundle id, project, scheme, simulator) and a capture plan, then run the documented pipeline to populate `./screenshots/raw` and `./screenshots/framed`. It fits when you are refreshing listing creatives for a release, localizing screenshot sets per locale, or agent-driving regression captures after UI changes. Scope today emphasizes build-run, plan capture, frame, and upload; device listing is first-class. Pair it with your existing asc authentication and App Store Connect project setup before upload.2kinstalls12Asc NotarizationAsc-notarization is a procedural agent skill for indie macOS developers who ship desktop apps outside the Mac App Store. It walks through preconditions—Xcode, asc authentication, a Developer ID Application certificate in the keychain, and a macOS-targeting Xcode project—then verification of signing identities with security find-identity, certificate creation on the Apple developer portal when needed, and remediation when macOS trust overrides break codesign or xcodebuild. The skill is invoked when you must archive, export, sign with Developer ID, and submit for Apple notarization so Gatekeeper accepts your build. It pairs command-line tooling (xcodebuild, security, asc) rather than manual Organizer clicks alone, which suits solo builders automating release scripts. Shelf it in Ship launch prep immediately before you publish a direct-download or update channel.2kinstalls13Asc Subscription Localizationasc-subscription-localization is an agent skill for solo and indie iOS builders who already use App Store Connect and the asc CLI. It walks you through resolving group and subscription IDs, listing current localizations, and applying the same display name (and description) across all supported App Store locales in bulk. That removes the repetitive manual work of opening each language in App Store Connect when you launch or update auto-renewable subscriptions and in-app purchases. Use it after subscriptions exist and auth is configured via asc auth login or ASC_* environment variables. The skill is intermediate complexity because you must know your app ID and subscription structure, but the steps are procedural shell commands with table output for verification. It fits mobile SaaS and subscription apps where consistent branding across regions matters for ASO and compliance with localized store listings.2kinstalls14Asc Localize Metadataasc-localize-metadata is an integration workflow for indie mobile developers who already ship through App Store Connect and want localized listing copy without manually copy-pasting dozens of locale fields. The skill centers on the asc CLI: authenticate, resolve your app and version identifiers explicitly, download existing metadata for a source language, run LLM translation for target locales, then upload translations back with typed commands rather than fragile UI scraping. It emphasizes operational safety—confirm subcommands with --help for your installed asc version, prefer long flags, default to JSON output for agent parsing, and avoid arbitrary "first row" ID guessing unless the user approves. Supported locales span major App Store markets (Arabic, European, Asian, and Americas variants). Use when someone asks to localize an app description, add languages to a listing, or keep what's new and subtitles synchronized across regions after a release.1.9kinstalls15Asc App Create Uiasc-app-create-ui is a workflow skill for indie iOS and Apple-platform builders who already use the App Store Connect CLI but hit the gap where app creation still lives only in the web UI. It chains API-backed preflight—bundle ID registration and duplicate checks—with opt-in Playwright or Cursor browser MCP automation while the user stays signed in and completes 2FA. The skill is narrowly scoped to standing up the app record, not metadata bulk edit or TestFlight, and it deliberately pauses for human confirmation before the irreversible Create click. Solo developers shipping their first App Store binary use it right after codegen and signing setup, when the bundle ID exists but Connect has no app row yet.1.9kinstalls16Asc Workflowasc workflow teaches agents to operate Rudrank’s App Store Connect CLI workflow subsystem for indie iOS/macOS shippers who want Fastlane-style lanes without leaving the repo. Workflows live at .asc/workflow.json, run trusted shell steps, and expose validate, list, dry-run, run, and resume primitives so beta and release trains stay auditable. Solo builders use it after ASC credentials and asc CLI are configured: validate structure, preview with --dry-run, pass BUILD_ID and GROUP_ID style parameters, then recover from partial failures via persisted run IDs. It fits small teams automating TestFlight uploads, metadata checks, and staged releases while keeping stdout JSON for CI parsers. Pair with other asc-* skills in the same bundle for auth and resource commands rather than one-off curl scripts.1.9kinstalls17Asc Crash Triageasc crash triage is an agent skill for indie iOS developers who manage TestFlight through Rudrankriyam’s asc CLI and need fast crash and feedback narratives instead of raw JSON dumps. Install it when testers report failures, when you are comparing builds, or when you need a concise picture of hangs, disk writes, launch diagnostics, and screenshot-accompanied feedback for a given app or build. The workflow starts by resolving the App Store Connect app identifier, then runs the appropriate asc testflight crashes or feedback list commands with limits, sorts, and filters, and finally translates results into a readable triage summary for your next fix list. It spans Ship when stabilizing pre-release builds and Operate when monitoring ongoing beta churn. Intermediate complexity assumes comfort with CLI flags and Apple build metadata. It is not a replacement for Xcode symbolicated crash logs on device-only repros—you still need local debugging—but it accelerates the connect-side inventory pass.1.6kinstalls18Asc Wall Submitasc-wall-submit teaches your agent the exact Wall of Apps flow in the App-Store-Connect-CLI repository: run from repo root, preview with --dry-run, then apply with --confirm so maintainers get a clean PR against docs/wall-of-apps.json. Solo iOS builders use it when they want showcase distribution for a shipped App Store app or a pre-release TestFlight build without guessing submission steps. The skill documents two input paths—numeric app ID for standard listings versus link plus name for beta—and insists you do not modify unrelated wall entries. Failures from bad inputs should be fixed and the CLI rerun rather than manual JSON surgery. It is narrow by design: marketing-style visibility for the ASC CLI community wall, not App Store Connect metadata editing or review submission.1.4kinstalls19Asc Revenuecat Catalog Syncasc-revenuecat-catalog-sync is an agent skill package for solo and indie iOS builders who monetize with subscriptions and in-app purchases across App Store Connect and RevenueCat. It walks through execution templates that mirror how you actually operate: pull the full ASC catalog with asc subscriptions and iap list commands, pull the RevenueCat side through MCP, and present a human-readable reconciliation before touching either system. When you need to bootstrap, it sequences group and subscription creation on ASC and then aligns RevenueCat entitlements and offerings under your project and iOS app. The skill fits anyone shipping a mobile SaaS who cannot afford silent catalog drift that breaks purchases or paywall logic. Use it during build when wiring billing, during validate when locking subscription SKUs, and again in operate when auditing production drift. It assumes you already have app and project identifiers and treats confirmation gates as non-negotiable for safe solo operations.1.3kinstalls20Asc Aso Auditasc-aso-audit packages the ASO rules reference that powers App Store Connect CLI auditing for solo iOS publishers who cannot afford wasted keyword characters or accidental duplication across title, subtitle, and the 100-character keyword field. It explains how Apple indexes metadata, why description still matters for conversion, and how to optimize word combinations across fields instead of repeating phrases. Builders invoke it when tightening listing copy before submission, recovering search combinations after a rebrand, or validating agency-prepared metadata against deterministic checks. The skill is checker-oriented: each documented rule ties to a test in the audit flow, so agents can flag comma spacing, duplicate tokens, and indexing misunderstandings early. It pairs naturally with App Store Connect automation skills in the same repo. Intermediate complexity—you should already have bundle metadata in ASC and basic ASO vocabulary. It does not replace human judgment on brand voice or creative screenshots, but it prevents costly structural mistakes that silently burn discoverability.1.2kinstalls21Asc Whats New Writerasc-whats-new-writer is a generator skill for indie iOS/macOS developers using the App Store Connect CLI (asc). It walks your agent through pulling or confirming canonical version metadata, picking the latest version folder, and drafting engaging What's New strings per locale. Input can be inferred from filtered git history since the last tag, from rough feature bullets, or from pasted notes—commits like CI-only or dependency bumps are stripped so customers see real product changes. The workflow references built-in release note guidelines and can optionally align promotional text with the same release. Preconditions include local metadata layout, authentication via asc auth login or ASC_* environment variables, and a chosen primary locale. It is aimed at repeatable ship-day copy, not replacing human review for sensitive launches.1.2kinstalls22Asc Screenshot Resizeasc screenshot resize is a focused agent skill for indie iOS and iPad developers preparing App Store Connect submissions. It tells your agent not to memorize screenshot matrices: always discover current accepted sizes with the asc CLI, then validate local folders against device types like IPHONE_65 or IPAD_PRO_3GEN_129 before upload. The workflow covers a practical macOS pitfall—Finder screenshots with narrow no-break spaces that break batch tools—and walks through inspect-and-resize steps using asc-owned data plus sips on macOS. It fits the Launch phase when your listing is otherwise ready but assets keep failing dimension or filename checks. The skill is procedural integration knowledge around rudrankriyam’s App Store Connect CLI skills repo, not a hosted resize service. Agents should run listed commands, confirm output tables, and iterate until validate passes.783installs