Skip to content
Back to search

rorkai

MarketplaceWorks with Claude CodeGitHub

Agent skills and tooling for App Store Connect workflows.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 11 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/rorkai/app-store-connect-cli-skills with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/rorkai/app-store-connect-cli-skills'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/rorkai-app-store-connect-cli-skills/badge.svg)](/listings/rorkai-app-store-connect-cli-skills)

HTML

<a href="/listings/rorkai-app-store-connect-cli-skills"><img src="/api/listings/rorkai-app-store-connect-cli-skills/badge.svg" alt="findsafeskills safety rating" /></a>

Install

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

Install the skills with `asc`:

asc install-skills

Or install them directly from GitHub with the Agent Skills installer:

npx skills add rorkai/app-store-connect-cli-skills

Claude Code plugin

This repository is also a Claude Code marketplace. Add it once, then install the `asc` plugin:

claude plugin marketplace add rorkai/app-store-connect-cli-skills
claude plugin install asc@rorkai

Codex plugin

The repository includes a Codex plugin manifest and can be listed by a Codex plugin marketplace. Codex currently installs plugins from configured marketplaces, so use the Agent Skills installer until `asc` has a public marketplace listing:

npx skills add rorkai/app-store-connect-cli-skills --agent codex

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 13 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. {
  2. "name": "rorkai",
  3. "owner": {
  4. "name": "Rork"
  5. },
  6. "description": "Agent skills and tooling for App Store Connect workflows.",
  7. "plugins": [
  8. {
  9. "name": "asc",
  10. "source": "./"
  11. }
  12. ]
  13. }
README.md · README · 466 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. # ASC CLI skills
  2. A collection of Agent Skills for shipping with the [asc cli](https://github.com/rorkai/App-Store-Connect-CLI) (`asc`). These skills help agents run builds, TestFlight, metadata, submissions, signing, and Apple Ads workflows.
  3. This is a community-maintained, unofficial skill pack and is not affiliated with Apple.
  4. Skills follow the Agent Skills format.
  5. ## Installation
  6. Install the skills with `asc`:
  7. ```bash
  8. asc install-skills
  9. ```
  10. Or install them directly from GitHub with the Agent Skills installer:
  11. ```bash
  12. npx skills add rorkai/app-store-connect-cli-skills
  13. ```
  14. ### Claude Code plugin
  15. This repository is also a Claude Code marketplace. Add it once, then install the `asc` plugin:
  16. ```bash
  17. claude plugin marketplace add rorkai/app-store-connect-cli-skills
  18. claude plugin install asc@rorkai
  19. ```
  20. The Claude plugin follows Git commits. Keep `version` out of both Claude
  21. manifests so skill updates do not require a manual version bump. To refresh an
  22. existing install, run these commands, then restart Claude Code:
  23. ```bash
  24. claude plugin marketplace update rorkai
  25. claude plugin update asc@rorkai
  26. ```
  27. ### Codex plugin
  28. The repository includes a Codex plugin manifest and can be listed by a Codex plugin marketplace.
  29. Codex currently installs plugins from configured marketplaces, so use the Agent Skills installer
  30. until `asc` has a public marketplace listing:
  31. ```bash
  32. npx skills add rorkai/app-store-connect-cli-skills --agent codex
  33. ```
  34. ## Available Skills
  35. ### asc-cli-usage
  36. Guidance for running `asc` commands (canonical verbs, flags, pagination, output, auth).
  37. **Use when:**
  38. - You need the correct `asc` command or flag combination
  39. - You want JSON-first output and pagination tips for automation
  40. - You need Apple Ads command, auth, ad-account, org, payload, or pagination guidance
  41. **Example:**
  42. ```bash
  43. Find the right asc command to list all builds for app 123456789 as JSON and paginate through everything.
  44. ```
  45. ### asc-apple-ads
  46. Apple Ads auth and account discovery, Platform API v1 campaigns, targeting, reports, assets, guarded mutations, raw calls, and v5 migration.
  47. **Use when:**
  48. - You need to read or change Apple Ads resources with `asc ads`
  49. - You need Apple Ads OAuth, profile, ad-account context, or `ASC_ADS_*` guidance
  50. - You need a safe read-first plan before mutating a live Ads account
  51. - You need to migrate deprecated `asc ads v5` automation to Platform API v1
  52. **Example:**
  53. ```bash
  54. Discover my Apple Ads ad account, query campaigns through Platform API v1, and draft a paused test plan before creating anything.
  55. ```
  56. ### asc-workflow
  57. Define and run repo-local automation graphs using `asc workflow` and `.asc/workflow.json`.
  58. **Use when:**
  59. - You are migrating from lane-based automation to repo-local workflows
  60. - You need multi-step orchestration with machine-parseable JSON output for CI/agents
  61. - You need hooks (`before_all`, `after_all`, `error`), conditionals (`if`), and private helper sub-workflows
  62. - You want validation (`asc workflow validate`) with cycle/reference checks before execution
  63. **Example:**
  64. ```bash
  65. Create an asc workflow that stages a release, validates it, and only submits when CONFIRM_RELEASE=true.
  66. ```
  67. ### asc-app-create-ui
  68. Create a new App Store Connect app via browser automation when no API exists.
  69. **Use when:**
  70. - You need to create an app record (name, bundle ID, SKU, primary language)
  71. - You are comfortable logging in to App Store Connect in a real browser
  72. **Example:**
  73. ```bash
  74. Create a new App Store Connect app for com.example.myapp with SKU MYAPP123 and primary language English (U.S.).
  75. ```
  76. ### asc-xcode-build
  77. Build, archive, generate export options, export, and manage Xcode version/build numbers before uploading.
  78. **Use when:**
  79. - You need to create an IPA or PKG for upload
  80. - You're setting up CI/CD build pipelines
  81. - You need to generate or customize ExportOptions.plist
  82. - You need a modern `release-testing` IPA for registered devices
  83. - You're troubleshooting encryption compliance issues
  84. **Example:**
  85. ```bash
  86. Archive and export my macOS app as a PKG I can upload to App Store Connect.
  87. ```
  88. ### asc-ad-hoc-distribution
  89. Prepare and publish verified private iOS installs for registered devices with
  90. the experimental `asc distribute` workflow.
  91. **Use when:**
  92. - You need to ship a build outside TestFlight to a controlled device list
  93. - You want a read-only plan before additive signing and storage mutations
  94. - You need to resume or live-verify a private S3-compatible distribution run
  95. **Example:**
  96. ```bash
  97. Plan a private release-testing install from this Xcode archive, show me the exact effects, and apply only after I approve the plan hash.
  98. ```
  99. ### asc-screenshot-resize
  100. Resize and validate App Store screenshots using the current size catalog from `asc screenshots sizes` and macOS `sips`.
  101. **Use when:**
  102. - You need to inspect the screenshot dimensions Apple currently accepts
  103. - You need to remove alpha or resize screenshots before upload
  104. - You want local validation against an App Store screenshot device type
  105. **Example:**
  106. ```bash
  107. Validate these iPhone screenshots, resize only the invalid files, and verify the results before upload.
  108. ```
  109. ### asc-shots-pipeline
  110. Agent-first screenshot pipeline using xcodebuild/simctl, AXe, JSON plans, `asc screenshots frame` (experimental), and `asc screenshots upload`.
  111. **Use when:**
  112. - You need a repeatable simulator screenshot automation flow
  113. - You want AXe-based UI driving before capture
  114. - You need a staged pipeline (capture -> frame -> upload)
  115. - You need to discover supported frame devices (`asc screenshots list-frame-devices`)
  116. - You want pinned Koubou guidance for deterministic framing (`koubou==0.20.0`)
  117. **Example:**
  118. ```bash
  119. Build my iOS app, capture the home and settings screens in the simulator, frame them, and prepare them for upload.
  120. ```
  121. ### asc-release-flow
  122. Stage, upload, publish, and submit App Store releases through dry-run and confirmation-oriented orchestration.
  123. **Use when:**
  124. - A prepared app version or artifact needs to be staged, uploaded, or submitted
  125. - You need to choose between `asc release stage`, `asc review submit`, and `asc publish appstore`
  126. - You need to assemble a multi-item submission containing Game Center or digital-goods versions
  127. For readiness failures, blocker diagnosis, monitoring, cancellation, or retry decisions, use `asc-submission-health`.
  128. **Example:**
  129. > Stage version 2.4.0 with the selected build, show the dry-run plan, and submit it after confirmation.
  130. ### asc-signing-setup
  131. Bundle IDs, capabilities, certificates, provisioning profiles, and encrypted signing sync.
  132. **Use when:**
  133. - You are onboarding a new app or bundle ID
  134. - You need to create or rotate signing assets
  135. - You need to sync a private identity, reconcile ad hoc profiles, or run a command in an isolated signing environment
  136. **Example:**
  137. ```bash
  138. Set up signing for com.example.app with iCloud enabled, a distribution certificate, and an App Store profile.
  139. ```
  140. ### asc-id-resolver
  141. Resolve IDs for apps, builds, app and digital-goods versions, groups, and testers.
  142. **Use when:**
  143. - A command requires IDs and you only have names
  144. - You need an API 4.4.1 IAP, subscription, or subscription-group version ID
  145. - You want deterministic outputs for automation
  146. **Example:**
  147. ```bash
  148. Resolve the App Store Connect app ID, latest build ID, and TestFlight group IDs for MyApp.
  149. ```
  150. ### asc-metadata-sync
  151. Metadata and localization sync (including legacy metadata format migration).
  152. **Use when:**
  153. - You are updating App Store metadata or localizations
  154. - You need to validate character limits before upload
  155. - You need to update privacy policy URL or app-level metadata
  156. **Example:**
  157. ```bash
  158. Pull my App Store metadata into ./metadata, update the privacy policy URL, and push the changes back safely.
  159. ```
  160. ### asc-localize-metadata
  161. Translate App Store metadata (description, keywords, what's new, subtitle) to multiple locales using LLM translation prompts and push via `asc`.
  162. **Use when:**
  163. - You want to localize an app's App Store listing from a source locale (usually en-US)
  164. - You need locale-aware keywords (not literal translations) and strict character limit enforcement
  165. - You want a review-before-upload workflow for translations
  166. **Example:**
  167. ```bash
  168. Translate my en-US App Store metadata into German, French, and Japanese, then show me the changes before upload.
  169. ```
  170. ### asc-aso-audit
  171. Run an offline ASO audit on canonical App Store metadata under `./metadata` and surface keyword gaps using Astro MCP.
  172. **Use when:**
  173. - You want to audit subtitle, keywords, description, and what's new fields for waste and formatting issues
  174. - You want keyword-gap analysis against Astro-tracked rankings and competitor terms
  175. - You want follow-up actions that map cleanly to `asc metadata keywords ...`
  176. **Example:**
  177. ```bash
  178. Audit ./metadata for ASO problems, then show the highest-value keyword gaps from Astro for my latest version.
  179. ```
  180. ### asc-analytics-reports
  181. Collect, download, and verify private App Store Connect Analytics reports with `asc`.
  182. **Use when:**
  183. - You need to find an existing analytics report request
  184. - You want report instances filtered by processing date or granularity
  185. - You need every report segment downloaded and checked against Apple's size and MD5 metadata
  186. **Example:**
  187. ```bash
  188. Collect my latest weekly analytics reports, download every segment privately, and verify each file before analysis.
  189. ```
  190. ### asc-whats-new-writer
  191. Generate engaging, localized App Store release notes from git log, bullet points, or free text using canonical metadata under `./metadata`.
  192. **Use when:**
  193. - You want polished What's New copy from rough release inputs
  194. - You want localized release notes across existing locales
  195. - You want a review-before-upload workflow using `asc metadata push` or direct metadata edits
  196. **Example:**
  197. ```bash
  198. Turn these release bullet points into polished What's New notes for en-US and localize them across my existing metadata locales.
  199. ```
  200. ### asc-submission-health
  201. Diagnose submission blockers, route repairs, monitor review state, cancel unhealthy submissions, and decide when to retry.
  202. **Use when:**
  203. - You want to know whether an app can be submitted now
  204. - Validation reports metadata, compliance, digital-goods, availability, or App Privacy blockers
  205. - A version is not in a valid state
  206. - You need to monitor, cancel, repair, or safely retry a submission
  207. For staging, upload, publication, and submission execution, use `asc-release-flow`.
  208. **Example:**
  209. ```bash
  210. Validate version 2.4.0, classify every blocker, route the repairs, and tell me whether it is safe to retry.
  211. ```
  212. ### asc-testflight-orchestration
  213. Beta groups, testers, build distribution, and What to Test notes.
  214. **Use when:**
  215. - You manage multiple TestFlight groups and testers
  216. - You need consistent beta rollout steps
  217. **Example:**
  218. ```bash
  219. Export my current TestFlight config, create a new external group, add testers, and attach the latest build.
  220. ```
  221. ### asc-build-lifecycle
  222. Build processing, latest build resolution, and cleanup.
  223. **Use when:**
  224. - You are waiting on build processing
  225. - You want automated cleanup and retention policies
  226. **Example:**
  227. ```bash
  228. Find the latest processed build for app 123456789 and preview expiring all TestFlight builds older than 90 days.
  229. ```
  230. ### asc-ppp-pricing
  231. Territory-specific pricing using purchasing power parity (PPP).
  232. **Use when:**
  233. - You want different prices for different countries
  234. - You are implementing localized pricing strategies
  235. - You need to adjust prices based on regional purchasing power
  236. **Example:**
  237. ```bash
  238. Update my subscription pricing for India, Brazil, and Mexico using a PPP-style rollout and verify the result.
  239. ```
  240. ### asc-subscription-localization
  241. Bulk-localize subscription and IAP display names across all App Store locales,
  242. including API 4.4.1 version-scoped v2 resources.
  243. **Use when:**
  244. - You want to set the same subscription display name in every language at once
  245. - You need to fill in missing subscription/group/IAP localizations
  246. - You're tired of clicking through each locale in App Store Connect manually
  247. **Example:**
  248. ```bash
  249. Set the display name Monthly Pro across all missing locales for this subscription and verify which locales were created.
  250. ```
  251. ### asc-revenuecat-catalog-sync
  252. Reconcile App Store Connect subscriptions/IAP with RevenueCat products, entitlements, offerings, and packages.
  253. **Use when:**
  254. - You want to sync ASC product catalogs to RevenueCat
  255. - You need to create missing ASC subscriptions/IAPs before mapping them
  256. - You want an audit-first workflow with explicit apply confirmation
  257. **Example:**
  258. ```bash
  259. Audit my App Store Connect subscriptions and IAPs against RevenueCat, then create any missing mappings after I approve the plan.
  260. ```
  261. ### asc-notarization
  262. Archive, export, and notarize macOS apps with Developer ID signing.
  263. **Use when:**
  264. - You need to notarize a macOS app for distribution outside the App Store
  265. - You want the full flow: archive → Developer ID export → zip → notarize → staple
  266. - You're troubleshooting Developer ID signing or trust chain issues
  267. **Example:**
  268. ```bash
  269. Archive my macOS app, export it for Developer ID, notarize the ZIP, and staple the result.
  270. ```
  271. ### asc-crash-triage
  272. Triage TestFlight crashes, beta feedback, and performance diagnostics.
  273. **Use when:**
  274. - You want to review recent TestFlight crash reports
  275. - You need a crash summary grouped by signature, device, and build
  276. - You want to check beta tester feedback and screenshots
  277. - You need performance diagnostics (hangs, disk writes, launches) for a build
  278. **Example:**
  279. ```bash
  280. Show me the latest TestFlight crashes and feedback for MyApp, grouped by signature and affected build.
  281. ```
  282. ### asc-in-app-events
  283. Create and localize App Store in-app events, upload event media, and submit or recover event review submissions.
  284. **Use when:**
  285. - You want to publish an in-app event from the terminal
  286. - You need to upload event card and event details page art
  287. - An event cannot be added to a review submission (missing deep link)
  288. - You need to recover an event submission without creating duplicate drafts
  289. **Example:**
  290. ```bash
  291. Prepare a challenge event for MyApp with en-US and de-DE localizations and event artwork, then report what remains before submission.
  292. ```
  293. ### asc-wall-submit
  294. Submit or update an app entry in the App-Store-Connect-CLI Wall of Apps using `asc apps wall submit`.
  295. **Use when:**
  296. - You want to add your app to the Wall of Apps
  297. - You want to update an existing Wall entry
  298. - You want the built-in CLI Wall submission flow
  299. **Example:**
  300. ```bash
  301. Submit app 1234567890 to the Wall of Apps using the built-in asc apps wall submit flow.
  302. ```
  303. ## Usage
  304. Skills are automatically available once installed. The agent will use them when relevant tasks are detected.
  305. ## Skill Structure
  306. Each skill contains:
  307. - `SKILL.md` - Instructions for the agent
  308. - `scripts/` - Helper scripts for automation (optional)
  309. - `references/` - Supporting documentation (optional)
  310. ## License
  311. MIT

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.