Agent skill · Security

growth

Growth skills for indie Apple developers — user acquisition, analytics interpretation, press/media outreach, community building, and indie business operations. Also covers the stage-by-stage store-growth audit and the post-launch store-signals loop. Use when user asks about growing their app, auditing growth levers, understanding metrics, getting press coverage, or running an indie dev business.

rshankrasgithub.com/rshankrasGitHub ↗
claude-coderead-onlyMIT
Install
npx skills add rshankras/claude-code-apple-skills --skill growth --agent claude-code

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

Facts
Files in the skill folder: 13
SKILL.md size: 3 KB
Bundled scripts: none
Allowed tools: ReadGlobGrepAskUserQuestionWebSearch
Path: skills/growth/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

# Growth Skills Growth skills for indie Apple developers — from analytics interpretation to press outreach to community building. Covers the non-code aspects of building a sustainable app business. ## When This Skill Activates Use this skill when the user: - Asks about growing their app or user acquisition - Wants to understand app metrics or analytics - Asks about press/media outreach or getting reviews - Wants to build a community around their app - Asks about indie business operations (LLC, taxes, hiring) - Mentions growth strategy, marketing, or user engagement - Wants data-driven guidance on what to improve next ## Available Skills ### 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 ASC read, a codebase check, or an explicit question, then routed to the skill that fixes it. Read-only; works for live apps (audit) and pre-launch apps (growth plan). ### store-signals/ Close the post-launch loop — turn a live app's App Store signals (reviews, analytics, sales, crashes, listing conversion) into a metric-tagged backlog, and verify whether last cycle's changes moved the metric they promised t

What's inside
Steps it walks through
  1. When This Skill Activates
  2. Available Skills
  3. store-growth-audit/
  4. store-signals/
  5. analytics-interpretation/
  6. press-media/
  7. community-building/
  8. indie-business/
  9. How to Use
Ships with 12 files
  • analytics-interpretation/SKILL.md
  • analytics-interpretation/metrics-reference.md
  • community-building/SKILL.md
  • indie-business/SKILL.md
  • press-media/SKILL.md
  • press-media/pitch-templates.md
  • store-growth-audit/SKILL.md
  • store-growth-audit/audit-checklist-p0-p4.md
  • store-growth-audit/audit-checklist-p5-p9.md
  • store-growth-audit/detection-playbook.md
  • store-signals/SKILL.md
  • store-signals/signals-ledger.md
More from claude-code-apple-skills
All skills →
About this skill
What does the growth skill do?

Growth skills for indie Apple developers — user acquisition, analytics interpretation, press/media outreach, community building, and indie business operations. Also covers the stage-by-stage store-growth audit and the post-launch store-signals loop. Use when user asks about growing their app, auditing growth levers, understanding metrics, getting press coverage, or running an indie dev business.

How do I install it?

Run `npx skills add rshankras/claude-code-apple-skills --skill growth --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