Agent skill · Security

store-growth-audit

Stage-by-stage audit of an app's App Store growth machinery against a 54-item P0–P9 playbook — every item scored from an App Store Connect MCP call, a codebase check, or an explicit question to the user, then routed to the skill or command that fixes it. Read-only on App Store Connect. Use for a growth audit or scorecard, a pre-launch growth plan, a quarterly re-audit, or "which growth levers am I missing.

rshankrasgithub.com/rshankrasGitHub ↗
claude-codecan modify filesMIT
Install
npx skills add rshankras/claude-code-apple-skills --skill store-growth-audit --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 4
SKILL.md size: 14 KB
Bundled scripts: none
Allowed tools: ReadWriteGlobGrepAskUserQuestionmcp__asc-metadata__list_appsmcp__asc-metadata__get_metadatamcp__asc-metadata__list_localesmcp__asc-metadata__get_app_pricingmcp__asc-metadata__list_price_pointsmcp__asc-metadata__get_availabilitymcp__asc-metadata__list_iap
Path: skills/growth/store-growth-audit/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 589
Language: Swift

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Store Growth Audit Walk an app — new or live — through the full App Store growth playbook, phase by phase, and produce a scorecard: what's installed, what's missing, what to do next, and who fixes it. > The invariant: **every item has a detection rule**. Status comes from an ASC read, a codebase > check, or an explicit question — never from vibes. If the user doesn't know, the item is > 🟠 *unverified*, not assumed ✅. ## Where it fits (read the seams) - **Not `store-signals`.** That is the continuous *signal → backlog* loop: are the numbers moving, did last cycle's bets pay off? This is the *structural* audit: is the machinery even installed? Run this quarterly (or pre-launch); run store-signals monthly. Trend questions route there. - **Not `analytics-interpretation`.** Metric-quality judgments ("is 3.2% conversion good?") route there; this skill only records the baseline and whether benchmarks were checked. - **Fixes never happen here.** Every 🔴/🟠 routes to a named sibling skill and (when driven from SwiftShip) an `/apple:*` command. This skill detects, scores, and routes. Read-only on ASC. ## When This Skill Activates - "Audit my app's growth / store presence / what levers am

What's inside
Steps it walks through
  1. Where it fits (read the seams)
  2. When This Skill Activates
  3. The Model: P0–P9
  4. Reference Files
  5. Audit Process
  6. Item Record Format
  7. Scoring & Maturity
  8. Modes: Existing vs Pre-Launch
  9. Scoped Runs (single phase)
  10. Output Format
  11. Routing Map
  12. Caveats
Ships with 3 files
  • audit-checklist-p0-p4.md
  • audit-checklist-p5-p9.md
  • detection-playbook.md
More from claude-code-apple-skills
All skills →
About this skill
What does the store-growth-audit skill do?

Stage-by-stage audit of an app's App Store growth machinery against a 54-item P0–P9 playbook — every item scored from an App Store Connect MCP call, a codebase check, or an explicit question to the user, then routed to the skill or command that fixes it. Read-only on App Store Connect. Use for a growth audit or scorecard, a pre-launch growth plan, a quarterly re-audit, or "which growth levers am I missing.

How do I install it?

Run `npx skills add rshankras/claude-code-apple-skills --skill store-growth-audit --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From rshankras/claude-code-apple-skills, a repository with 589 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going