Agent skill · Audited from source
app-launch
skill · eronred/aso-skillsMIT licenceAudited 26 Oct 2026 · source d508dfb48734
Is it safe? Yes — SAFE, grade B (89/100). We read this skill's source at commit d508dfb48734 and found no filesystem, network or shell access and no hard-coded secrets. What it does: 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…
Cite
Cite this page
ModelsAtlas. “app-launch (eronred/aso-skills)”. Retrieved 26 Oct 2026. https://modelsatlas.com/skills/eronred/app-launch
Trust audit
Audit 0.4.1 · source read 26 Oct 2026
SAFE means nothing in the source contradicts what the skill says it does. Grade B is shared by 13,985 of 14,816 audited skills.
What the source does
- FilesystemNone observedNo reads or writes in the source
- NetworkNone observedNo outbound calls in the source
- ShellNone observedNo commands run in the source
- DependenciesPinnedNothing floats
- SecretsNone foundNo keys in source
Five audit layers
| Layer | What we check | Result | Findings |
|---|---|---|---|
L0 Provenance | Repo owner, licence, archive status, activity | PASS | 0 |
L1 Static source | Secrets, path traversal, supply chain, hidden code | NA | 0 |
L2 Instructions | Prompt injection, authority framing, hidden directives | PASS | 0 |
L3 Inventory | The files and declarations match the source | PASS | 0 |
L4 Sandbox | Run in isolation and watch behaviour | SKIPPED why | 0 |
Gates applied: no behavioural pass.
Findings (0)
No findings at any severity. We re-audit when the source changes.
Audit 0.4.1 · source sha d508dfb48734 · 26 Oct 2026Report an issue or request a re-scan
Provenance
Who published it, and what the verdict is pinned to
- Publishereronred GitHub organizationOwner of the repository this skill is read from
- Source foldereronred/aso-skills/skills/app-launchThe exact folder we audited
- LicenceMITAs the repository states it
- Commit pinned for this verdictd508dfb48734A new audit runs when the source changes
- Repository statusNot archivedLast push 19 days ago
- Sandboxed runNot runSkills are read, not executed; layer L4 is skipped
What it tells the agent
Full source on GitHub ↗Its description: 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…
---
name: app-launch
description: 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.
metadata:
version: 1.0.0
---
# 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 reviewsExcerpt, first 5,743 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.
Install
Pinned to the audited commit d508dfb
git clone https://github.com/eronred/aso-skills git -C aso-skills checkout d508dfb48734
The author documents no install command, so this uses the repository directly. Our verdict covers commit d508dfb48734 only.
Works in
The author has not said which agents this skill supports, and we have not tested it in any.
Audit history
Every audit, every source change
- ✓SAFE B 89 / 100
first audit · source
d508dfb48734
README badge
For maintainers · shows the latest audit
[](https://modelsatlas.com/skills/eronred/app-launch/)
The badge shows our verdict and grade for this skill, and links back to this page. It changes when the audit does.
Similar skills
eronred/aso-skills
When the user wants to analyze their own app's actual performance data from App Store Connect — real downloads, revenue, IAP, subscriptions, trials, or country breakdowns synced via Appeeky Connect. Use when the user…
eronred/aso-skills
When the user wants a full ASO health audit, review their App Store listing quality, or diagnose why their app isn't ranking. Also use when the user mentions "ASO audit", "ASO score", "why am I not ranking", "listing…
eronred/aso-skills
When the user wants to set up, optimize, or scale Apple Search Ads (ASA) campaigns — including keyword bidding, match types, campaign structure, Creative Product Sets, CPP routing, and ROAS optimization. Use when the…
eronred/aso-skills
When the user's app or update was rejected by Apple App Review or Google Play Review and they need to diagnose why, fix it, and resubmit fast. Use when the user mentions "app rejected", "App Review rejection",…
eronred/aso-skills
When the user wants to get featured on the App Store or understand the editorial process. Also use when the user mentions "get featured", "App Store editorial", "App of the Day", "Today tab", "Apple featuring", or "how…
eronred/aso-skills
When the user wants to plan, script, produce, or optimize App Store Preview videos or Google Play promo videos — the autoplay videos that show in App Store/Play Store search and product pages. Use when the user mentions…
Add this badge to your README
[](https://modelsatlas.com/skills/eronred/app-launch/)
<a href="https://modelsatlas.com/skills/eronred/app-launch/"><img src="https://modelsatlas.com/skills/eronred/app-launch/badge.svg" alt="ModelsAtlas: SAFE B"></a>
Questions about app-launch
What does the app-launch skill do?
Is app-launch safe to install?
What can app-launch access on my machine?
How current is this page?
Sources
- github.com/eronred/aso-skills/tree/main/skills/app-launch — the audited source at commit d508dfb48734 and every finding aboveObserved · 26 Oct 2026
Spotted something wrong? Report a correction · Methodology
Keep going in your AI
Opens with this page as the source. We add nothing else to the prompt.
- What does the app-launch skill do?
- Is app-launch safe to install?
- What can app-launch access on my machine?