rorkai/app-store-connect-cli-skills
22 skills14.4k installs18.6k starsGitHub
Install
npx skills add https://github.com/rorkai/app-store-connect-cli-skillsSkills in this repo
1Asc Cli Usageasc-cli-usage teaches your agent how to operate the asc command-line tool against App Store Connect in this repository context. It emphasizes discovering commands with --help and asc search, validating endpoints with asc schema, and checking supported workflows via asc capabilities before scripting releases. Documentation and automation should prefer view and edit over legacy get aliases for reads and availability updates. Solo iOS builders use it when asked to list builds, inspect apps or versions, adjust pricing availability, or design submit-for-review flows without guessing flags. The skill is integration-oriented: correct CLI shape reduces failed submissions and brittle CI steps. Pair it with your Apple API keys and app IDs in the environment your agent already uses.713installs2Asc Metadata Syncasc-metadata-sync is an agent skill for solo iOS builders maintaining App Store listings with the asc CLI. It steers agents toward the canonical asc metadata workflow for app-info and version localization fields instead of ad-hoc fastlane edits unless the user specifically needs .strings files or legacy fastlane-format metadata. The documented pull command syncs a version and platform into ./metadata, with guidance to resolve app-info IDs when multiple records exist. Local edits happen in metadata/app-info/<locale>.json (name, subtitle, privacy URLs/text) and metadata/version/<version>/<locale>.json (description, keywords, marketing and support URLs, promotional text, whatsNew). Copyright is updated through asc versions update, keeping version-level legal fields separate from localizations. Use it when updating metadata, localizations, keywords, or migrating legacy fastlane trees—typically in Launch prep alongside other asc app-store-connect skills.704installs3Asc Release Flowasc-release-flow is an agent skill for solo and indie iOS builders who ship with the App Store Connect CLI (asc) instead of clicking through every panel blind. It starts with the question developers actually ask—can this build be submitted right now—and forces a structured response: readiness verdict, enumerated blockers, whether each blocker needs the public API, a web session workaround, or human fallback, then the single next command to run. The workflow assumes identifiers and auth are resolved up front and that canonical metadata may live under ./metadata for staging. It spans validation, attaching builds, review submission, first-time availability, subscriptions, in-app purchases, Game Center items, and App Privacy publish state, reflecting real App Store friction where not everything is API-complete. Use it in Ship when you are closing a release candidate; it pairs with other asc skills for discovery and metadata edits. Treat experimental asc web commands as escape hatches only when the skill flags a web-session-fixable gap.694installs4Asc Aso Auditasc-aso-audit is a checker skill for solo iOS builders using App Store Connect workflows to validate listing metadata against documented ASO rules. It maps indexing behavior—what Apple search indexes versus what only affects conversion—and enforces practical keyword-field hygiene such as comma formatting, deduplication against title and subtitle, and cross-field query combinations. Use it at Launch before submission or when refreshing seasonal copy so you do not waste the 100-character keyword budget or repeat indexed terms. It is designed to pair with App Store Connect CLI skills in the same repo rather than replacing human judgment on brand voice. Expect rule-based audit output aligned to the skill’s reference index, not guaranteed ranking outcomes.685installs5Asc Localize Metadataasc localize metadata is an agent skill for indie iOS builders who already use App Store Connect and the asc CLI but dread manually copying listing text into dozens of locales. It standardizes discovery with `--help` on localizations and apps info commands, pulls English or another source locale, translates fields with an LLM, and pushes results back through upload flows while preferring explicit flags and JSON for agent reliability. Preconditions are clear: authenticated asc session, known app ID, and at least one populated locale so translations are syncs—not greenfield invention. The workflow fits launch-week ASO expansion when you are adding languages for a release, refreshing What’s New globally, or keeping subtitle and keyword sets aligned after a positioning change. It is not a replacement for human legal or marketing review in regulated markets, but it collapses repetitive CLI choreography so one builder can ship multilingual listings faster.678installs6Asc 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 verifying that a build is VALID, running the current `asc validate` readiness command (not deprecated preflight shortcuts), handling encryption declarations when needed, and monitoring review after submission. Preconditions assume auth, resolved app/version/build IDs, and completed metadata, screenshots, pricing, and availability. The skill is aimed at reducing preventable review failures and giving automatable pass/fail signals when you add `--strict`. It fits anyone already on the asc toolchain who needs a repeatable submission-health ritual rather than ad-hoc command memory.676installs7Asc Id ResolverAsc Id Resolver is a reference skill for solo iOS builders who automate App Store Connect with the asc CLI but hate copying UUIDs from the web UI. It catalogs the exact list and info commands to turn human-friendly app names, bundle IDs, version strings, and TestFlight group labels into the IDs downstream asc subcommands require. Coverage spans apps, builds, store versions, TestFlight groups and testers, pre-release versions, and review submissions, with tips for pagination, sorting, and setting ASC_APP_ID as a default. It assumes you already use asc in terminal workflows during release week—not a replacement for Apple's portal when you only need one-click manual submits. Following the guardrails reduces missed records on large accounts and makes CI or agent-driven release scripts repeatable.671installs8Asc Signing Setupasc-signing-setup is an agent skill for solo and indie builders shipping Apple apps who already use Rork’s asc CLI instead of clicking through App Store Connect for every cert rotation. It walks through finding or creating bundle identifiers, enabling capabilities with the correct settings payloads, issuing IOS_DISTRIBUTION (or analogous) certificates, and tying those assets to provisioning profiles so Xcode and CI can sign consistently. The skill fits when you onboard a new bundle ID, renew expired distribution certs, or need a repeatable path to share keys and profiles without leaking private material in chat. It assumes authentication is configured via asc auth login or ASC_* environment variables and that you know your target platform. Compared with ad-hoc Xcode-only setup, it favors scriptable, reviewable commands your coding agent can run and log—while you still own Apple Developer portal policy and secret handling.658installs9Asc Screenshot Resizeasc screenshot resize is an agent skill for solo iOS builders preparing App Store Connect screenshot sets without guessing pixel matrices. Apple changes accepted display sizes over time; this skill insists you discover current requirements from the asc CLI first, then resize and validate local PNGs with macOS sips. It walks through filename sanitization—hidden Unicode spaces break batch tools—inspection of dimensions, anchored device types such as IPHONE_65 for common 6.5-inch iPhone sets and IPAD_PRO_3GEN_129 for large iPad sets, and validate commands per folder before upload. Install it when you are fixing rejected screenshots, localizing store images, or generating a new device family set. You need asc installed and authenticated, macOS for sips, and screenshot masters at reasonable resolution. The skill is procedural packaging around the Rork asc toolchain, not a hosted resize API.653installs10Asc Xcode Buildasc-xcode-build is an agent skill for solo iOS, tvOS, and visionOS builders who need a dependable path from Xcode source to an upload-ready IPA or PKG. It steers agents toward the App Store Connect CLI helpers—viewing and editing marketing version and build numbers, bumping semver or build counters, resolving the next safe build number against remote ASC records, then archiving and exporting with `asc xcode` when those commands fit the repo layout. The readme lists hard preconditions: installed Xcode command line tools, workable signing, and configured ASC authentication whenever upload or remote build lookup is required. Use it when you are creating distributable binaries for App Store Connect rather than debugging Swift compile errors or designing store listing copy. The outcome is a signed export aligned with ASC expectations, with build numbers that survive automated review.652installs11Asc Build Lifecycleasc-build-lifecycle teaches solo and indie mobile builders how to operate App Store Connect builds through the asc CLI: finding the right artifact, waiting on Apple processing, shipping to testers or production, and cleaning up old binaries. It fits builders who already have an IPA and APP_ID and need repeatable commands instead of clicking through Connect. Typical flows start with asc builds info using --latest or a version filter, asc builds next-build-number to avoid collisions, and list with sort on uploadedDate for a short audit trail. Distribution prefers wrapped publish commands with polling flags for long processing. Cleanup uses expire-all with dry-run first, then confirm, which matters when storage and compliance policies stack up across many betas. Intermediate complexity reflects Apple identifiers, platform enums, and confirm-gated destructive steps. Pair it with signing and archive skills earlier in the pipeline; this skill assumes binaries exist and focuses on lifecycle after upload.651installs12Asc Whats New WriterASC What's New Writer is a template-style agent skill for indie iOS and mobile builders who ship through App Store Connect and need store-facing release notes that actually convert. It encodes editorial law: lead with the single most impactful change in roughly 170 characters, then organize remaining bullets under New, Improved, and Fixed only when each section has real content. The skill pushes benefit language over internal engineering jargon and flags common wastes of space such as version numbers in headings or empty bug-fix-and-improvements placeholders. Use it when you are packaging a release for submission or refreshing listing copy after a meaningful update—not for full app descriptions, keyword research, or Android Play Console listings unless you adapt the rules manually.650installs13Asc Shots Pipelineasc-shots-pipeline is an agent-oriented workflow for solo iOS developers who dread manually clicking through simulators for every App Store screenshot size. Prism places it on Launch → ASO because the payoff is framed assets uploaded through asc, even though you touch Build tooling (Xcode project, scheme, bundle id) along the way. The skill walks an ordered pipeline: create shots.settings.json, maintain a screenshots.json AXe plan, build and run on a simulator UDID, capture raw shots, run Koubou-based framing, then upload with asc screenshots upload. It encodes opinionated paths and versioning so agents do not improvise directory layouts each run. Use it when refreshing screenshots after a UI overhaul, localizing store listings, or batch-producing device frames before submission. It is narrower than full CI release management—it optimizes the screenshot slice of launch prep. Expect experimental CLI surfaces; verify asc version and Koubou pin before trusting unattended automation.648installs14Asc Workflowasc workflow teaches solo iOS builders how to run lane-style App Store Connect automation through the asc CLI using repo-local `.asc/workflow.json` files. You validate structure, discover workflows, preview with dry-run, execute with build and group identifiers, and resume interrupted runs using the run ID from JSON results—critical when TestFlight or release steps fail mid-pipeline. The skill stresses verifying flags via asc workflow --help on each subcommand because CLI surfaces evolve. Machine-readable stdout plus streamed stderr makes it agent-friendly for Cursor or Claude Code driving ASC from the terminal. Skip ad-hoc shell scripts when you need audited, resumable, trusted-command workflows tied to Apple’s release process.645installs15Asc Ppp PricingASC PPP Pricing is a procedural skill for the App Store Connect CLI (asc) that walks solo mobile builders through territory-specific subscription and in-app purchase pricing. It favors high-level commands—subscriptions setup, subscriptions pricing, iap setup, iap pricing summary, and pricing schedules—so you implement purchasing-power-parity or custom regional ladders without clicking through every storefront in the web UI. Preconditions include authenticated asc access, an explicit app id, a USA (or chosen) base price, and territory IDs from the CLI. Use it when validating monetization before ship and when adjusting live prices by country. It is narrowly focused on Apple monetization surfaces, not Google Play or Stripe web billing.641installs16Asc Crash Triageasc-crash-triage teaches your coding agent to use the App Store Connect CLI (asc) to pull TestFlight crash reports, beta feedback, and related diagnostics into readable summaries for solo iOS builders who do not want to click through App Store Connect for every regression. The skill prescribes a short workflow: confirm the app identifier, run the right asc testflight crashes or feedback list invocation with limits and filters, then translate JSON into action-oriented narrative. It supports narrowing by build, device model, OS version, and sorting by created date so you can compare a bad build against a known good one. Use it when testers report crashes, when launch hangs spike, or when you need a concise crash digest before a TestFlight promotion or App Store submission. It assumes asc is installed and authenticated; it does not replace symbolic crash log symbolication workflows you may still do in Xcode.639installs17Asc Testflight Orchestrationasc TestFlight orchestration is a procedural agent skill for indie iOS developers who manage App Store Connect through the asc CLI instead of clicking through web consoles. It walks through exporting the current TestFlight configuration to YAML (optionally including builds and testers), maintaining beta groups, inviting emails, listing large rosters with pagination, attaching build IDs to groups, and writing localized What to Test copy. The workflow assumes you already have an app identifier and build identifiers from your CI or archive step; it favors explicit IDs for repeatable automation and notes when to pair with the ID resolver skill. Solo builders use it when each release means new tester cohorts, refreshed instructions, or scripted group membership changes during ship week.637installs18Asc App Create Uiasc-app-create-ui is an agent skill for solo and indie builders shipping iOS, macOS, tvOS, or visionOS apps who already use App Store Connect CLI but hit the wall where Apple exposes no API to create a new app. It documents a guarded workflow: verify and register the bundle ID with asc, confirm no duplicate app, then automate the web New App form while you stay signed in. The skill assumes a browser automation stack is available, all required fields are decided up front, and you accept human confirmation before the final Create click. It fits launch and ASO prep when the catalog record must exist before versioning, TestFlight, or store listing tasks. Prism tags it as phase-specific launch/aso because it solves one distribution bottleneck rather than general product build or growth analytics.636installs19Asc Subscription Localizationasc-subscription-localization is an agent skill for indie iOS builders who already use Apple’s asc CLI and need every subscription or in-app purchase name translated consistently across App Store locales. It replaces hours of clicking each language in App Store Connect with a repeatable ID-resolution and bulk-localization workflow: find the app, list subscription groups and subscriptions, inspect current localizations, then push display names and descriptions at scale. The skill is narrowly focused on metadata localization for monetization surfaces—assumes groups and products already exist and that you have ASC_APP_ID or --app handy. It pairs naturally with launch checklists when you ship a paywall update, align pricing tiers across regions, or fix embarrassing English-only subscription titles before a marketing push.632installs20Asc Notarizationasc-notarization is a procedural agent skill for indie macOS developers distributing outside the App Store. It walks through preflight signing identity checks, resolving common keychain trust failures, archiving with xcodebuild, and notarizing through the asc CLI once App Store Connect authentication is configured. The audience is a solo builder who already has an Xcode macOS target and a Developer ID Application certificate but needs a repeatable agent-guided ritual instead of tribal Xcode UI knowledge. Use it at the end of the Ship phase when binaries must be stapled and trusted by Gatekeeper on customer machines. It does not replace App Store submission flows or iOS signing; it complements other asc skills for listing metadata and Connect automation.621installs21Asc Revenuecat Catalog Syncasc-revenuecat-catalog-sync is an agent skill package that teaches realistic workflows for keeping Apple App Store Connect subscription and in-app purchase catalogs aligned with RevenueCat. Solo iOS builders use it when monthly and annual products, entitlement identifiers, or offerings have drifted between the store and RevenueCat. Templates cover a read-only reconciliation: list ASC subscription groups, IAP, and group subscriptions with JSON pagination, then list RevenueCat apps, products, entitlements, offerings, and packages to produce a structured diff. A second path bootstraps missing ASC resources with asc create commands and syncs them into a named RevenueCat project under the correct iOS app. The skill expects you to audit first, present gaps, and confirm before destructive or create operations. It pairs store-native identifiers with RevenueCat’s subscription backend so indie apps ship monetization without hand-maintaining two spreadsheets.616installs22Asc Wall Submitasc wall submit is a narrow workflow skill for developers using the App-Store-Connect-CLI repository who want to add or refresh an entry on the project’s Wall of Apps without hand-editing JSON. It encodes the exact command sequence: run from repo root, preview with --dry-run for either --app with a numeric App Store id or --link with a TestFlight join URL and --name, then apply with --confirm after you accept the generated PR plan. The skill emphasizes guardrails—fix invalid inputs and rerun, keep changes scoped to docs/wall-of-apps.json, and stay on the PR-based intake path unless maintainers define otherwise. For solo builders promoting a shipped or beta iOS app in a curated community wall, this removes ambiguity about flags, confirmation, and what files may change. It assumes you already have App Store Connect identifiers or a public TestFlight link ready to paste.596installs