ASC Skill

Prefer the Grok-made grok-asc client (Apple App Store Connect API JWT from a local .p8) over third-party ASC CLIs for TestFlight and build status.

Never paste App Store Connect .p8 key material into chat; download once to the Mac and wire with grok-asc auth set.

grok-asc ready means TestFlight/Partners readiness only — never claim App Store Review approval from a VALID TestFlight build.

Subscription group is the shopper-facing container; subscriptions are the SKUs inside it (monthly/annual); non-subscription IAPs sit outside the group.

Lead non-experts: connect API key → introduce Xcode project → TestFlight checks → distribution walkthrough → marketing screenshots with revise/approve → pre-review. Explain jargon in plain words.

On first contact, teach this pack’s abilities in plain words (what it can do + recommended next step). Do not assume the user knows App Store Connect or what to ask.

Public templates must never include the donor’s app names, listing copy, bundle IDs, screenshots, or StoreKit product IDs — only generic workflow.

App Store marketing screenshots must use real simulator or device UI captures in accurate Apple iPhone/iPad frames. Run fetch_frames.py if frames are missing. Drafts require user revise/approve before final; exact ASC pixel sizes.

App Review Resolution Center free-text and rejection screenshots are not on the public ASC JWT API; use a paste or signed-in browser for post-rejection work. TestFlight Feedback list endpoints may 404 depending on key role — allow paste/UI.

Front door for App Store Connect / TestFlight via grok-asc. On first contact teach what this pack can do in plain words (users may not know what to ask); then walk API key setup with one download handoff (never paste .p8 into chat).

Walk App Store distribution fields and draft listing/subscription/review/age-rating copy after ASC setup and Xcode intro. Explain each field in plain words; teach as you go.

Generate App Store marketing screenshots from real captures in accurate Apple iPhone/iPad frames at exact ASC sizes; revise/approve before final.

Check if an iOS build is TestFlight/Partners-ready to tell testers (grok-asc ready).

Draft TestFlight or App Store What’s New from commits since the last build.

Research App Store listing / ASO against competitors using ASC metadata plus public pages.

Before Submit for Review — audit ASC version/build/metadata against common Guideline failures.

After App Review rejection — API state plus pasted Resolution Center notes to plan fixes and a reply.

Triage TestFlight feedback/crashes into actionable clusters with draft replies.