- name
SKILL.md
스킬 파일은 게시자의 저장소에 그대로 있습니다.
복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add rorkai/app-store-connect-cli-skills --skill asc-ad-hoc-distribution -a cursor -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add rorkai/app-store-connect-cli-skills --skill asc-ad-hoc-distribution -a claude-code -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add rorkai/app-store-connect-cli-skills --skill asc-ad-hoc-distribution -a codex -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add rorkai/app-store-connect-cli-skills --skill asc-ad-hoc-distribution -a grok -y복사한 메시지를 Grok Bot 채팅에 보냅니다. Bot이 GitHub에서 이 SKILL.md를 가져와 모든 Bot이 공유하는 스킬에 추가합니다.
Install this skill: https://github.com/rorkai/app-store-connect-cli-skills/tree/HEAD/skills/asc-ad-hoc-distribution게시자 제공
Use the experimental asc distribute workflow to turn an existing iOS archive
into a private, verified install link for registered devices. Use TestFlight or
the App Store release skills instead when the build should go through Apple-hosted
distribution.
Confirm the installed contract before acting:
asc distribute --help
asc distribute plan --help
asc distribute apply --help
asc distribute resume --help
asc distribute status --help
asc distribute verify --help
plan -> apply -> resume/status -> verify for an end-to-end,
hash-authorized run starting from an .xcarchive.inspect -> prepare -> publish only when the caller already owns the
ad hoc IPA and wants to operate the lower-level boundaries separately.ASC_S3_ACCESS_KEY_ID,
ASC_S3_SECRET_ACCESS_KEY, and optional ASC_S3_SESSION_TOKEN, or the
standard AWS SDK credential chain.plan is read-only and may exit successfully with ready: false. Inspect the
typed blockers and effects before continuing.apply can register missing devices, create safe App IDs and successor ad hoc
profiles, write local artifacts, and publish immutable objects. Run it only
after the user authorizes the exact plan hash and effect inventory..xcarchive with one main app target. Embedded apps,
extensions, Watch apps, and App Clips make the v1 plan not ready.{"schemaVersion":1,"devices":[{"name":"Test iPhone","udid":"DEVICE_UDID","platform":"IOS"}]}
Relative paths resolve from the spec directory. The spec does not interpolate environment variables or accept credentials. A representative private config is:
{
"schemaVersion": 1,
"devicesFile": "devices.json",
"signing": {
"identity": {
"format": "pkcs12",
"path": "../signing/distribution.p12",
"passwordFile": "../secrets/distribution-p12-password"
},
"minimumValidityDays": 7,
"maxMutations": 32
},
"publication": {
"endpoint": "https://objects.example.com",
"downloadEndpoint": "https://downloads.example.com",
"region": "auto",
"bucket": "ios-builds",
"prefix": "team/app",
"addressingStyle": "path",
"urlTtl": "24h",
"downloadGrace": "1h",
"verifyTimeout": "30s"
},
"metadata": {
"title": "App",
"channel": "pull-request-42",
"sourceRevision": "abc123",
"sourceUrl": "https://example.com/team/app/commit/abc123"
}
}
passwordFile, certificateSha256, downloadEndpoint, and every metadata field
are optional. An omitted password file means the PKCS#12 must use an empty
password. Protect the config and secret inputs before planning:
chmod 600 ".asc/distribution/config.json" ".asc/distribution/devices.json"
chmod 600 ".asc/signing/distribution.p12" ".asc/secrets/distribution-p12-password"
asc distribute plan \
--archive-path ".asc/artifacts/App.xcarchive" \
--config ".asc/distribution/config.json" \
--plan ".asc/distribution/plan.json" \
--state-dir ".asc/distribution/runs" \
--output json
Inspect ready, planHash, signing validity, destination, and the complete
ordered effects inventory. Resolve blockers and create a new plan when
ready is false. Do not infer readiness from exit code alone.
After approval of the exact effects, pass the full 64-character hash:
PLAN_HASH="$(jq -er '.planHash' ".asc/distribution/plan.json")"
asc distribute apply \
--plan ".asc/distribution/plan.json" \
--confirm "$PLAN_HASH" \
--output json
Missing, malformed, or unequal confirmation is rejected before side effects. Success means publication and live fetch verification completed; it does not mean a device installed or launched the app.
Use the returned runId:
asc distribute status --run "RUN_ID" --state-dir ".asc/distribution/runs" --output json
asc distribute resume --run "RUN_ID" --state-dir ".asc/distribution/runs" --output json
asc distribute verify --run "RUN_ID" --state-dir ".asc/distribution/runs" --timeout 30s --output json
status is local-only and succeeds for running, recoverable, and blocked
runs; branch on typed fields rather than prose. resume revalidates durable
evidence before retrying and never blindly repeats a remote write. verify is
read-only but performs live fetches. Add --device "DEVICE_SELECTOR" only when
the user asks to observe the matching installed bundle, version, and build on a
connected device; this observation does not prove IPA byte identity.
The exact private install URL is a bearer credential stored only in the owner-private link artifact reported by the completed run. Share it only with the intended tester through an approved private channel.
Use this lane when signing and export are already complete. Pass the exact
bundleDir returned by prepare to publish:
asc distribute inspect --ipa ".asc/artifacts/App.ipa" --output json
asc distribute prepare --ipa ".asc/artifacts/App.ipa" --channel "pull-request-42" --output json
asc distribute publish \
--bundle-dir ".asc/distribution/com.example.app/1.2-42-IPA_SHA_PREFIX" \
--endpoint "https://objects.example.com" \
--region "auto" \
--bucket "ios-builds" \
--prefix "team/app" \
--receipt ".asc/publishes/app-1.2-42.json" \
--link-path ".asc/publishes/app-1.2-42-link.json" \
--output json
inspect omits raw device UDIDs unless --include-devices is explicitly
needed. prepare never overwrites a bundle and reuses only an exact equivalent.
Private publish is the default and writes exact presigned links only to the
mode-0600 link artifact. Public publication is a separate explicit lane using
--access public --public-base-url; it assumes anonymous reads are already
configured and never changes storage policy.
Prepare, publish, resume, and verify private iOS release-testing installs with asc distribute. Use when distributing an IPA to registered devices outside TestFlight, reconciling ad hoc profiles, publi
---name: asc-ad-hoc-distributiondescription: Prepare, publish, resume, and verify private iOS release-testing installs with asc distribute. Use when…---# skills/asc-ad-hoc-distribution/SKILL.md개요
Prepare, publish, resume, and verify private iOS release-testing installs with asc distribute. Use when distributing an IPA to registered devices outside TestFlight, reconciling ad hoc profiles, publishing through caller-owned S3-compatible storage, or diagnosing a resumable private distribution run.
FAQ
게시자에게서 skills/asc-ad-hoc-distribution/SKILL.md를 다운로드하거나 경로를 복사해 저장소를 엽니다. PlugMCP는 스킬을 목록에 올릴 뿐 파일을 호스팅하지 않습니다.
게시자가 https://github.com/rorkai/app-store-connect-cli-skills에서 관리합니다.
Claude, Cursor, Codex, Grok Build는 게시자의 저장소에서 추가한 SKILL.md를 읽을 수 있습니다. Grok Bot은 채팅에서 스킬의 GitHub 폴더 링크를 보내면 설치합니다.