auditing-appstore-readiness — Claude Code skill: audit and install
auditing-appstore-readiness is a Claude Code skill that checks an iOS app before an App Store or TestFlight submission. It reviews the project, release archive, runtime behaviour, and App Store Connect setup.
no license 100 installs ★ 4 updated 2026-09-14
npx skills add tristanmanchester/agent-skills --skill auditing-appstore-readiness -a claude-codeWhat auditing-appstore-readiness does
The skill examines an iOS project, its release archive, behaviour on launch, and its App Store Connect setup. It separates confirmed submission blockers from items that still need evidence from a build, device, account, or policy check.
An optional source inventory runs through scripts/inspect_repo.py. It reads a bounded set of metadata and writes JSON marked NOT_ASSESSED; it does not run project code, so that output cannot establish submission readiness. Python 3.10 or later is required for this inventory.
Archive and runtime checks need an authorised macOS environment with Xcode or CI. Current policy and App Store Connect checks need the relevant access. Findings use verified, blocked, unverified, or not applicable statuses, with evidence, impact, a fix, and a follow-up check recorded for each finding.
What it helps with
- review an iOS project before submission
- separate proven blockers from checks still awaiting evidence
- inspect a release archive and device behaviour
- record App Store Connect and policy check status
Example prompts for the agent
- Audit my iOS app before I submit it to the App Store.
- Review what is verified for this TestFlight build and what still needs checking.
- Check the app archive and App Store Connect setup before submission.
How to install auditing-appstore-readiness
1Skills CLI (Vercel)
npx skills add tristanmanchester/agent-skills --skill auditing-appstore-readiness -a claude-code2Manually: put the files in place
~/.claude/skills/auditing-appstore-readiness/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/auditing-appstore-readiness/
1Skills CLI (Vercel)
npx skills add tristanmanchester/agent-skills --skill auditing-appstore-readiness -a codex2Manually: put the files in place
.agents/skills/auditing-appstore-readiness/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add tristanmanchester/agent-skills --skill auditing-appstore-readiness -a cursor2Manually: put the files in place
.cursor/skills/auditing-appstore-readiness/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install tristanmanchester/agent-skills auditing-appstore-readiness2Manually: put the files in place
.github/skills/auditing-appstore-readiness/SKILL.md1Skills CLI (Vercel)
npx skills add tristanmanchester/agent-skills --skill auditing-appstore-readiness -a gemini-cli2Platform CLI
gemini skills install https://github.com/tristanmanchester/agent-skills --path auditing-appstore-readinessManually: put the files in place
.devin/skills/auditing-appstore-readiness/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add tristanmanchester/agent-skills --skill auditing-appstore-readiness -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about auditing-appstore-readiness
How do I install auditing-appstore-readiness in Claude Code?
Run npx skills add tristanmanchester/agent-skills --skill auditing-appstore-readiness -a claude-code. The skill file is at ~/.claude/skills/auditing-appstore-readiness/SKILL.md.
What does auditing-appstore-readiness do?
It reviews an iOS project's source, release archive, runtime behaviour, and App Store Connect setup. It marks established blockers separately from checks that still need evidence.
What does auditing-appstore-readiness require?
Source inventory requires Python 3.10 or later. Archive and runtime checks need an authorised macOS environment with Xcode or CI; policy and App Store Connect checks need the relevant access.