Automated summary
Manages the App Store Connect build lifecycle through the asc CLI: locating the right build, tracking processing state, publishing to TestFlight or the App Store, and expiring old builds.
Strengths
- Covers the full lifecycle: latest build lookup, next build number, and a sorted list of recent builds
- Provides end-to-end publish flows (asc publish testflight / appstore) with --wait, --poll-interval, and --timeout options
- Cleanup is a two-step dry-run then --confirm process, reducing accidental deletions
- Commands are explicit and copy-pasteable, with platform and version parameters included
Limitations
- Assumes the asc CLI is already installed and authenticated against App Store Connect
- Does not explain handling of processing failures or rejected builds
- Notes that asc builds upload only prepares upload operations, without detailing that workflow
Use it when you need to wait for build processing, find the latest build for a version, or purge old builds from an app.
Do not use it for signing, certificates, or provisioning profiles, which are handled by other tooling.
Security analysis
CautionThe skill contains legitimate App Store Connect build lifecycle commands and does not exfiltrate data, use obfuscated payloads, or disable safety. However, it instructs agents to run potentially destructive and irreversible operations such as expiring builds and submitting to the App Store, so it warrants caution rather than being classified as fully safe.
- •Includes destructive/irreversible operations (`asc builds expire-all --confirm`, `asc builds expire --confirm`) and App Store submission (`--submit --confirm`) without declared tool restrictions or explicit guardrails beyond dry-run examples.
- •No allowed-tools are declared, so an agent may execute these CLI commands with broader permissions than necessary if it has shell access.
Examples
Check whether my latest iOS build for version 1.2.3 has finished processing on App Store Connect and tell me its status.Show me which builds older than 90 days would be expired for app 123456789, without actually expiring anything yet.Publish ./build/app.ipa to TestFlight group GROUP_ID for my app and wait until processing completes.name: asc-build-lifecycle description: Track build processing, find latest builds, and clean up old builds with asc. Use when managing build retention or waiting on processing.
asc build lifecycle
Use this skill to manage build state, processing, and retention.
Find the right build
- Latest build:
asc builds info --app "APP_ID" --latest --version "1.2.3" --platform IOS
- Next safe build number:
asc builds next-build-number --app "APP_ID" --version "1.2.3" --platform IOS
- Recent builds:
asc builds list --app "APP_ID" --sort -uploadedDate --limit 10
Inspect processing state
asc builds info --build-id "BUILD_ID"
Distribution flows
- Prefer end-to-end:
asc publish testflight --app "APP_ID" --ipa "./app.ipa" --group "GROUP_ID" --waitasc publish appstore --app "APP_ID" --ipa "./app.ipa" --version "1.2.3" --wait --submit --confirm
Cleanup
- Preview expiration:
asc builds expire-all --app "APP_ID" --older-than 90d --dry-run
- Apply expiration:
asc builds expire-all --app "APP_ID" --older-than 90d --confirm
- Single build:
asc builds expire --build-id "BUILD_ID" --confirm
Notes
asc builds uploadprepares upload operations only; useasc publishfor end-to-end flows.- For long processing times, use
--wait,--poll-interval, and--timeoutwhere supported.
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-build-lifecycle-ms47vqko/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-build-lifecycle-ms47vqko' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/asc-build-lifecycle-ms47vqko/download' --output '.skill-downloads/asc-build-lifecycle-ms47vqko/SKILL.md.part' && mv '.skill-downloads/asc-build-lifecycle-ms47vqko/SKILL.md.part' '.skill-downloads/asc-build-lifecycle-ms47vqko/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-build-lifecycle-ms47vqko/SKILL.md' && test -s '.skill-downloads/asc-build-lifecycle-ms47vqko/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/asc-build-lifecycle' && cp -R '.skill-downloads/asc-build-lifecycle-ms47vqko' '.claude/skills/asc-build-lifecycle'Cursor
test -f '.skill-downloads/asc-build-lifecycle-ms47vqko/SKILL.md' && test -s '.skill-downloads/asc-build-lifecycle-ms47vqko/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/asc-build-lifecycle' && cp -R '.skill-downloads/asc-build-lifecycle-ms47vqko' '.cursor/skills/asc-build-lifecycle'Codex
test -f '.skill-downloads/asc-build-lifecycle-ms47vqko/SKILL.md' && test -s '.skill-downloads/asc-build-lifecycle-ms47vqko/SKILL.md' && mkdir -p '.agents/skills' && test ! -e '.agents/skills/asc-build-lifecycle' && cp -R '.skill-downloads/asc-build-lifecycle-ms47vqko' '.agents/skills/asc-build-lifecycle'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-build-lifecycle-ms47vqko'openskills read 'asc-build-lifecycle-ms47vqko'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-build-lifecycle-ms47vqko/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.