Skip to content
Agentmart
Submit a tool

app-store-readiness

Use when auditing a prepared iOS release for App Store or TestFlight submission risk, including metadata, privacy, capabilities, and reviewer-facing behavior.

Skill by phrypy

IndexedMIT★ 7
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/phrypy-app-store-readiness

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Use when auditing a prepared iOS release for App Store or TestFlight submission risk, including metadata, privacy, capabilities, and reviewer-facing behavior.

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/app-store-readiness

What's inside

Skill name
app-store-readiness
Description
Use when auditing a prepared iOS release for App Store or TestFlight submission risk, including metadata, privacy, capabilities, and reviewer-facing behavior.
License
MIT
Instructions
49 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

# App Store Readiness

Submission quality is product quality plus review hygiene.

This is the submission audit gate. It does not archive, upload, or release the build. Use `solo-ios-release-flow` for the release sequence and `ship-ios-build-one-command` for the archive-to-upload operation.

## Audit In This Order

1. the app build itself
2. store metadata versus real behavior
3. privacy, entitlements, and capabilities
4. subscriptions, legal URLs, and account flows
5. screenshots and review notes

## Metadata Rules

- never claim a feature is live if it is hidden, disabled, or "coming soon"
- title, subtitle, promo text, and description should match the shipped build
- if a capability is conditional or manual, describe it honestly

## Review Risk Areas

- unused background modes
- incomplete privacy manifests
- entitlement drift
- broken paywalls or restore flows
- misleading screenshots
- half-finished imports, notifications, or sync claims

## iCloud And Restore Rules

- do not label a status refresh as a restore
- destructive or recovery actions need explicit user language
- if a restore path exists, explain exactly what device state it rebuilds and when

## Pre-Submit Checks

- release build succeeds
- app opens and core loop works on device
- purchase and restore flows are understandable
- notification and permission prompts appear at sensible moments
- legal links resolve
- support path exists

## Final Standard

If a reviewer or first-time user could misunderstand what the app does, the submission is not ready yet.

From phrypy/ios-app-playbook, MIT.

More from phrypy/ios-app-playbook

Signals

Stars
7
Forks
2
Open issues
0
Last commit (this folder)
Jun 23, 2026 (4 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from phrypy

Cite this page

app-store-readiness skill. Agent Mart. https://agentmart.dev/skills/phrypy-app-store-readiness (last updated 2026-10-24)