- name
SKILL.md
技能文件保留在发布者的仓库中。
在终端中粘贴复制的命令。它会把这个 SKILL.md 安装到对应的智能体中。
npx skills add rorkai/app-store-connect-cli-skills --skill asc-signing-setup -a cursor -y在终端中粘贴复制的命令。它会把这个 SKILL.md 安装到对应的智能体中。
npx skills add rorkai/app-store-connect-cli-skills --skill asc-signing-setup -a claude-code -y在终端中粘贴复制的命令。它会把这个 SKILL.md 安装到对应的智能体中。
npx skills add rorkai/app-store-connect-cli-skills --skill asc-signing-setup -a codex -y在终端中粘贴复制的命令。它会把这个 SKILL.md 安装到对应的智能体中。
npx skills add rorkai/app-store-connect-cli-skills --skill asc-signing-setup -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-signing-setup来自发布者
Use this skill when you need to create or renew signing assets for iOS/macOS apps.
asc auth login or ASC_* env vars).asc certificates create --generate-csr create one.asc bundle-ids list --paginateasc bundle-ids create --identifier "com.example.app" --name "Example" --platform IOSasc bundle-ids capabilities list --bundle "BUNDLE_ID"asc bundle-ids capabilities add --bundle "BUNDLE_ID" --capability ICLOUD--settings '[{"key":"ICLOUD_VERSION","options":[{"key":"XCODE_6","enabled":true}]}]'PRIVATE_CLOUD_COMPUTE capability, use a
user-owned web session and the Developer Portal Bundle ID resource ID:
asc web bundle-ids capabilities enable --bundle-id "BUNDLE_RESOURCE_ID" --capability PRIVATE_CLOUD_COMPUTE --confirmasc web auth logout --apple-id "[email protected]"asc web auth login --apple-id "[email protected]"APP_GROUPS but cannot create or
associate App Group resources. Use an Account Holder or Admin web session:
asc web app-groups list --paginate --output tableasc web app-groups create --name "Example Shared" --identifier "group.com.example.app.shared" --confirmasc web app-groups assign --group "GROUP_RESOURCE_ID" --bundle-id "BUNDLE_RESOURCE_ID" --confirmasc web app-groups list and the opaque
Bundle ID resource ID with asc bundle-ids list. A changed assignment
invalidates provisioning profiles containing that App ID, so regenerate
affected profiles before the next signed build.asc certificates list --certificate-type IOS_DISTRIBUTIONasc certificates create --certificate-type IOS_DISTRIBUTION --csr "./cert.csr"asc certificates create --certificate-type IOS_DISTRIBUTION --generate-csr --key-out "./signing/dist.key" --csr-out "./signing/dist.csr"asc pass-type-ids create --identifier "pass.com.example" --name "Example Pass"asc certificates create --certificate-type PASS_TYPE_ID --pass-type-id "PASS_TYPE_ID" --csr "./pass.csr"asc pass-type-ids certificates list --pass-type-id "PASS_TYPE_ID" --paginateasc profiles create --name "AppStore Profile" --profile-type IOS_APP_STORE --bundle "BUNDLE_ID" --certificate "CERT_ID"asc profiles create --name "Dev Profile" --profile-type IOS_APP_DEVELOPMENT --bundle "BUNDLE_ID" --certificate "CERT_ID" --device "DEVICE_ID"asc profiles download --id "PROFILE_ID" --output "./profiles/AppStore.mobileprovision"asc profiles inspect --path "./profiles/AppStore.mobileprovision" --output tableasc profiles inspect --path "./profiles/AppStore.mobileprovision" --entitlements --output markdownasc profiles local install --path "./profiles/AppStore.mobileprovision"asc profiles local list --output table~/Library/Developer/Xcode/UserData/Provisioning Profiles; Xcode 15 or older uses ~/Library/MobileDevice/Provisioning Profiles. Hosts without a full active Xcode fall back to the legacy directory and print a note to stderr.--install-dir when automation must target a fixed directory.asc certificates revoke --id "CERT_ID" --confirmasc profiles list --profile-state ACTIVE,INVALID --paginate --output jsonprofileState is not a complete expiration signal: some profiles can have a past expirationDate while still reporting ACTIVE. For true expired-profile audits, compare expirationDate against the current date instead of relying only on INVALID.asc profiles delete --id "PROFILE_ID" --confirmasc profiles local clean --expired --dry-runasc profiles local clean --expired --confirm--install-dir.asc signing syncUse this when you want a lightweight, non-interactive alternative to fastlane match for encrypted git-backed certificate/profile storage.
# Protect secret inputs before use
chmod 600 "./signing-sync-password" "./distribution.p12" "./distribution-p12-password"
# Push a usable private identity with its matching certificate and profile
asc signing sync push \
--bundle-id "com.example.app" \
--profile-type IOS_APP_ADHOC \
--repo "[email protected]:team/certs.git" \
--password-file "./signing-sync-password" \
--identity "./distribution.p12" \
--identity-password-file "./distribution-p12-password" \
--output json
# Pull and decrypt them into a local directory
asc signing sync pull \
--repo "[email protected]:team/certs.git" \
--password-file "./signing-sync-password" \
--output-dir "./signing" \
--output json
Notes:
--identity, or use --private-key with --identity-sha256 to select its
matching App Store Connect certificate. A multi-identity PKCS#12 also needs
--identity-sha256.--password-file; ASC_SIGNING_SYNC_PASSWORD is the non-file fallback.
--password was removed in 5.0.0 and is rejected. ASC_MATCH_PASSWORD is
no longer read and is ignored if set.identityPresent: false; it is not a usable signing identity by itself.pull reports private identities in sensitiveFiles and writes them mode
0600. Importing or using the pulled identity remains a separate explicit step.MAC_APP_DIRECT and
MAC_CATALYST_APP_DIRECT; certificate/profile-only sync remains available.Use the experimental reconcile workflow for deterministic, additive changes derived from an Xcode archive and a protected desired-devices file:
asc signing reconcile plan \
--archive-path ".asc/artifacts/App.xcarchive" \
--devices-file ".asc/distribution/devices.json" \
--output json
asc signing reconcile apply \
--plan ".asc/distribution/signing/plan.json" \
--confirm \
--output json
Planning performs no mutation and may return ready: false. Apply can register
missing devices, create safe baseline App IDs, and create successor ad hoc
profiles; it never deletes or patches resources, enables capabilities, or
creates certificates. Review the plan before --confirm. Use the
asc-ad-hoc-distribution skill when these signing effects should be bound into
an end-to-end distribution plan hash.
On macOS, avoid persistent login-keychain and profile changes by wrapping the child command:
asc signing run \
--identity "./signing/App.p12" \
--identity-password-file "./signing/App-password" \
--profile "./signing/App.mobileprovision" \
--receipt ".asc/distribution/signing-run.json" \
-- xcodebuild -exportArchive \
-archivePath ".asc/artifacts/App.xcarchive" \
-exportPath ".asc/artifacts/release-testing" \
-exportOptionsPlist ".asc/ExportOptions.release-testing.plist"
The command runs directly without a shell, preserves the child's exit code, uses an isolated temporary keychain, and cleans up its temporary profile. It does not print success data, so the child owns stdout. Never pass identity passwords inline.
--help for the exact enum values (certificate types, profile types).--paginate for large accounts.--certificate accepts comma-separated IDs when multiple certificates are required.asc devices commands (UDID required).asc profiles inspect and asc profiles local ... operate on local disk state, not App Store Connect API resources.Set up bundle IDs, capabilities, signing certificates, provisioning profiles, and encrypted signing sync with the asc cli. Use when onboarding a new app, rotating signing assets, or sharing them acros
---name: asc-signing-setupdescription: Set up bundle IDs, capabilities, signing certificates, provisioning profiles, and encrypted signing sync with…---# skills/asc-signing-setup/SKILL.md概览
Set up bundle IDs, capabilities, signing certificates, provisioning profiles, and encrypted signing sync with the asc cli. Use when onboarding a new app, rotating signing assets, or sharing them across a team.
常见问题
从发布者处下载 skills/asc-signing-setup/SKILL.md,或复制路径后打开仓库。PlugMCP 只收录该技能,不托管文件。
发布者将它存放在 https://github.com/rorkai/app-store-connect-cli-skills。
Claude、Cursor、Codex 和 Grok Build 可以读取你从发布者仓库添加的 SKILL.md。在聊天中发送技能的 GitHub 文件夹链接,Grok Bot 就会安装它。