rudrankriyam/asc-skills
22 skills21k installs18.6k starsGitHub
Install
npx skills add https://github.com/rudrankriyam/asc-skillsSkills in this repo
1Asc Cli Usageasc-cli-usage documents how solo iOS publishers should drive App Store Connect through the asc CLI without guessing command paths. It emphasizes discovery: layered --help, asc search with table or markdown output, and asc schema to read bundled endpoint shapes before you script releases. The capabilities command explains what is CLI-supported versus web-only or limited by public API, which saves hours when a workflow is not automatable. Canonical read/write verbs—view and edit—replace legacy get aliases so docs and CI stay consistent. Auth, flags, and pagination patterns keep long build lists and version lookups reliable in agents and shells. Use it when designing release automation, answering where to upload a build, or mapping pricing and availability edits during launch prep.1.1kinstalls2Asc Release Flowasc-release-flow is a readiness-first workflow skill for solo and indie mobile builders who submit with Apple’s App Store Connect via the asc CLI. It is meant when you need a direct answer to whether the app can be submitted right now—not a vague checklist—and when you want the agent to drive validation, metadata staging, review details, and related store objects with commands you can run immediately. The skill forces early resolution of app identifiers, builds, and authentication, and it separates fixes you can make through the API from flows that still need a web session or manual App Store Connect work, which is how real release weeks actually break down. By naming blockers before suggesting fixes, it reduces thrash between engineering, metadata, and compliance tasks such as encryption declarations, content rights, IAP readiness, and App Privacy publish state. It fits builders shipping native apps who already use asc and want agent-guided release operations instead of ad-hoc forum threads.1.1kinstalls3Asc Metadata Syncasc metadata sync is an agent skill for keeping iOS App Store Connect metadata aligned with a repo-backed canonical workflow using the asc CLI. It suits solo and indie mobile builders who ship versioned releases and need repeatable pulls of names, subtitles, descriptions, keywords, URLs, and whats-new text across locales without hand-editing Connect for every copy change. Use it when updating listings before submission, refreshing keywords for Launch ASO, or migrating off legacy fastlane metadata folders. The skill prioritizes `asc metadata pull` and JSON edits under predictable directories, then apply/validate steps consistent with current asc commands; lower-level localization or migrate utilities are secondary when users need `.strings` compatibility. Correct metadata sync reduces submission surprises, keeps marketing and support URLs consistent per locale, and gives agents a file-based source of truth that diffs cleanly in git.1.1kinstalls4Asc Id Resolverasc-id-resolver is an agent skill for indie iOS builders who drive App Store Connect through the asc CLI but think in human names—app titles, bundle IDs, version strings—not opaque Apple IDs. It catalogs the exact list and info commands to resolve apps, builds, App Store versions, TestFlight groups and testers, pre-release versions, and review submission records, plus how to set ASC_APP_ID and read results as JSON, tables, or markdown. Use it whenever another asc skill or command fails because it needs APP_ID, build ID, or TestFlight identifiers you only know by label. The skill is narrow and procedural: no API theory, just repeatable lookups with pagination and sorting so you do not miss entities on large accounts. It pairs naturally with other rudrankriyam asc-skills that assume IDs are already in hand.1kinstalls5Asc Submission Healthasc-submission-health guides solo and indie iOS builders through App Store Connect submission hygiene using current asc CLI patterns. Before you ship a version to review, you confirm the build reached a valid processing state, run asc validate against the app and semantic version (or version ID), and optionally fail automation on warnings with strict mode. The skill stresses that asc validate is the canonical readiness check and explicitly deprecates older submit-preflight and submit-create shortcuts that cause drift in docs and CI. It also covers encryption declaration listing when export compliance is not exempt, aligning metadata, screenshots, pricing, and availability expectations called out in preconditions. Use it when you are shipping or troubleshooting a stuck review, especially when a prepared build should be submitted but readiness errors keep blocking the pipeline.1kinstalls6Asc Localize Metadataasc-localize-metadata is a mobile Launch skill for solo and indie iOS builders who already ship through App Store Connect and want repeatable multilingual listings without manual copy-paste in the web UI. It walks you through authenticating the asc CLI, resolving your app and version identifiers deterministically, downloading existing metadata from a source locale such as en-US, running LLM translation for additional languages, and uploading localized fields back to Connect. The workflow emphasizes id-based operations, JSON-first CLI output, and checking --help for the installed asc version so flags stay accurate. Use it when someone asks to localize an app’s store listing, translate What’s New for a release, or add new languages to an existing app. It assumes at least one locale is already populated in Connect and that credentials are configured via asc auth login or ASC environment variables.1kinstalls7Asc Build Lifecycleasc-build-lifecycle is a procedural agent skill for solo and indie iOS builders who already use Apple's asc CLI against App Store Connect. It standardizes how you find the right build for a version and platform, inspect processing state before you block a release, run publish testflight or publish appstore with wait and optional submit flags, and retire old binaries so quotas and clutter do not surprise you. The skill is written as copy-paste command recipes with APP_ID, BUILD_ID, and platform placeholders, which fits agents in Claude Code, Cursor, or Codex that need deterministic steps rather than guessing xcodebuild or Transporter flows alone. You reach for it when a build is stuck processing, you need the next build number before upload, or you want a 90-day expire-all dry-run before confirm. It does not replace signing, archive, or CI configuration—it assumes you have an IPA and Connect credentials configured for asc.1kinstalls8Asc Testflight Orchestrationasc-testflight-orchestration teaches coding agents how to manage Apple TestFlight using the asc command-line tool. It is aimed at indie iOS/macOS developers who already use App Store Connect and want to roll out betas without clicking through every group, tester, and localization by hand. The skill covers exporting the current TestFlight configuration to YAML, creating groups, inviting testers, assigning builds to groups, and maintaining What to Test copy per locale. Pagination flags and ID-first commands reflect real-world scale when tester lists grow. The readme notes pairing with an ID resolver skill when names are ambiguous—plan for that when automating pipelines. Invoke it when a build is ready for external or internal testers and you need consistent, scriptable steps your agent can repeat each release train. It does not replace App Store review submission or full ASC project setup; it focuses on TestFlight distribution orchestration immediately before and during beta cycles.1kinstalls9Asc Signing Setupasc signing setup is an agent skill that scripts the Apple signing ladder for solo and indie iOS and macOS builders through the asc command-line tool. Use it when onboarding a new app identifier, renewing distribution certificates before expiry, or aligning capabilities like iCloud with what Xcode expects. The documented flow lists bundle IDs, attaches capabilities with optional settings payloads, creates IOS_DISTRIBUTION (or analogous) certificates from a CSR or generated key material, and provisions profiles that match your bundle and team. It assumes authentication is already configured via asc auth login or ASC environment variables, and it fits the stressful window between a working archive and a successful upload to App Store Connect. Treat outputs as operational secrets: keys and profiles belong in secure storage, not committed repos.1kinstalls10Asc Xcode Buildasc-xcode-build is an agent skill for indie iOS, tvOS, and visionOS developers who need a repeatable path from Xcode source to an upload-ready IPA or PKG using the asc CLI family. It assumes Xcode and command-line tools are installed, signing identities or automatic signing are configured, and App Store Connect authentication is ready when you need remote build lookups. The workflow favors asc xcode archive and asc xcode export over copying fragile xcodebuild snippets, and it front-loads version hygiene with asc xcode version commands plus optional next-build-number resolution against App Store Connect to avoid low build-number rejections. Solo builders use it right before submission sprints when archive errors, stale build numbers, or multi-target projects slow release. It pairs naturally with distribution-focused skills once the binary exists, but it does not replace human review of provisioning profiles, entitlements, or App Review guidelines.998installs11Asc Shots Pipelineasc-shots-pipeline is an agent skill for solo iOS builders who want repeatable App Store screenshots without hand-clicking every simulator state. It wires Xcode CLI build and launch, AXe-driven UI automation from JSON plans, Koubou-based framing through `asc screenshots frame`, and listing upload via `asc screenshots upload`. Defaults keep settings in `.asc/shots.settings.json`, plans in `.asc/screenshots.json`, raw captures under `./screenshots/raw`, and framed assets under `./screenshots/framed`, with `iphone-air` as the default frame device. The skill is explicit that device listing is built-in, framing version is pinned for reproducibility, and some local automation commands remain experimental—file issues at the App Store Connect CLI repo when flows break. Use it when a user asks for AXe simulator flows, framed marketing shots, or a full capture-to-ASC pipeline in one session.965installs12Asc Ppp PricingAsc-ppp-pricing guides agents through Apple App Store Connect territory pricing for auto-renewing subscriptions and in-app purchases using the asc CLI. Solo iOS builders use it when implementing purchasing-power-parity or regional price ladders without clicking through every territory in the web UI. The skill separates greenfield paths—subscriptions setup and iap setup—from change paths such as subscriptions pricing, iap pricing summary, and price schedule updates. Preconditions include authenticated asc sessions or ASC_* environment variables, an app identifier, and a chosen baseline territory (usually USA). It expects you to list supported territories when IDs are unclear. The workflow is command-sequence documentation for Codex, Claude Code, or Cursor operators shipping mobile SaaS, not a generic spreadsheet calculator. Validate your price points against App Store rules and local tax display requirements before applying schedules.955installs13Asc Workflowasc-workflow is an agent skill for repo-local multi-step automation using the `asc` CLI and `.asc/workflow.json`. Solo and indie iOS builders use it when they need lane-style release work—validate structure, list public workflows, preview with dry-run, execute with build and group parameters, and recover failed runs via `--resume` without re-passing KEY:VALUE pairs. Workflows run trusted shell commands, keep stdout as JSON for tooling, and stream human-readable step output to stderr. It pairs naturally with Apple ASC skills for signing, uploads, and TestFlight when you want repeatable, auditable release paths instead of one-off terminal history. Verify flags with built-in help before scripting agents.953installs14Asc Subscription Localizationasc-subscription-localization is an agent skill for indie and solo iOS builders who already use Rudrankriyam’s asc CLI and need every App Store locale filled in for subscriptions, subscription groups, and in-app purchases. It walks through resolving group and subscription IDs, inspecting existing localizations, and applying bulk display names and descriptions across the full App Store Connect locale set—from ar-SA through zh-Hant—so you stop duplicating the same strings in the web UI. You should reach for it when pricing and monetization are wired in App Store Connect but localization is incomplete or stale, typically as you prepare a release or expand markets. The skill assumes authentication via asc auth login or ASC_* environment variables and that ASC_APP_ID (or --app) is known. It is procedural CLI documentation, not a hosted integration: your agent runs the documented asc commands against your project.942installs15Asc NotarizationAsc-notarization is a procedural agent skill for indie Mac developers shipping outside the App Store. It assumes Xcode and command-line tools, asc authentication (login or ASC_* env vars), and a Developer ID Application certificate in the login keychain. The workflow starts with verifying signing identity, fixing invalid trust settings if codesign fails, then archiving and notarizing through xcodebuild and asc. It calls out that Developer ID certificates must be created in the Apple Developer portal because the App Store Connect API cannot mint them. Solo builders use it to avoid ad-hoc forum recipes when stapling notarization tickets to a .app or disk image for Gatekeeper-friendly downloads.914installs16Asc Crash TriageASC Crash Triage is an agent skill that wires Apple TestFlight operations into a repeatable triage ritual for solo iOS builders. When testers report crashes or sluggish launches, you invoke it to resolve the app identifier, pull the right asc testflight crashes or feedback datasets, and convert raw JSON into an actionable summary instead of scrolling App Store Connect blindly. It covers listing crashes newest-first, narrowing by build, device model, and OS version, and pairing quantitative crash rows with qualitative beta feedback—including screenshots when needed. The skill assumes you already ship through TestFlight and have asc configured; it does not replace symbolic crash log deep dives but accelerates “what broke on this build?” decisions before you cut another release or respond to testers.912installs17Asc App Create Uiasc-app-create-ui lets a solo iOS, macOS, tvOS, or visionOS builder create an App Store Connect app entry by automating the web UI because Apple offers no public API for net-new app records. The workflow starts with asc bundle-ids create and asc apps list JSON checks, then opens a signed-in Connect session to fill the New App form with name, bundle ID, SKU, platform, language, and access level. It is opt-in local automation for agents that already have browser tooling and a human who can complete login and two-factor authentication. Guardrails forbid storing cookies, require a visible browser, pause for final confirmation before Create, and avoid automatic retries on failure. Use when you have a registered bundle ID and need the Connect shell record before versioning, ASO metadata, or TestFlight pipelines. It complements API-first asc skills rather than replacing them for listings you can create programmatically elsewhere.910installs18Asc Aso Auditasc-aso-audit is an agent skill that applies a structured App Store Connect (ASC) rules reference when you review or prepare iOS and Mac App Store listings. Solo and indie builders shipping mobile apps use it to catch wasted keyword characters, duplicated indexed terms, and misunderstandings about what Apple actually searches versus what only affects conversion on the product page. The skill encodes indexing mechanics—indexed title, subtitle, and keyword field versus non-indexed description and promotional text—and practical keyword-field formatting such as tight comma separation and avoiding repeats already present in title or subtitle. It also explains Apple Full Text Search combinations across fields and why single-word tokens can outperform cramming phrases into one field. Description and promotional text guidance focuses on natural keyword reflection for download rate rather than search index placement. Screenshot caption OCR indexing is noted as an algorithm update builders should plan for even when this audit does not verify captions automatically. Treat it as a checklist-driven checker before release or metadata refresh, not a substitute for live Search Ads experiments or l873installs19Asc Revenuecat Catalog Syncasc-revenuecat-catalog-sync is an agent skill for solo and indie iOS and macOS builders who sell through App Store Connect and manage entitlements in RevenueCat. It walks through reconciling subscription and in-app purchase catalogs across both systems using the asc tool and the RevenueCat MCP server, starting in audit-only mode and only applying changes after you confirm. Typical flows include bootstrapping RevenueCat from an existing ASC catalog, creating missing ASC products then mapping them, and running a pre-release drift check so identifiers, offerings, and packages match what you intend to ship. Safety defaults assume write-enabled RevenueCat API v2 keys only when you are ready to mutate state. The skill is aimed at builders who already know their ASC app ID, RevenueCat project_id, and target app type (app_store or mac_app_store) plus bundle ID for create paths.850installs20Asc Whats New Writerasc-whats-new-writer encodes how solo and indie iOS developers should draft App Store What's New text so updates convert instead of disappearing behind generic boilerplate. The skill treats the first roughly 170 characters as the only copy many users will read, and demands a complete compelling sentence that leads with the highest-impact user benefit. Body content may be grouped into New, Improved, and Fixed blocks, but only when each section has real substance—empty headings are discarded. Voice is benefit-led and second-person, favoring verbs users can picture rather than internal engineering jargon. It also documents Apple-aligned anti-patterns such as version numbers in headings and empty maintenance notes. Use it at each release when you are tired of shipping update notes that waste store real estate and want an agent to enforce structure, length, and tone before submission.844installs21Asc Wall Submitasc-wall-submit documents the exact CLI workflow for indie iOS developers who want their app listed on the App-Store-Connect-CLI Wall of Apps. It wraps `asc apps wall submit` with a preview-then-confirm discipline: dry-run first with either a standard App Store app ID or a manual TestFlight-style link plus display name, then apply with `--confirm` after reviewing the generated PR plan. The skill insists on running from the CLI repo root, touching only the intended wall entry in docs/wall-of-apps.json, and retrying after fixing bad inputs. It fits builders who say submit to wall of apps, add my app to the wall, or wall-of-apps and want a repeatable agent-guided path instead of hand-editing JSON blindly.838installs22Asc Screenshot Resizeasc-screenshot-resize is an agent skill for solo and indie builders shipping Apple apps who need App Store Connect screenshots that actually pass validation. It walks you through discovering current accepted dimensions from the asc CLI, sanitizing filenames that break on hidden Unicode spaces, resizing with macOS sips, and validating local folders against concrete device-type anchors before upload. The workflow assumes you are on macOS with asc installed and raw captures ready to batch-process. Because Apple’s accepted sizes change, the skill deliberately does not embed a static pixel table—it forces live discovery and validation commands so your agent does not ship outdated specs. Use it when you are preparing a new submission, fixing rejections tied to screenshot dimensions, or expanding to additional display families beyond the common iPhone 6.5-inch and iPad Pro sets.674installs