agentleFS
Sign inStart free
moasqmoasq/ios-dev-agent/.agents/skills/asc-signing-setup/SKILL.md

asc-signing-setup

Skill4 starsChanged 6 months agoMITView on GitHub

Use when setting up or repairing App Store signing: bundle IDs, capabilities, certificates, provisioning profiles, encrypted signing sync, export options, or archive signing failures.

9 other projects use a version of this, 9 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

8 rules. 6 are common, 0 are distinctive, and 2 are very specific to this project.

  • 6

    Common

    Most of the 9 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Common:

    Use this skill when you need to create or renew signing assets for iOS/macOS apps.

    line 8
  2. Common:

    Create or find the bundle ID:

    line 16
  3. Common:

    Add capability settings when required:

    line 22
  4. Common:

    Create a signing certificate:

    line 24
  5. Common:

    Create a provisioning profile:

    line 27
  6. Common:

    Use this when you want a lightweight, non-interactive alternative to fastlane match for encrypted git-backed certificate/profile storage.

    line 41
  7. Very specific:

    Always check --help for the exact enum values (certificate types, profile types).

    line 64
  8. Very specific:

    Use --paginate for large accounts.

    line 65

“Common” is measured: kept by at least 6 in 10 of the 9 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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 login or ASC_* env vars).
  • You know the bundle identifier and target platform.
  • You have a CSR file for certificate creation.

Workflow

  1. Create or find the bundle ID:
    • asc bundle-ids list --paginate
    • asc bundle-ids create --identifier "com.example.app" --name "Example" --platform IOS
  2. 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}]}]'
  3. Create a signing certificate:
    • asc certificates list --certificate-type IOS_DISTRIBUTION
    • asc certificates create --certificate-type IOS_DISTRIBUTION --csr "./cert.csr"
  4. 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"
  5. 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:

  • --password falls back to ASC_MATCH_PASSWORD.
  • The encrypted repo follows a familiar match-style git layout for certs and profiles.
  • pull writes files to disk; keychain import or profile installation is a separate step.

Notes

  • Always check --help for the exact enum values (certificate types, profile types).
  • Use --paginate for large accounts.
  • --certificate accepts comma-separated IDs when multiple certificates are required.
  • Device management uses asc devices commands (UDID required).

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free