Automated summary
Automates the creation and renewal of iOS/macOS signing assets (bundle IDs, capabilities, certificates, provisioning profiles) through the asc CLI, including encrypted sync of signing material to a git repo.
Strengths
- Covers the full signing chain: bundle ID, capabilities, certificate, profile, then profile download
- Offers `asc signing sync` as a lightweight, non-interactive alternative to fastlane match with a match-style git layout
- Provides explicit commands for rotating, revoking certificates and deleting stale profiles
- Handles development/ad-hoc profiles with device inclusion and accepts comma-separated certificate IDs
Limitations
- Assumes asc auth is already configured and that a CSR file is available
- Relies entirely on the asc CLI, whose installation and enum values are not covered here
- `signing sync pull` only writes files; keychain import and profile installation remain separate steps
Use it when onboarding a new app, rotating signing assets, or sharing certificates and profiles across a team.
Skip it if you don't use the asc CLI or if signing is handled solely through Xcode or fastlane.
Security analysis
CautionThe instructions are transparent and limited to legitimate Apple Developer signing workflows via the `asc` CLI, with no obfuscation, remote code execution, or data exfiltration. However, it performs powerful and partially destructive actions (certificate revocation, profile deletion, encrypted cert sync to a git remote) and handles private key material and secrets, so it warrants caution rather than a clean 'safe' rating.
- •Destructive operations on real signing assets (`asc certificates revoke --confirm`, `asc profiles delete --confirm`) are documented with only a `--confirm` flag and no backup/verification guidance.
- •Encrypted-signing password is expanded inline into a CLI argument (`--password "$MATCH_PASSWORD"`), which can leak via shell history, process listings, or CI logs; no guidance on safer secret injection.
- •`asc signing sync pull` decrypts certificates/profiles to an arbitrary `--output-dir` with no instruction on directory permissions or post-use cleanup of sensitive material at rest.
- •Pushes private signing assets to a git remote; security depends entirely on the encryption password strength and repo access control, which the skill does not discuss.
- •No guidance on scoping `ASC_*` credentials to least-privilege API keys, even though the skill manages account-wide signing infrastructure.
Examples
Set up signing for a new iOS app with bundle ID com.example.app: create the bundle ID, enable iCloud, create an IOS_DISTRIBUTION certificate from ./cert.csr, then create and download an App Store provisioning profile to ./profiles/.My IOS_DISTRIBUTION certificate expired. Create a new one from ./cert.csr, recreate the App Store profile using the new certificate, then revoke the old certificate.Push our signing assets for com.example.app (IOS_APP_STORE profile) to git@github.com:team/certs.git with asc signing sync, then show how a teammate pulls and decrypts them into ./signing.name: asc-signing-setup description: 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.
asc signing setup
Use this skill when you need to create or renew signing assets for iOS/macOS apps.
Preconditions
- Auth is configured (
asc auth loginorASC_*env vars). - You know the bundle identifier and target platform.
- You have a CSR file for certificate creation.
Workflow
- Create or find the bundle ID:
asc bundle-ids list --paginateasc bundle-ids create --identifier "com.example.app" --name "Example" --platform IOS
- Configure bundle ID capabilities:
asc bundle-ids capabilities list --bundle "BUNDLE_ID"asc bundle-ids capabilities add --bundle "BUNDLE_ID" --capability ICLOUD- Add capability settings when required:
--settings '[{"key":"ICLOUD_VERSION","options":[{"key":"XCODE_13","enabled":true}]}]'
- Create a signing certificate:
asc certificates list --certificate-type IOS_DISTRIBUTIONasc certificates create --certificate-type IOS_DISTRIBUTION --csr "./cert.csr"
- Create a provisioning profile:
asc profiles create --name "AppStore Profile" --profile-type IOS_APP_STORE --bundle "BUNDLE_ID" --certificate "CERT_ID"- Include devices for development/ad-hoc:
asc profiles create --name "Dev Profile" --profile-type IOS_APP_DEVELOPMENT --bundle "BUNDLE_ID" --certificate "CERT_ID" --device "DEVICE_ID"
- Download the profile:
asc profiles download --id "PROFILE_ID" --output "./profiles/AppStore.mobileprovision"
Rotation and cleanup
- Revoke old certificates:
asc certificates revoke --id "CERT_ID" --confirm
- Delete old profiles:
asc profiles delete --id "PROFILE_ID" --confirm
Shared team storage with asc signing sync
Use this when you want a lightweight, non-interactive alternative to fastlane match for encrypted git-backed certificate/profile storage.
# Push current ASC signing assets into an encrypted git repo
asc signing sync push \
--bundle-id "com.example.app" \
--profile-type IOS_APP_STORE \
--repo "git@github.com:team/certs.git" \
--password "$MATCH_PASSWORD"
# Pull and decrypt them into a local directory
asc signing sync pull \
--repo "git@github.com:team/certs.git" \
--password "$MATCH_PASSWORD" \
--output-dir "./signing"
Notes:
--passwordfalls back toASC_MATCH_PASSWORD.- The encrypted repo follows a familiar match-style git layout for certs and profiles.
pullwrites files to disk; keychain import or profile installation is a separate step.
Notes
- Always check
--helpfor the exact enum values (certificate types, profile types). - Use
--paginatefor large accounts. --certificateaccepts comma-separated IDs when multiple certificates are required.- Device management uses
asc devicescommands (UDID required).
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/asc-signing-setup-ms47vqk1/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/asc-signing-setup-ms47vqk1' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/asc-signing-setup-ms47vqk1/download' --output '.skill-downloads/asc-signing-setup-ms47vqk1/SKILL.md.part' && mv '.skill-downloads/asc-signing-setup-ms47vqk1/SKILL.md.part' '.skill-downloads/asc-signing-setup-ms47vqk1/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/asc-signing-setup-ms47vqk1/SKILL.md' && test -s '.skill-downloads/asc-signing-setup-ms47vqk1/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/asc-signing-setup' && cp -R '.skill-downloads/asc-signing-setup-ms47vqk1' '.claude/skills/asc-signing-setup'Cursor
test -f '.skill-downloads/asc-signing-setup-ms47vqk1/SKILL.md' && test -s '.skill-downloads/asc-signing-setup-ms47vqk1/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/asc-signing-setup' && cp -R '.skill-downloads/asc-signing-setup-ms47vqk1' '.cursor/skills/asc-signing-setup'Codex
test -f '.skill-downloads/asc-signing-setup-ms47vqk1/SKILL.md' && test -s '.skill-downloads/asc-signing-setup-ms47vqk1/SKILL.md' && mkdir -p '.agents/skills' && test ! -e '.agents/skills/asc-signing-setup' && cp -R '.skill-downloads/asc-signing-setup-ms47vqk1' '.agents/skills/asc-signing-setup'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/asc-signing-setup-ms47vqk1'openskills read 'asc-signing-setup-ms47vqk1'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/asc-signing-setup-ms47vqk1/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
Configure a Chat Channel with SecretRefs
DevOps
Set up chat channels using non-interactive commands, with secrets only as SecretRefs. Covers gather, mutate, repair, and prove steps for reliable delivery.
Investigate ClickHouse CI Failures
DevOps
Investigate a ClickHouse CI failure end-to-end from a PR or S3 report URL. Fetches failed tests, classifies flaky vs real regression, and checks for existing issues/fixes.
Ansible PR Review
DevOps
Reviews an Ansible PR following the project's standardized process, including changelog checks, test coverage validation, and feedback tracking.