Agent skill

App Release

by glebis in glebis/claude-skills

End-to-end pipeline for releasing an iOS / watchOS app to TestFlight and the App Store.

MITAuto-check passedMobile

Install App Release

skills CLI
$ npx skills add glebis/claude-skills --skill app-release -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install glebis/claude-skills app-release --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/glebis/claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/app-release .claude/skills/app-release && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
app-release
GitHub stars
389
Token cost
~1.4k tokens
SKILL.md length
689 words
Files
3 (incl. references)
Skills in repo
91
Repo updated
First seen
Licence
MIT

At a glance

End-to-end pipeline for releasing an iOS / watchOS app to TestFlight and the App Store.

  • Works in 9 steps: Inventory the gates. List what is… → CloudKit → Production (if the app uses… → Export compliance. Bake… → …
  • The user wants to publish
  • SKILL.md covers When to use, The gates (run in order;…, Guardrails (non-negotiable) and Tooling notes
  • Calls xcodebuild

What it does

App Release is an agent skill from glebis/claude-skills. End-to-end pipeline for releasing an iOS / watchOS app to TestFlight and the App Store. Use when the user wants to publish, ship, or release an iOS/watchOS app, get a build onto TestFlight, archive and upload via xcodebuild, deploy a CloudKit schema to Production, set App Privacy or export compliance, mint a Distribution certificate, or work through App Store Connect / Apple Developer portal steps. Triggers on 'continue publishing', 'ship the app to TestFlight', 'release the iOS app', 'upload a build', 'deploy…

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/gotchas.md` and `references/pipeline.md`).

It sits in Mobile, covering App store release and iOS development. It works with App Store Connect, iOS, Xcode and macOS. The repository describes itself as: Collection of Claude Code skills for enhanced AI workflows. The licence is MIT.

When your agent uses it

  • The user wants to publish
  • Release an iOS/watchOS app
  • Get a build onto TestFlight
  • Archive and upload via xcodebuild

Example prompts

  • “continue publishing”
  • “ship the app to TestFlight”
  • “release the iOS app”
  • “/app-release”

Workflow steps

9 steps, taken from the first numbered list in SKILL.md.

  1. Inventory the gates. List what is actually open (issue tracker, or derive
  2. CloudKit → Production (if the app uses CloudKit). Development indexes/record
  3. Export compliance. Bake ITSAppUsesNonExemptEncryption: false into every
  4. App Privacy. Audit the code for analytics / third-party SDKs / external
  5. Privacy Policy + Impressum. App Store requires a hosted privacy-policy URL;
  6. Signing audit. With automatic signing, Xcode mints the Distribution cert +
  7. Archive. xcodebuild archive the iPhone scheme that embeds the Watch app,
  8. Export + upload to TestFlight. xcodebuild -exportArchive with method
  9. Hand off the device test. The final TestFlight verification (install the

What it can do on your machine

Read from SKILL.md and the folder at commit 7524dff. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • xcodebuild

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

App Release loads about 1.4k tokens when it runs, and up to ~4.7k if it reads all its reference files. Until then it costs about 183 tokens; SKILL.md has 689 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~183
When it runs · the whole SKILL.md, loaded when a task matches
~1.4k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~4.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from glebis/claude-skills at commit 7524dff, republished under its MIT licence (© glebis). 689 words, ~1,446 tokens.

Download SKILL.mdSave it as .claude/skills/app-release/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
app-release
description
End-to-end pipeline for releasing an iOS / watchOS app to TestFlight and the App Store. Use when the user wants to publish, ship, or release an iOS/watchOS app, get a build onto TestFlight, archive and upload via xcodebuild, deploy a CloudKit schema to Production, set App Privacy or export compliance, mint a Distribution certificate, or work through App Store Connect / Apple Developer portal steps. Triggers on 'continue publishing', 'ship the app to TestFlight', 'release the iOS app', 'upload a build', 'deploy CloudKit to production', 'App Privacy labels', 'distribution signing', or any cryptic Apple upload error (cloud signing, 90057 missing CFBundleShortVersionString, 90474 orientation). macOS and Xcode only.

App Release (iOS / watchOS → TestFlight / App Store)

Drive an iOS/watchOS app from "production path unstarted" to a Distribution-signed build processing in TestFlight. The hard part is not any single step — it is that the release path spans three disconnected web portals (Apple Developer, App Store Connect, CloudKit Dashboard) plus CLI signing arcana, and each gate hides a silent failure discoverable only after the previous one passes. Treat the whole thing as an airlock checklist: each gate must verifiably seal before the next opens.

When to use

Releasing/publishing/shipping an iOS or watchOS app; getting a build to TestFlight; archiving + uploading; deploying CloudKit schema to Production; filling App Privacy or export compliance; distribution signing; or debugging an Apple upload rejection.

The gates (run in order; verify each before moving on)

Track every gate in the project's issue tracker. Do not assume a gate is closed because a portal shows green — verify the underlying artifact.

  1. Inventory the gates. List what is actually open (issue tracker, or derive from the steps below). Distinguish gates that block TestFlight from gates that block App Store submission — they are different.
  2. CloudKit → Production (if the app uses CloudKit). Development indexes/record types do not exist in Production until an explicit Deploy Schema Changes. Deploy via the dashboard and verify the record type appears in the Production environment. One-way action — confirm with the user first.
  3. Export compliance. Bake ITSAppUsesNonExemptEncryption: false into every shippable target (the app and the watch app), in the source of truth (e.g. XcodeGen project.yml info.properties), so TestFlight never prompts per build.
  4. App Privacy. Audit the code for analytics / third-party SDKs / external networking first. If the developer cannot access user data (e.g. data lives only in the user's private CloudKit), the honest label is Data Not Collected. Set it in App Store Connect. Leave Publish for submission time.
  5. Privacy Policy + Impressum. App Store requires a hosted privacy-policy URL; an EU/German operator also needs an Impressum. Add pages to the product site, deploy, paste the privacy URL into App Store Connect.
  6. Signing audit. With automatic signing, Xcode mints the Distribution cert + App Store profiles at archive/export — no manual portal work. Confirm the team id and CODE_SIGN_STYLE: Automatic.
  7. Archive. xcodebuild archive the iPhone scheme that embeds the Watch app, -allowProvisioningUpdates. (Archive signs with Apple Development; the Distribution cert is minted at the export step.)
  8. Export + upload to TestFlight. xcodebuild -exportArchive with method app-store-connect, automatic signing, and an App Store Connect API key. The key must be Admin role — a Developer-role key cannot cloud-sign and fails with "Cloud signing permission error / no iOS Distribution cert found."
  9. Hand off the device test. The final TestFlight verification (install the processed build, exercise the real feature loop on Production) is a human on-device step. Do not claim it as done.

Read references/pipeline.md for the exact commands, ExportOptions.plist, and verification one-liners for every gate above.

When any step fails with a cryptic Apple error, read references/gotchas.md first — it catalogs the silent failures from real releases (corrupted SwiftPM checkout, Developer-role API key, missing CFBundleShortVersionString, iPad-orientation 90474) with the exact fix.

Show full SKILL.md (175 more words)Show less

Guardrails (non-negotiable)

  • Confirm before one-way production actions: CloudKit Deploy to Production and App Privacy Publish. They affect shipped users / the public product page.
  • Never print secret key values. Keep .p8 keys in ~/.appstoreconnect/; clean up any temp copies after use.
  • Use trash, never rm.
  • Drive logged-in portals via browser automation; never enter Apple credentials. Ask the user to log in once in the automation browser.
  • Leave the on-device feature-loop test and the final Publish / Submit-for-review to the human.
  • Commit only release-related changes in focused commits; never sweep unrelated branch WIP into a release commit.

Tooling notes

  • Portal work (CloudKit Dashboard, App Store Connect, Apple Developer) is best driven through a persistent logged-in browser (e.g. the browser-mate skill) so the user logs in once and the session persists.
  • The heavy build/sign/upload steps belong in the shell (xcodebuild), not GUI clicking — the CLI gives real error output instead of a progress bar. Reserve computer-use/GUI for steps that genuinely need it.
  • Run long xcodebuild steps in the background and poll for ARCHIVE SUCCEEDED / EXPORT SUCCEEDED / Upload succeeded markers.

© glebis, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (references) in app-release of glebis/claude-skills.

  • SKILL.md
  • references/gotchas.md
  • references/pipeline.md

Open the folder on GitHubat commit 7524dff

Compare with similar skills

App Release next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

App Release compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
App Release this skillglebis/claude-skills389—~1.4kAutomated safety check: PassMIT
OdevioOdevio/Odevio-CLI423—~7.6kAutomated safety check: PassMIT
Asc Xcode Buildrorkai/app-store-connect-cli-skills1.1k2 repos~2.1kAutomated safety check: PassMIT
CI CD Setuprshankras/claude-code-apple-skills783—~1.5kAutomated safety check: NotesMIT
App Store Preflight Skillstruongduy2611/app-store-preflight-skills1.4k—~1.4kAutomated safety check: PassMIT
iOS App Store SubmitZestfulPulse/ios-app-store-submit142—~4.7kAutomated safety check: PassMIT

Similar skills

  • Odevio

    Odevio/Odevio-CLI

    Take a Flutter project to an iPhone or the App Store with Odevio - build, sign and publish iOS apps from Windows, Linux or macOS with no Mac and no Xcode.

    423 GitHub stars~7.6k tokensUpdated 14 days ago
    MobileAuto-check passed
  • Asc Xcode Build

    rorkai/app-store-connect-cli-skills

    Build, archive, generate export options, export, upload, and manage Xcode version/build numbers with the current asc xcode helpers.

    1.1k GitHub starsUsed in 2 repos~2.1k tokens
    MobileAuto-check passed
  • CI CD Setup

    rshankras/claude-code-apple-skills

    Generate CI/CD configuration for automated builds, tests, and distribution of iOS/macOS apps.

    783 GitHub stars~1.5k tokensUpdated 2 mo ago
    DevOps & CloudAuto-check: notes
  • App Store Preflight Skills

    truongduy2611/app-store-preflight-skills

    Scan an iOS/macOS Xcode project for common App Store rejection patterns before submission.

    1.4k GitHub stars~1.4k tokensUpdated 4 mo ago
    MobileAuto-check passed
  • iOS App Store Submit

    ZestfulPulse/ios-app-store-submit

    Build, sign, and submit a Flutter/iOS app to the App Store Connect — covers Xcode archive/export, code signing (including headless-Mac keychain workarounds), the asc CLI for App Store Connect…

    142 GitHub stars~4.7k tokensUpdated 7 days ago
    MobileAuto-check passed
  • Remote Installer

    icodesign/remote-installer

    Put an iOS or Android build on a real phone or tablet over the air with the remote-installer CLI — it validates the build, opens a temporary HTTPS tunnel, and prints one or more install URLs plus QR…

    106 GitHub stars~4k tokensUpdated 8 days ago
    MobileAuto-check passed

More from glebis/claude-skills

All 91 skills in this repo
  • Runs a human-first workflow for labeling PII spans in a transcript, then scores inter-annotator agreement and drafts an adjudicated gold set.

    389 GitHub stars~1.3k tokensUpdated 12 days ago
    Auto-check passed
  • Automates a dedicated, logged-in Chrome instance per profile without ever closing the user's own open tabs or browser windows.

    389 GitHub stars~973 tokensUpdated 12 days ago
    Auto-check passed
  • Deep Research

    glebis/claude-skills

    This skill should be used when conducting comprehensive research on any topic using the OpenAI Deep Research API.

    389 GitHub stars~2.6k tokensUpdated 12 days ago
    Auto-check: notes
  • Elimination Research

    glebis/claude-skills

    This skill should be used for elimination-style research where the user wants to choose from a shortlist of products, tools, services, vendors, or other options using explicit criteria, numeric…

    389 GitHub stars~1.6k tokensUpdated 12 days ago
    Auto-check passed
  • Narrated HTML Presentations

    glebis/claude-skills

    Generates a self-contained HTML presentation with article and slides modes, ElevenLabs voiceover narration and optional GPT Image 2 illustrations.

    389 GitHub stars~2.3k tokensUpdated 12 days ago
    Auto-check: notes
  • Writes fictional but realistic coaching or therapy session transcripts for evals, demos and few-shot examples, in several modalities and export formats.

    389 GitHub stars~2.9k tokensUpdated 12 days ago
    Auto-check passed

Categories

Questions about App Release

What does App Release do?

End-to-end pipeline for releasing an iOS / watchOS app to TestFlight and the App Store. App Release is an agent skill from glebis/claude-skills. End-to-end pipeline for releasing an iOS / watchOS app to TestFlight and the App Store.

When should I use App Release?

App Release fits situations like: the user wants to publish; release an iOS/watchOS app; get a build onto TestFlight; archive and upload via xcodebuild.

How do I install App Release in Claude Code?

Run `npx skills add glebis/claude-skills --skill app-release -a claude-code`. Or copy the skill folder (app-release in glebis/claude-skills) into .claude/skills/app-release in your project. Claude Code loads it when a task matches its description.

How do I install App Release in Codex?

Run `npx skills add glebis/claude-skills --skill app-release -a codex`. Or copy the skill folder (app-release in glebis/claude-skills) into .agents/skills/app-release in your project. Codex loads it when a task matches its description.

Can I use App Release in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add glebis/claude-skills --skill app-release -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/app-release, .gemini/skills/app-release, .github/skills/app-release and .opencode/skills/app-release in your project.

What does App Release need to run?

Going by SKILL.md and its folder, App Release needs the command-line tools its instructions call (xcodebuild).

Does App Release access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is App Release safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does App Release use?

App Release is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does App Release use?

About 1.4k tokens (SKILL.md is roughly 5.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3.2k tokens, read only when the agent opens those files.

What are the alternatives to App Release?

Skills that share tags, products or a category with App Release: Odevio (Odevio/Odevio-CLI, 423 stars), Asc Xcode Build (rorkai/app-store-connect-cli-skills, 1.1k stars), CI CD Setup (rshankras/claude-code-apple-skills, 783 stars) and App Store Preflight Skills (truongduy2611/app-store-preflight-skills, 1.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains App Release?

glebis (a GitHub user) maintains it in glebis/claude-skills, which has 389 GitHub stars. The repository holds 91 skills in this directory. The repository was last updated on September 26, 2026.

Source: glebis/claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.