Apple review
Skill markdavidgan/apple-dev-skills/src/mcp/skill-search/test/fixtures/skills/apple-review
App Store review submission and rejection recovery. Use when an app is rejected, needs metadata improvements, or requires guideline compliance checks.From its SKILL.md
npx -y skills add markdavidgan/apple-dev-skills --skill apple-reviewAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
0.8 KB, 123 tokens by cl100k_base, as published. Nobody here has run it
Apple Review
Guidance for passing App Store Review and recovering from rejections.
Common Rejection Reasons
- Guideline 4.0: Design — UI does not follow Human Interface Guidelines
- Guideline 2.1: Performance — crashes or bugs
- Guideline 5.1.1: Privacy — missing usage description keys
Review Response Strategy
When rejected, respond through App Store Connect within 24 hours.
Writing an Appeal
Be concise, reference the specific guideline, and attach screenshots if needed.
Metadata Tips
Ensure your app description accurately reflects current functionality.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most review quality skills give in 123 tokens
Counted across 1,048 of the 1,783 authors here whose files we hold, read 2026-08-07
- Ask questions one at a timein 81 of 1048, across 64 files
- Provide a recommended answer for each questionin 73 of 1048, across 50 files
- Explore the codebase instead of asking answerable questionsin 66 of 1048, across 42 files
- Resolve dependencies between decisions one-by-onein 42 of 1048, across 17 files
- Interview the user relentlessly about the planin 38 of 1048, across 13 files
- Order findings by severityin 31 of 1048
- Resolve each branch of the decision treein 27 of 1048, across 5 files
- Run a grilling sessionin 26 of 1048, across 5 files
- Update CONTEXT.md immediately when a term is resolvedin 26 of 1048, across 11 files
- Propose precise canonical terms for vague languagein 25 of 1048, across 7 files
- Create documentation files lazilyin 24 of 1048, across 5 files
- Assign severity to every findingin 24 of 1048
Said here and by no other author read
- Respond through App Store Connect within 24 hours
- Be concise in appeals
- Reference the specific guideline in appeals
- Attach screenshots if needed
- Ensure app description reflects current functionality
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.