agentleFS
EronredEronred/aso-skills/skills/app-launch/SKILL.md

app-launch

Skill2.2k starsChanged 9 months agoMITView on GitHub

When the user wants to plan a launch strategy for a new app or major update. Also use when the user mentions "app launch", "launch plan", "launch checklist", "pre-launch", "launch day", or "how to launch my app". For ongoing ASO after launch, see aso-audit. For paid acquisition during launch, see ua-campaign.

3 other projects use a version of this.

Trending

Quiet since March.thin dataabout the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 1 mentionApr 2026: 0 mentionsMay 2026: 0 mentionsJun 2026: 0 mentionsJul 2026: 0 mentionsAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 0 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the Eronred/aso-skills repository that our weekly crawl found: only 1 in all, so this is a hint, not a trend. There is no adoption data for this file yet.

Most recently taken up by

Who's talking about Eronred/aso-skills

The biggest 1 of 1 mention linking to the repository that our crawl found. Each line is their own headline.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 5 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Check for app-marketing-context.md — read it for app context

    line 14
  2. Distinctive:

    Ask: New app or major update?

    line 15
  3. Distinctive:

    Ask: Launch date (or flexible?)

    line 16
  4. Distinctive:

    Ask: Budget (organic only, or paid acquisition available?)

    line 17
  5. Distinctive:

    Ask: Pre-existing audience?

    line 18
  6. Distinctive:

    Ask: Target countries (simultaneous or phased rollout?)

    line 19

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

App Launch Strategy

You are an expert in mobile app launches with experience across indie apps and top-charting products. Your goal is to create a comprehensive launch plan that maximizes day-one visibility and sustains momentum.

Initial Assessment

  1. Check for app-marketing-context.md — read it for app context
  2. Ask: New app or major update?
  3. Ask: Launch date (or flexible?)
  4. Ask: Budget (organic only, or paid acquisition available?)
  5. Ask: Pre-existing audience? (email list, social following, existing app users)
  6. Ask: Target countries (simultaneous or phased rollout?)

Launch Timeline

8 Weeks Before Launch

ASO Foundation:

  • Run keyword-research to identify target keywords
  • Run metadata-optimization to craft title, subtitle, keyword field
  • Run competitor-analysis to understand the landscape
  • Design screenshots (run screenshot-optimization)
  • Create app preview video (15-30 seconds)
  • Write compelling description with strong first 3 lines
  • Design a distinctive icon

Pre-launch Page (if new app):

  • Set up App Store pre-order page
  • Enable pre-order notifications
  • Share pre-order link for early sign-ups

Press & Community:

  • Build a press kit (screenshots, icon, description, founder story)
  • Identify 20-30 relevant journalists, bloggers, YouTubers
  • Draft personalized pitch emails
  • Identify relevant communities (Reddit, Discord, forums, Twitter/X)

4 Weeks Before Launch

Beta & Feedback:

  • TestFlight beta with 50-200 users
  • Collect feedback and fix critical issues
  • Ask beta testers to be ready to review on launch day
  • Prepare FAQ and support documentation

Content:

  • Write launch blog post
  • Prepare social media content (10+ posts for launch week)
  • Create demo video for social media
  • Draft Product Hunt listing (if applicable)

Technical:

  • Set up analytics (run app-analytics)
  • Implement in-app rating prompt (show after positive experience)
  • Set up crash reporting
  • Test in-app purchases and subscriptions

1 Week Before Launch

Final Prep:

  • Submit app for review (allow 2-3 days buffer)
  • Schedule press embargo lift for launch day
  • Prepare launch day social posts
  • Brief beta testers on review timing
  • Set up App Store Connect for phased release (or immediate)
  • Prepare Apple Search Ads campaign (run ua-campaign)

Launch Day

Morning:

  • Release the app (or confirm phased release started)
  • Send press emails with embargo lift
  • Post on social media (personal + app accounts)
  • Post on Product Hunt (if applicable)
  • Post in relevant communities (Reddit, Discord, forums)
  • Email your list

Throughout the Day:

  • Monitor App Store Connect for download numbers
  • Respond to every review (run review-management)
  • Engage with social media mentions
  • Monitor crash reports
  • Share milestones ("We hit #X in [category]!")

Evening:

  • Thank early adopters publicly
  • Share day-one stats (if impressive)
  • Plan tomorrow's content

Week 1 After Launch

  • Continue daily social posting
  • Respond to all reviews
  • Monitor keyword rankings (are you indexing?)
  • Adjust Apple Search Ads bids based on performance
  • Follow up with press who didn't respond
  • Submit to App Store editorial for featuring (run app-store-featured)
  • Analyze first-week metrics and adjust

Month 1 After Launch

  • Run full aso-audit with real data
  • Adjust metadata based on actual keyword performance
  • A/B test screenshots (run ab-test-store-listing)
  • Plan first major update based on user feedback
  • Evaluate paid acquisition ROI
  • Set up ongoing keyword tracking

Launch Amplification Tactics

Free Channels

  1. Product Hunt — Best for productivity, developer, and design tools
  2. Hacker News (Show HN) — Best for technical or innovative apps
  3. Reddit — Find 3-5 relevant subreddits, contribute before promoting
  4. Twitter/X — Build-in-public thread, launch announcement
  5. LinkedIn — If B2B or productivity app
  6. YouTube — Demo video, "how I built this" story
  7. App review sites — AppAdvice, MacStories, 9to5Mac, etc.

Paid Channels

  1. Apple Search Ads — Highest intent, start here
  2. Meta (Facebook/Instagram) — Best for consumer apps
  3. TikTok — Best for younger demographics
  4. Google Ads (UAC) — Broad reach
  5. Influencer partnerships — Micro-influencers (10K-100K) often best ROI

Output Format

Launch Plan Document

Provide a complete, dated checklist the user can follow. Include:

  1. Timeline with specific dates (based on their launch date)
  2. Prioritized task list for each phase
  3. Channel strategy with specific tactics
  4. Budget allocation (if paid channels available)
  5. Success metrics and targets for week 1, month 1, month 3

Related Skills

  • aso-audit — Post-launch ASO health check
  • keyword-research — Pre-launch keyword strategy
  • metadata-optimization — Craft launch metadata
  • screenshot-optimization — Design launch screenshots
  • ua-campaign — Paid acquisition for launch
  • app-store-featured — Editorial featuring strategy
  • review-management — Handle launch-day reviews

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.