rudrankriyam/app-store-connect-cli-skills
23 skills46.3k installs21.5k 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 for designing and running the asc App Store Connect CLI with disciplined discovery and automation-friendly flags. Command discovery starts with asc help on groups, asc search for workflow lookup, asc schema for bundled API endpoint inspection, and asc capabilities for coverage status across release workflows. Canonical verbs prefer view over legacy get aliases for read-only commands and edit for availability updates, reserving set only where help still documents it as canonical. Flag conventions require explicit long flags, confirm on destructive operations, and paginate when users need all pages. Output defaults are TTY-aware table versus json, with pretty valid only for JSON. Authentication prefers keychain login via asc auth login with ASC key env fallbacks plus ASC_APP_ID defaults. Apple Ads commands use separate asc ads auth, ASC_ADS variables, org resolution via acls, and JSON file payloads for bulk endpoints. Timeout env vars ASC_TIMEOUT and ASC_UPLOAD_TIMEOUT control request and upload limits. Developers reach for it when automating builds, versions, pricing availability, or review submission through asc.2.8kinstalls2Asc Release Flowasc-release-flow is an agent skill for answering whether an iOS app can be submitted now and executing the current App Store Connect CLI workflow with asc. It starts by resolving APP_ID, version, VERSION_ID, and BUILD_ID, confirming auth via asc auth login or ASC environment variables, and separating API-fixable blockers from web-session or manual fixes. Readiness begins with asc validate for the target version, optional strict mode, and product checks such as asc validate iap and asc validate subscriptions when selling digital goods. Staging uses asc release stage with metadata directories or copy-metadata-from, dry-run planning, then --confirm mutations. Submission paths include asc review submit for prepared versions, asc publish appstore for upload-plus-submit flows, and status monitoring via asc status and asc submit status. First-time blockers cover initial pricing availability bootstrap, subscription attachment for first review, IAP review screenshots, Game Center version items, and App Privacy publish steps through documented asc web escape hatches when the public API is insufficient.2.7kinstalls3Asc Submission Healthasc-submission-health is the App Store Connect CLI skill for reducing review failures and tracking submission state end to end. It mandates asc validate as the canonical readiness check, explicitly deprecating legacy submit-preflight and submit-create shortcuts. The pre-submission checklist walks build processing state, strict validation mode, encryption declarations and exempt plist flows, content rights, version metadata pull validate and push, app info localizations, screenshot validation, digital goods IAP and subscription checks, and App Privacy advisory gaps with optional web-session flows. Submit paths cover asc review submit for prepared versions, asc publish appstore for upload-plus-submit, multi-item review submissions for Game Center, and web-session IAP attachment for Apple web-only gaps. Monitor commands poll asc status, submit status, and review submissions-list. Cancel and retry guidance addresses invalid version state, export compliance, and multiple app-info conflicts. Notes flag that App Privacy publish state is not fully verifiable through the public API alone.2.6kinstalls4Asc Xcode Buildasc-xcode-build guides agents through producing App Store-ready artifacts with asc xcode archive and export instead of raw xcodebuild recipes when they fit. Preconditions cover Xcode, command line tools, signing identities, and App Store Connect auth. Version management uses asc xcode version view, edit, and bump, with asc builds next-build-number to avoid CFBundleVersion rejects before editing build numbers. The preferred iOS flow archives with workspace or project flags, exports with ExportOptions.plist, optionally waits for direct upload processing, then uploads via asc builds upload or publishes to TestFlight or the App Store with asc publish. macOS App Store flow archives for generic/platform=macOS, exports PKG via xcodebuild when needed, and uploads with explicit version and build-number flags. Raw xcodebuild is a fallback only when asc helpers lack project-specific options, with extra flags passed through --xcodebuild-flag. Troubleshooting covers missing provisioning profiles, low build numbers, and macOS icon asset requirements. Cross-links asc-submission-health for post-upload readiness.2.6kinstalls5Asc Metadata Syncasc metadata sync keeps App Store metadata aligned with App Store Connect using the canonical asc metadata workflow for app-info and version localization fields. Pull writes metadata/app-info locale JSON for name, subtitle, and privacy URLs plus metadata/version locale JSON for description, keywords, marketing URL, promotional text, support URL, and whatsNew. Validate runs before any remote write, with an optional subscription-app Terms of Use heuristic. Push and apply support dry-run previews before applying changes. Keyword-only workflows use metadata keywords diff, apply, import, and sync commands. Quick field updates use apps info edit with explicit version-id or version plus platform selectors. Lower-level asc localizations commands handle strings files when requested, and asc migrate supports legacy fastlane-format trees only. Character limits cover name thirty, subtitle thirty, keywords one hundred, and description four thousand characters.2.5kinstalls6Asc Id ResolverThe asc-id-resolver skill maps human-friendly App Store Connect names to IDs required by other asc commands. App IDs are found by bundle ID or name via asc apps list, with paginate for full inventories and ASC_APP_ID for defaults. Build IDs come from asc builds info with latest and version filters or recent asc builds list sorted by upload date. Version, TestFlight group, tester, pre-release, and review submission IDs each have dedicated list commands with paginate recommended to avoid missing entries. Output tips note JSON default, pretty for debug, and table or markdown for human viewing. Guardrails stress paginate on lists and sort where available for deterministic results. Teams invoke this skill before TestFlight orchestration, build lifecycle, or publish flows whenever commands need stable IDs instead of display names. It complements sibling asc skills by preventing failed operations caused by ambiguous app or group labels across large accounts.2.4kinstalls7Asc Testflight OrchestrationThe asc-testflight-orchestration skill guides TestFlight beta distribution with the asc CLI for groups, testers, builds, and What to Test localizations. It starts by exporting current config to YAML with optional builds and testers included, then documents listing and creating groups, adding and inviting testers by email, and attaching or removing builds from groups by ID. What to Test notes are created or updated per build locale with whats-new text. Commands emphasize paginate for large lists and prefer stable IDs over names, pointing to the asc-id-resolver skill when human-friendly names must be mapped. Distribution examples use asc builds add-groups and remove-groups with confirm flags. The skill targets teams rolling out betas who need repeatable CLI workflows instead of manual App Store Connect UI steps. It assumes an APP_ID is known or resolvable and that build and group IDs are used for deterministic attach and detach operations across environments.2.4kinstalls8Asc Build LifecycleThe asc-build-lifecycle skill manages App Store Connect build state, processing waits, retention, and publish flows with the asc CLI. Finding builds uses asc builds info with latest and version platform filters, asc builds next-build-number for safe increments, and sorted asc builds list for recent uploads. Processing state is inspected per build-id before distribution. End-to-end publish prefers asc publish testflight with ipa, group, and wait flags or asc publish appstore with version, wait, submit, and confirm for store submission. Cleanup supports expire-all with older-than dry-run previews and confirmed expiration, plus single build expire by id. Notes clarify asc builds upload only prepares upload operations while asc publish handles full pipelines, and long processing should use wait, poll-interval, and timeout options. Teams invoke it when waiting on build processing, choosing build numbers, pushing IPAs to TestFlight or App Store, or pruning stale binaries to manage account retention limits.2.4kinstalls9Asc Ppp PricingThe asc-ppp-pricing skill implements localized App Store pricing across territories using the asc CLI for subscriptions and in-app purchases. Preconditions require asc auth, a base territory usually USA, and territory IDs from asc pricing territories list. New products bootstrap with asc subscriptions setup or asc iap setup, creating localization, initial price, and availability in one verified flow. Bulk PPP updates prefer subscriptions pricing prices import with a territory and price CSV, always dry-run first, then apply and re-check asc subscriptions pricing summary per territory. One-off overrides use prices set with optional start-date and preserved flags. IAP changes use asc iap pricing summary, price-points list, and schedules create for manual or tier-based updates. Strategy guidance covers base-territory-first rollout, tiered regional discounts, and spreadsheet-driven imports with post-apply summary verification. Notes warn that canonical asc subscriptions pricing and asc iap pricing families supersede older paths and storefront propagation may lag after changes.2.4kinstalls10Asc Signing Setupasc-signing-setup walks through App Store Connect signing asset creation and team sharing using the asc CLI. Preconditions require configured auth, known bundle identifier, target platform, and a CSR file or inline --generate-csr. The workflow creates or lists bundle IDs, adds capabilities like ICLOUD with optional settings JSON, creates IOS_DISTRIBUTION certificates with CSR generation, builds IOS_APP_STORE or development profiles with device IDs when needed, downloads and inspects profiles locally, and installs them via profiles local install. Rotation guidance revokes old certificates, audits profiles comparing expirationDate against profileState ACTIVE quirks, deletes stale profiles, and cleans expired local Xcode profiles with dry-run first. asc signing sync push and pull provide encrypted git-backed certificate storage similar to fastlane match, using ASC_MATCH_PASSWORD fallback. Notes remind users that profile inspect and local commands operate on disk, not API resources, and that pull writes files without automatic keychain import.2.3kinstalls11Asc Shots PipelineThe asc-shots-pipeline skill orchestrates agent-driven iOS screenshot automation for App Store Connect. Pipeline stages cover settings JSON at .asc/shots.settings.json, xcodebuild and simctl build-run on simulators, AXe or asc screenshots run plan capture, Koubou 0.18.1 framing via asc screenshots frame, and upload or plan-apply flows to App Store Connect. Defaults include raw screenshots in ./screenshots/raw and framed output in ./screenshots/framed with iphone-air as the default frame device. Multi-locale capture uses per-simulator UDID locale defaults rather than unreliable launch -e flags, with parallel capture and framing scripts. Review steps include review-generate, review-open, and review-approve before plan and apply guardrailed uploads. Agents confirm flags with --help, prefer JSON output, verify screenshot files exist, and treat local screenshot automation as experimental. Framing requires pip install koubou==0.18.1 and kou setup-frames when device frames are missing.2.2kinstalls12Asc Notarizationasc-notarization guides agents through macOS app notarization for distribution outside the Mac App Store using xcodebuild archive and export plus the asc CLI. Preconditions include Xcode command line tools, asc auth login or ASC env vars, a Developer ID Application certificate in the keychain, and a macOS-targeting Xcode scheme. The workflow covers preflight identity verification with security find-identity, fixing broken trust settings that cause errSecInternalComponent, validating the signing chain through Developer ID Application to Apple Root CA, archiving with xcodebuild, exporting with a Developer ID ExportOptions plist, submitting the app for notarization via asc, stapling tickets, and verifying gatekeeper acceptance. It documents common failure modes around custom trust overrides, missing certificates, and runtime hardening options. Use when shipping signed macOS binaries to customers who download directly rather than through the App Store.2.1kinstalls13Asc Subscription LocalizationUse this skill to bulk create or bulk update display names and descriptions for subscriptions subscription groups and in app purchases across all App Store Connect locales This eliminates the tedious manual process of clicking through each language in App Store Connect to set the same display name Preconditions Auth configured asc auth login or ASC_ env vars Know your app ID ASC_APP_ID or app Subscription groups and subscriptions already exist These are the locales supported by App Store Connect for subscription and IAP localizations ar SA ca cs da de DE el en AU en CA en GB en US es ES es MX fi fr CA fr FR he hi hr hu id it ja ko ms nl NL no pl pt BR pt PT ro ru sk sv th tr uk vi zh Hans zh Hant2.1kinstalls14Asc Localize MetadataUse this skill to pull English or any source locale App Store metadata translate it with LLM and push translations back to App Store Connect all automated Command discovery and output conventions Always confirm flags with help for the exact asc version asc localizations help asc localizations download help asc localizations upload help asc apps info edit help Prefer explicit long flags app version version id type app info Default output is JSON use output table only for human verification steps Prefer deterministic ID based operations Do not pick the first row via head 1 unless the user explicitly agrees Preconditions Auth configured asc auth login or ASC_ env vars Know your app ID asc apps list to find it At least one locale typically en US already has metadata in App Store Connect App Store Connect locales for version and app info localizations ar SA ca cs da de DE el en AU en CA en GB en US es ES es MX fi fr CA fr FR he2.1kinstalls15Asc App Create UiUse this skill to create a new App Store Connect app by driving the web UI This is opt in local only automation that requires the user to be signed in Preconditions A browser automation tool is available Playwright Cursor browser MCP or equivalent User is signed in to App Store Connect or can complete login 2FA The bundle ID must already be registered in the Apple Developer portal Required inputs are known app name max 30 characters bundle ID must exist and be unused by another app SKU platform iOS macOS tvOS visionOS primary language user access Full Access or Limited Access Safety Guardrails Never export or store cookies Use a visible browser session only Pause for a final confirmation before clicking Create for standalone scripts Do not retry the Create action automatically on failure 1 Preflight register bundle ID and verify no existing app bash Register the bundle ID via public API if not already registered asc bundle ids create identifier com example app name My App platform2.1kinstalls16Asc WorkflowUse this skill when you need lane style automation inside the CLI using asc workflow validate asc workflow list asc workflow run Workflows are repo local automation files They run trusted shell commands stream step output to stderr and keep stdout as machine readable JSON bash asc workflow help asc workflow validate help asc workflow list help asc workflow run help 1 Author asc workflow json 2 Validate structure and references The asc workflow agent skill provides documented workflows prerequisites triggers and safety guidance from its SKILL md source Agents load it when user requests match the description and follow step by step instructions without inventing capabilities It integrates with standard agent tooling for the tasks inputs outputs and failure modes described in the repository documentation2kinstalls17Asc Crash TriageThe asc-crash-triage skill Triage TestFlight crashes, beta feedback, and performance diagnostics using asc. Use when the user asks about TF crashes, TestFlight crash reports, beta tester feedback, app hangs, disk writes, launch diagnostics, or wants a crash summary for a build or app. It covers resolve the app ID if not provided use asc apps list .. Key workflows include fetch data with the appropriate command.. 1. Resolve the app ID if not provided use asc apps list . 2. Fetch data with the appropriate command. 3. Parse JSON output and present a human-readable summary. Developers invoke asc-crash-triage when the task matches the triggers and reference files in SKILL.md for grounded, stepwise execution. Reference files and progressive disclosure keep context focused while preserving concrete commands, configuration fields, and validation checks copied from the upstream documentation.1.7kinstalls18Asc Wall SubmitThe asc-wall-submit skill guides adding or updating Wall of Apps entries via the built-in asc apps wall submit CLI flow. Required inputs support standard App Store flow with an app ID or manual pre-release flow with link plus name. Workflow runs commands from the App-Store-Connect-CLI repository root, gathers app metadata, and executes the wall submission steps users request when they say submit to wall of apps or add my app to the wall. Agents confirm which input path applies before running submit. Use for Wall of Apps publicity listings tied to the asc CLI ecosystem. Uses asc apps wall submit from App-Store-Connect-CLI repo root Standard flow: app ID; manual flow: link plus name for pre-release apps Add or update existing Wall of Apps entries via built-in CLI Triggered by wall of apps, add to wall, or asc wall submit requests Confirms input path before executing submission workflow asc-wall-submit adds or updates Wall of Apps entries via asc apps wall submit CLI Submitted or updated Wall of Apps entry using the1.6kinstalls19Asc Revenuecat Catalog SyncThis skill aligns App Store Connect (ASC) subscription and IAP catalogs with RevenueCat's product, entitlement, and offering data using asc CLI and RevenueCat MCP server. Developers use it to bootstrap RevenueCat from an existing ASC catalog, audit drift before release, or create missing ASC items and map them deterministically by product identifier. The workflow starts in read-only audit mode, builds a diff showing missing or conflicting items across systems, then executes approved changes in order: ASC groups/subscriptions/IAPs, RevenueCat apps/products, entitlements/attachments, and offerings/packages. It requires ASC and RevenueCat authentication, uses store_identifier as the canonical cross-system key, and reports all operations with final reconciliation counts.1.5kinstalls20Asc Aso Auditasc-aso-audit is an App Store Connect CLI companion skill that automatically checks an iOS listing against Apple's ASO rules before you submit. It validates which fields are search-indexed—title, subtitle, and the 100-character keyword field—versus fields that drive conversion only, such as description and promotional text. The skill also flags screenshot caption keyword usage, reflecting Apple's June 2025 OCR indexing update for caption text. Developers reach for asc-aso-audit when a build is ready for review and metadata has changed, or when organic search traffic underperforms after a listing update. It pairs with the app-store-connect-cli workflow to run rule-linked checks rather than manual checklist review.1.4kinstalls21Asc Whats New Writerasc-whats-new-writer is a skill from rudrankriyam/app-store-connect-cli-skills that turns git commits, bullet lists, or free-form notes into polished, localized App Store What's New release notes following Apple's tone and metadata conventions. It expects metadata pulled locally via asc metadata pull with app ID, version, and ./metadata directory, or manually supplied keywords when pull is unavailable. Authentication uses asc auth login or ASC_* environment variables for upload-ready workflows, with en-US as the default primary locale unless overridden. Developers reach for asc-whats-new-writer when preparing App Store Connect submissions, refreshing release notes across locales, or pairing What's New text with promotional text updates without hand-writing Apple-style copy for every language.1.3kinstalls22Asc Screenshot Resizeasc-screenshot-resize is a Claude Code skill from rudrankriyam/app-store-connect-cli-skills that prepares App Store Connect screenshots without hard-coded dimension tables. The skill discovers current accepted sizes via `asc screenshots sizes --output table` and `asc screenshots sizes --all --output table`, then resizes and validates local assets with macOS `sips` and `asc screenshots validate --path` before upload. Developers use asc-screenshot-resize when fixing rejected screenshots or batch-preparing iPhone and iPad assets for submission. Output includes correctly dimensioned PNG sets and validation reports aligned to the live asc size matrix.899installs23Asc Apple Adsasc-apple-ads is a Claude Code skill for ai & agent building. It helps solo builders move faster with AI-assisted development.91installs