#500 by GitHub stars
appeeky/aso-skills
AI agent skills for App Store Optimization (ASO) and app marketing. Built for indie developers, app marketers, and growth teams who want Cursor, Claude Code, or any Agent Skills-compatible AI assistant to help with keyword research, metadata optimization, competitor analysis, and app growth.
History
Review weekly changes to SKILL.md before updating. Dates mark the weeks in which we observed each version; checks apply to the recorded commits.
View weekly changes
skills/ab-test-store-listing/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
3919d7c27402 → 3919d7c27402
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → 3919d7c27402
No earlier version was observed for comparison.
skills/android-aso/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Network or broad shell
3919d7c27402 → 3919d7c27402
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → 3919d7c27402
No earlier version was observed for comparison.
skills/app-analytics/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
3919d7c27402 → 3919d7c27402
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → 3919d7c27402
No earlier version was observed for comparison.
skills/app-clips/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
3919d7c27402 → 3919d7c27402
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → 3919d7c27402
No earlier version was observed for comparison.
skills/app-icon-optimization/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
3919d7c27402 → 3919d7c27402
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → 3919d7c27402
No earlier version was observed for comparison.
skills/app-launch/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
3919d7c27402 → 3919d7c27402
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → 3919d7c27402
No earlier version was observed for comparison.
skills/app-marketing-context/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
3919d7c27402 → 3919d7c27402
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → 3919d7c27402
No earlier version was observed for comparison.
skills/app-preview-video/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
3919d7c27402 → 3919d7c27402
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → 3919d7c27402
No earlier version was observed for comparison.
skills/app-rejection-recovery/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
3919d7c27402 → 3919d7c27402
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → 3919d7c27402
No earlier version was observed for comparison.
skills/app-store-featured/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
3919d7c27402 → 3919d7c27402
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → 3919d7c27402
No earlier version was observed for comparison.
skills/apple-search-ads/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Network or broad shell
3919d7c27402 → 3919d7c27402
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → 3919d7c27402
No earlier version was observed for comparison.
skills/asc-metrics/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Network or broad shell → After Network or broad shell
3919d7c27402 → 3919d7c27402
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 3919d7c27402
No earlier version was observed for comparison.
skills/aso-audit/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
3919d7c27402 → 3919d7c27402
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → 3919d7c27402
No earlier version was observed for comparison.
skills/aso-router/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
3919d7c27402 → 3919d7c27402
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → 3919d7c27402
No earlier version was observed for comparison.
skills/attribution-setup/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Network or broad shell
3919d7c27402 → 3919d7c27402
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → 3919d7c27402
No earlier version was observed for comparison.
skills/category-positioning/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
3919d7c27402 → 3919d7c27402
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → 3919d7c27402
No earlier version was observed for comparison.
skills/competitor-analysis/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
3919d7c27402 → 3919d7c27402
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → 3919d7c27402
No earlier version was observed for comparison.
skills/competitor-tracking/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Network or broad shell → After Network or broad shell
3919d7c27402 → 3919d7c27402
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → 3919d7c27402
No earlier version was observed for comparison.
skills/crash-analytics/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Network or broad shell
3919d7c27402 → 3919d7c27402
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → 3919d7c27402
No earlier version was observed for comparison.
skills/creator-ugc-marketing/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
3919d7c27402 → 3919d7c27402
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → 3919d7c27402
No earlier version was observed for comparison.
skills/custom-product-pages/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
3919d7c27402 → 3919d7c27402
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → 3919d7c27402
No earlier version was observed for comparison.
skills/in-app-events/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
3919d7c27402 → 3919d7c27402
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → 3919d7c27402
No earlier version was observed for comparison.
skills/keyword-research/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
3919d7c27402 → 3919d7c27402
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → 3919d7c27402
No earlier version was observed for comparison.
skills/localization/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
3919d7c27402 → 3919d7c27402
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → 3919d7c27402
No earlier version was observed for comparison.
skills/market-movers/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
3919d7c27402 → 3919d7c27402
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → 3919d7c27402
No earlier version was observed for comparison.
skills/market-pulse/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
3919d7c27402 → 3919d7c27402
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → 3919d7c27402
No earlier version was observed for comparison.
skills/metadata-optimization/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
3919d7c27402 → 3919d7c27402
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → 3919d7c27402
No earlier version was observed for comparison.
skills/monetization-strategy/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
3919d7c27402 → 3919d7c27402
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → 3919d7c27402
No earlier version was observed for comparison.
skills/onboarding-optimization/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
3919d7c27402 → 3919d7c27402
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → 3919d7c27402
No earlier version was observed for comparison.
skills/paywall-optimization/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
3919d7c27402 → 3919d7c27402
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → 3919d7c27402
No earlier version was observed for comparison.
skills/press-and-pr/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
3919d7c27402 → 3919d7c27402
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → 3919d7c27402
No earlier version was observed for comparison.
skills/rating-prompt-strategy/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
3919d7c27402 → 3919d7c27402
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → 3919d7c27402
No earlier version was observed for comparison.
skills/referral-program/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
3919d7c27402 → 3919d7c27402
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → 3919d7c27402
No earlier version was observed for comparison.
skills/retention-optimization/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
3919d7c27402 → 3919d7c27402
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → 3919d7c27402
No earlier version was observed for comparison.
skills/review-management/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
3919d7c27402 → 3919d7c27402
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → 3919d7c27402
No earlier version was observed for comparison.
skills/screenshot-optimization/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
3919d7c27402 → 3919d7c27402
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → 3919d7c27402
No earlier version was observed for comparison.
skills/seasonal-aso/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Network or broad shell
3919d7c27402 → 3919d7c27402
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → 3919d7c27402
No earlier version was observed for comparison.
skills/subscription-lifecycle/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
3919d7c27402 → 3919d7c27402
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → 3919d7c27402
No earlier version was observed for comparison.
skills/ua-campaign/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
3919d7c27402 → 3919d7c27402
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → 3919d7c27402
No earlier version was observed for comparison.
skills/web-to-app-funnel/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Network or broad shell
3919d7c27402 → 3919d7c27402
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → 3919d7c27402
No earlier version was observed for comparison.
Verified commit 3919d7c27402d92c7ef698f2016174b874ea189e
git clone --filter=blob:none --no-checkout https://github.com/appeeky/aso-skills.git .hotskills/appeeky-aso-skills && git -C .hotskills/appeeky-aso-skills checkout --detach 3919d7c27402d92c7ef698f2016174b874ea189e
# Copy each selected skill directory from .hotskills/appeeky-aso-skills into .claude/skills/<skill-name>/git clone --filter=blob:none --no-checkout https://github.com/appeeky/aso-skills.git .hotskills/appeeky-aso-skills && git -C .hotskills/appeeky-aso-skills checkout --detach 3919d7c27402d92c7ef698f2016174b874ea189e
# Copy each selected skill directory from .hotskills/appeeky-aso-skills into .agents/skills/<skill-name>/Heat
5.9- Star growth, last 7 daysAhead of 87% of tracked repositories
- Star growth, last 24 hoursAhead of 91% of tracked repositories
- Rank movement, last 7 daysAhead of 50% of tracked repositories
- Commits, last 30 daysAhead of 0% of tracked repositories
- Accounts asking about it through MCP, last 7 daysNot available
- Hot votes this weekAhead of 0% of tracked repositories
Heat never changes the order by stars, and sponsorship never touches it. How heat works
Stars over time
Individual skills in this repository
- ab-test-store-listing
skills/ab-test-store-listing - android-aso
skills/android-aso - app-analytics
skills/app-analytics - app-clips
skills/app-clips - app-icon-optimization
skills/app-icon-optimization - app-launch
skills/app-launch - app-marketing-context
skills/app-marketing-context - app-preview-video
skills/app-preview-video - app-rejection-recovery
skills/app-rejection-recovery - app-store-featured
skills/app-store-featured - apple-search-ads
skills/apple-search-ads - asc-metrics
skills/asc-metrics - aso-audit
skills/aso-audit - aso-router
skills/aso-router - attribution-setup
skills/attribution-setup - category-positioning
skills/category-positioning - competitor-analysis
skills/competitor-analysis - competitor-tracking
skills/competitor-tracking - crash-analytics
skills/crash-analytics - creator-ugc-marketing
skills/creator-ugc-marketing - custom-product-pages
skills/custom-product-pages - in-app-events
skills/in-app-events - keyword-research
skills/keyword-research - localization
skills/localization - market-movers
skills/market-movers - market-pulse
skills/market-pulse - metadata-optimization
skills/metadata-optimization - monetization-strategy
skills/monetization-strategy - onboarding-optimization
skills/onboarding-optimization - paywall-optimization
skills/paywall-optimization - press-and-pr
skills/press-and-pr - rating-prompt-strategy
skills/rating-prompt-strategy - referral-program
skills/referral-program - retention-optimization
skills/retention-optimization - review-management
skills/review-management - screenshot-optimization
skills/screenshot-optimization - seasonal-aso
skills/seasonal-aso - subscription-lifecycle
skills/subscription-lifecycle - ua-campaign
skills/ua-campaign - web-to-app-funnel
skills/web-to-app-funnel
How it works
ab-test-store-listing
When your agent uses it
When the user wants to A/B test App Store product page elements to improve conversion rate. Also use when the user mentions "A/B test", "product page optimization", "test my screenshots", "test my icon", "conversion rate optimization", "CPP", or "custom product pages". For screenshot design, see screenshot-optimization. For metadata optimization, see metadata-optimization.
What it loads into context
Frontmatter
97 tokensAlways available to the agent
SKILL.md
1,829 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Initial Assessment
- What You Can Test
- Test Prioritization
- Test Design Framework
- Common Test Ideas
- Output Format
- Related Skills
Files
../../.claude-plugin/icon.pngasset215,384 bytes../../.claude-plugin/marketplace.jsonasset853 bytes../../.claude-plugin/plugin.jsonasset748 bytesSKILL.mdcore7,382 bytes
Read SKILL.md
# A/B Test Store Listing
You are an expert in App Store product page optimization and A/B testing. Your goal is to help the user design, run, and interpret tests that improve their App Store conversion rate.
## Initial Assessment
1. Check for `app-marketing-context.md` — read it for context
2. Ask for the **App ID**
3. Ask for **current conversion rate** (if known from App Store Connect)
4. Ask for **daily impressions** (determines test duration)
5. Ask: **What do you want to test?** (icon, screenshots, description, etc.)
## What You Can Test
View the complete source on GitHubandroid-aso
When your agent uses it
When the user wants to optimize their Google Play Store listing — title, short description, full description, keywords, ratings, or Play Store-specific features. Use when the user mentions "Google Play", "Android", "Play Store", "Play Console", "short description", "full description indexed", "Google Play ASO", or wants Google Play-specific keyword, creative, or ratings strategy. For iOS App Store optimization, see aso-audit and metadata-optimization.
What it loads into context
Frontmatter
113 tokensAlways available to the agent
SKILL.md
1,597 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Key Differences vs iOS
- Character Limits
- Initial Assessment
- Metadata Optimization
- Keyword Research for Play Store
- Feature Graphic (1024×500px)
- Ratings Strategy
- Play Store Experiments (A/B Testing)
- Pre-Launch (Early Access)
- Output Format
- Related Skills
Files
SKILL.mdcore6,805 bytesSKILL.mdcore6,805 bytes
Read SKILL.md
# Android ASO (Google Play)
You are a Google Play ASO expert. Google Play's algorithm differs fundamentally from iOS — the full description is indexed, there is no hidden keyword field, and ratings are continuous (not version-reset).
## Key Differences vs iOS
| Factor | Google Play | Apple App Store |
|--------|------------|----------------|
| **Keyword indexing** | Title + Short desc + Full desc (all indexed) | Title + Subtitle + Keyword field only |
| **Hidden keyword field** | ✗ None | ✓ 100-char field |
| **Description indexed** | ✓ Full 4000 chars | ✗ Not indexed |
| **Ratings** | Continuous — never reset | Reset per version (can request reset) |
| **A/B testing** | Play Store Experiments (native) | Product Page Optimization |
| **Screenshots** | 2–8 per language | Up to 10 per language |View the complete source on GitHubapp-analytics
When your agent uses it
When the user wants to set up, interpret, or improve their app analytics and tracking. Also use when the user mentions "analytics", "tracking", "metrics", "KPIs", "App Store Connect analytics", "install tracking", "funnel", "attribution", or "how is my app performing". For A/B testing, see ab-test-store-listing. For retention metrics, see retention-optimization.
What it loads into context
Frontmatter
103 tokensAlways available to the agent
SKILL.md
1,652 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Initial Assessment
- Analytics Stack
- Key Metrics Framework
- Event Tracking Plan
- Dashboard Setup
- Output Format
- Related Skills
Files
SKILL.mdcore6,980 bytes
Read SKILL.md
# App Analytics
You are an expert in mobile app analytics and measurement strategy. Your goal is to help the user set up meaningful tracking, interpret their data, and make data-driven decisions.
## Initial Assessment
1. Check for `app-marketing-context.md` — read it for context
2. Ask: **What analytics tools do you currently use?**
3. Ask: **What are your top 3 questions about your app's performance?**
4. Ask: **What decisions do you need data to make?**
5. Ask: **Do you run paid acquisition?** (attribution matters)
## Analytics Stack
View the complete source on GitHubapp-clips
When your agent uses it
When the user wants to implement, optimize, or use App Clips for app discovery and conversion. Use when the user mentions "App Clip", "app clip code", "mini app", "instant app", "App Clip card", "App Clip link", "no download required", "instant experience", or wants to understand how App Clips appear in App Store search. For general App Store discoverability, see aso-audit. For marketing campaigns, see ua-campaign.
What it loads into context
Frontmatter
113 tokensAlways available to the agent
SKILL.md
1,360 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- What App Clips Are
- Size Limit
- Best Use Cases
- App Clip Discovery in the App Store
- Technical Requirements
- App Clip Experiences
- App Clip Card Design
- Measurement
- App Clip vs Full App Install Trade-offs
- Implementation Checklist
- Related Skills
Files
SKILL.mdcore5,793 bytes
Read SKILL.md
# App Clips
You help plan, implement, and optimize App Clips — lightweight iOS experiences (max 15MB) that users can launch instantly without installing the full app.
## What App Clips Are
App Clips are small, focused pieces of your app that users can use without downloading the full app. They appear in:
- **App Store search results** — alongside your full app
- **Smart App Banners** on websites
- **QR codes** and App Clip codes (physical NFC/QR)
- **Safari** — when visiting a linked URL
- **Messages** — when a URL is shared in iMessages
- **Maps** — for location-based businessesView the complete source on GitHubapp-icon-optimization
When your agent uses it
When the user wants to design, test, or improve their app icon to increase tap-through rate and conversions in App Store search and browse. Use when the user mentions "app icon", "icon design", "icon A/B test", "icon variants", "tap-through rate", "icon conversion", "icon refresh", or wants to know what makes a good app icon. For screenshot optimization, see screenshot-optimization. For full listing A/B tests, see ab-test-store-listing.
What it loads into context
Frontmatter
118 tokensAlways available to the agent
SKILL.md
1,456 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why the Icon Is Your Most Impactful Asset
- Icon Design Principles
- Icon Sizes Required
- A/B Testing Icons
- Icon Audit
- Brief for Icon Designer
- Related Skills
Files
SKILL.mdcore6,006 bytes
Read SKILL.md
# App Icon Optimization
You help design, audit, and A/B test app icons to maximize tap-through rate (TTR) — the percentage of users who tap your app after seeing it in search results or browse.
## Why the Icon Is Your Most Impactful Asset
The icon is the **first thing users see** in search results — before the title, rating, or screenshots. A compelling icon can lift TTR by 20–40% with no other changes. In browse/charts, it's often the only visual element competing for attention.
## Icon Design Principles
### 1. Simplicity at Small Size
Icons render at 60×60pt (iPhone search results). At that size, detail disappears.
View the complete source on GitHubapp-launch
When your agent uses it
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.
What it loads into context
Frontmatter
92 tokensAlways available to the agent
SKILL.md
1,423 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Initial Assessment
- Launch Timeline
- Launch Amplification Tactics
- Output Format
- Related Skills
Files
SKILL.mdcore5,784 bytes
Read 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 TimelineView the complete source on GitHubapp-marketing-context
When your agent uses it
When the user wants to create or update their app marketing context document. Also use when the user mentions "app context", "marketing brief", "app positioning", or when starting any ASO or app marketing project. This is the foundation skill — all other skills check for this context first.
What it loads into context
Frontmatter
78 tokensAlways available to the agent
SKILL.md
928 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Initial Assessment
- Context Document Structure
- Output
- Related Skills
Files
SKILL.mdcore3,655 bytes
Read SKILL.md
# App Marketing Context
You are an expert mobile app marketing strategist. Your goal is to help the user create a comprehensive context document that all other ASO and app marketing skills will reference.
## Initial Assessment
Check if `app-marketing-context.md` exists in the project root or `.claude/` directory.
**If it exists:** Read it and ask if the user wants to update any section.
**If it doesn't exist:** Walk through each section below, asking questions to build the document.
## Context Document Structure
View the complete source on GitHubapp-preview-video
When your agent uses it
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 "App Preview", "preview video", "app store video", "promo video", "Play Store video", "video poster frame", "YouTube promo for Play Store", "30 second app video", "video script", "video specs", or "should I add a preview video". For static screenshots, see screenshot-optimization. For A/B testing the video, see ab-test-store-listing. For broader creative briefs, see screenshot-optimization (covers stills).
What it loads into context
Frontmatter
158 tokensAlways available to the agent
SKILL.md
1,629 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Initial Assessment
- Platform Specs (memorize)
- The 30-Second Video Structure
- Script Output Format
- 3-Variant Strategy (iOS)
- Production Checklist
- Common Rejection Reasons (Apple)
- Localization Strategy
- A/B Testing
- Cross-Skill Handoffs
Files
SKILL.mdcore6,478 bytes
Read SKILL.md
# App Preview Video
You are an App Store Preview video specialist. Your goal is to help the user produce up to 3 iOS App Previews (or 1 Play Store promo video) that lift product page conversion by 5–25%.
## Initial Assessment
1. Check for `app-marketing-context.md` — read for app, audience, and core value
2. Ask for the **App ID** and **platform(s)** — iOS, Android, or both
3. Ask if they have **existing screen recordings** or need to capture fresh
4. Ask for **target conversion goal** — install (top-of-funnel) or trial start (mid-funnel)
5. Ask for **localization scope** — English only, or which markets
## Platform Specs (memorize)
View the complete source on GitHubapp-rejection-recovery
When your agent uses it
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", "guideline violation", "Apple rejected my app", "Google Play rejected", "Play policy violation", "Resolution Center", "metadata rejection", "binary rejection", "guideline 2.1", "guideline 4.3", "guideline 5.1.1", "Sign in with Apple required", "Apple ID rejection", "Play Store suspension", "appeal", "I need to respond to App Review", or "expedited review". For pre-submission listing health, see aso-audit. For metadata-only fixes, see metadata-optimization.
What it loads into context
Frontmatter
183 tokensAlways available to the agent
SKILL.md
2,235 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Initial Assessment
- Apple Rejection Taxonomy
- Common Rejection → Fix Playbook
- Google Play Rejection Taxonomy
- The Resolution Center Response Template
- When to Appeal vs Fix
- Expedited Review (Apple)
- Output Template
- Prevent Future Rejections
- Cross-Skill Handoffs
Files
SKILL.mdcore9,551 bytes
Read SKILL.md
# App Rejection Recovery
You are an App Review specialist. Your goal is to diagnose the rejection, write a clean response (or appeal), fix the underlying issue, and get the user resubmitted within 24–72 hours.
## Initial Assessment
1. Ask the user to **paste the full rejection message** verbatim — including the guideline number(s)
2. Ask: **App Store, Play Store, or both?**
3. Ask: **First submission or update?** (First submissions are scrutinized harder)
4. Ask: **App ID** and **app category**
5. Ask: **What was changed in this version** vs the last approved version (for updates)
6. Ask: **Is this time-sensitive** (launch date, marketing tied)?
Do not start writing the fix until you've classified the rejection type below.View the complete source on GitHubapp-store-featured
When your agent uses it
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 to get Apple to feature my app". For launch strategy, see app-launch. For ASO optimization, see aso-audit.
What it loads into context
Frontmatter
95 tokensAlways available to the agent
SKILL.md
1,826 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Initial Assessment
- Understanding Apple's Editorial Process
- Featuring Optimization Checklist
- How to Pitch Apple
- In-App Events Strategy
- Output Format
- Related Skills
Files
SKILL.mdcore7,714 bytes
Read SKILL.md
# App Store Featured Strategy
You are an expert in Apple's App Store editorial process and featuring strategy. Your goal is to help the user maximize their chances of getting featured on the App Store.
## Initial Assessment
1. Check for `app-marketing-context.md` — read it for context
2. Ask for the **App ID** (to assess current state)
3. Ask: **Has the app been featured before?**
4. Ask: **Any upcoming updates or launches?** (timing matters)
5. Ask: **Does the app use latest Apple technologies?** (SwiftUI, WidgetKit, etc.)
## Understanding Apple's Editorial Process
View the complete source on GitHubapple-search-ads
When your agent uses it
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 user mentions "Apple Search Ads", "ASA", "Search Ads", "Search tab ads", "Today tab ads", "CPT", "TTR", "Search Match", "exact match", "broad match", "CPP in ads", "ASA bidding", or "Search Ads budget". For Meta/Google UAC/TikTok paid UA, see ua-campaign.
What it loads into context
Frontmatter
142 tokensAlways available to the agent
SKILL.md
1,826 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why ASA Is Different
- Campaign Types
- Account Structure
- Match Types
- Keyword Strategy
- Bidding Strategy
- Creative Product Sets (CPS) and CPP Routing
- Metrics and Benchmarks
- Weekly Optimization Checklist
- Scaling Checklist
- Output Format
- Related Skills
Files
SKILL.mdcore7,511 bytesSKILL.mdcore7,511 bytes
Read SKILL.md
# Apple Search Ads
You are a specialist in Apple Search Ads (ASA) — the only ad platform that places ads natively within the App Store. ASA drives highly qualified installs because users are already in purchase intent.
## Why ASA Is Different
- Users are actively searching the App Store — highest intent of any channel
- Ads appear exactly like organic results (only "Ad" badge distinguishes them)
- No audience targeting (demographics, interests) — only keyword-based
- Conversion data is reliable (no ATT/SKAdNetwork limitations)
- CPI is typically higher than other channels but LTV is proportionally higher
## Campaign Types
View the complete source on GitHubasc-metrics
When your agent uses it
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 asks about "my downloads", "my revenue", "how is my app performing", "ASC data", "sales and trends", "my subscription numbers", "App Store Connect metrics", or wants to compare periods or top markets. For third-party app estimates, see app-analytics. For subscription analytics depth, see monetization-strategy.
What it loads into context
Frontmatter
132 tokensAlways available to the agent
SKILL.md
1,393 tokensWhen the skill is activated
Reference documents
1,295 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Prerequisites
- Initial Assessment
- Fetching Data
- Analysis Frameworks
- Output Format
- Common Questions
- Related Skills
Files
SKILL.mdcore5,388 bytesSKILL.mdcore5,388 bytesSKILL.mdcore5,388 bytesSKILL.mdcore5,388 bytes../../tools/integrations/appeeky-connect.mddoc4,279 bytes
Read SKILL.md
# ASC Metrics
You analyze the user's **official App Store Connect data** synced into Appeeky — exact downloads, revenue, IAP, subscriptions, and trials. This is first-party data, not estimates.
## Prerequisites
- Appeeky account with ASC connected (Settings → Integrations → App Store Connect)
- Indie plan or higher (2 credits per request)
- Data syncs nightly; up to 90 days of history available
If ASC is not connected, prompt the user to connect it at [appeeky.com/settings](https://appeeky.com) and return.
## Initial Assessment
View the complete source on GitHubaso-audit
When your agent uses it
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 review", or "optimize my app store page". For keyword-specific research, see keyword-research. For metadata writing, see metadata-optimization.
What it loads into context
Frontmatter
100 tokensAlways available to the agent
SKILL.md
1,590 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Initial Assessment
- Data Collection
- Audit Framework
- Output Format
- Related Skills
Files
SKILL.mdcore6,570 bytes
Read SKILL.md
# ASO Audit
You are an expert in App Store Optimization with deep knowledge of Apple's and Google's ranking algorithms. Your goal is to perform a comprehensive ASO health audit and provide a prioritized action plan.
## Initial Assessment
1. Check for `app-marketing-context.md` — read it if available for app context
2. Ask for the **App ID** (Apple numeric ID or Google Play package name)
3. Ask for the **target country** (default: US)
4. Ask which **platform** to audit (iOS / Android / Both)
## Data Collection
If Appeeky MCP or API is available, fetch:View the complete source on GitHubaso-router
When your agent uses it
Single entry point that routes any ASO, App Store, Google Play, app marketing, paid UA, monetization, retention, reviews, ratings, market-intel, or app-analytics question to the correct specialist skill in this library. Use FIRST whenever the user mentions an app, App Store, Play Store, keywords, ranking, downloads, revenue, subscriptions, screenshots, icon, reviews, competitors, charts, in-app events, launch, press, or ads — but the right specialized skill is not obvious. Triggers: "/aso-router", "/aso-skill", "/aso", "aso help", "help me with my app", "I need ASO", "which skill should I use", or any ambiguous app-marketing request. Skip this router only when the user explicitly invokes a specific skill (e.g. /aso-audit, /keyword-research).
What it loads into context
Frontmatter
210 tokensAlways available to the agent
SKILL.md
2,912 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- How to Use This Skill
- Routing Table
- Multi-Skill Routing
- Disambiguation Playbook
- Routing Anti-Patterns
- Output Template
- Context Check
- When NOT to Use This Skill
Files
SKILL.mdcore10,807 bytes
Read SKILL.md
# ASO Router
You are the routing layer for the ASO Skills library. Your single job is to read the user's request, pick the **one** (or at most three) specialist skill(s) that best fit, and load them. Do NOT try to answer the ASO question yourself — your job is dispatch, not delivery.
## How to Use This Skill
1. Read the user's message.
2. Match it against the routing table below.
3. Announce the chosen skill in one short sentence: `→ Loading: <skill-name>` (and 2nd/3rd if relevant).
4. Read `skills/<skill-name>/SKILL.md` and follow it.
5. If the user's intent is genuinely ambiguous, ask **one** clarifying question from the disambiguation playbook below.
Never load more than 3 skills at once. If you would, ask the user to narrow down.
View the complete source on GitHubattribution-setup
When your agent uses it
When the user wants to set up, debug, or interpret app install attribution — including SKAdNetwork (SKAN), Apple's AdAttributionKit, Google Play Install Referrer, MMPs (AppsFlyer, Adjust, Singular, Branch, Kochava), deep links, deferred deep links, conversion values, postback windows, or privacy thresholds. Use when the user mentions "SKAdNetwork", "SKAN", "SKAN 4", "AdAttributionKit", "AAK", "MMP", "AppsFlyer", "Adjust", "Singular", "Branch", "attribution", "conversion value", "postback", "Install Referrer", "deferred deep link", "iOS 14.5", "ATT", "App Tracking Transparency", "IDFA", or "I can't measure my ad campaigns". For paid campaign strategy, see ua-campaign and apple-search-ads. For analytics events, see app-analytics.
What it loads into context
Frontmatter
215 tokensAlways available to the agent
SKILL.md
2,091 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Initial Assessment
- The iOS Attribution Reality (2024+)
- SKAdNetwork 4.0 Essentials
- Conversion Value Schema Design
- Setup Checklist by MMP
- Android Attribution
- Deep Link Architecture
- Debug Playbook
- Output Template
- Common Mistakes
- Cross-Skill Handoffs
Files
SKILL.mdcore8,171 bytesSKILL.mdcore8,171 bytesSKILL.mdcore8,171 bytesSKILL.mdcore8,171 bytesSKILL.mdcore8,171 bytes
Read SKILL.md
# Attribution Setup
You are an app attribution specialist. Your goal is to set up — or debug — a measurement stack that tells the user which paid campaigns drove which installs and revenue, while respecting iOS privacy constraints.
## Initial Assessment
1. Check for `app-marketing-context.md`
2. Ask: **iOS, Android, or both?**
3. Ask: **Do you currently use an MMP** (AppsFlyer, Adjust, Singular, Branch, Kochava)? If yes, which.
4. Ask: **Which paid channels** are running or planned? (ASA, Meta, TikTok, Google UAC, etc.)
5. Ask: **What's broken / what's the goal?** (new setup, fix a discrepancy, optimize CV schema, migrate to AdAttributionKit, etc.)
## The iOS Attribution Reality (2024+)
View the complete source on GitHubcategory-positioning
When your agent uses it
When the user wants to choose, change, or evaluate their App Store / Google Play category and subcategory — including primary vs secondary category trade-offs, chart-rank competitive analysis, category-driven discoverability, and how category choice affects featuring eligibility. Use when the user mentions "which category", "App Store category", "primary category", "secondary category", "change my category", "Health & Fitness vs Lifestyle", "Productivity vs Utilities", "rank higher in a smaller category", "category chart", "subcategory", "Play Store category", or "should I switch categories". For full ASO health beyond category, see aso-audit. For competitor analysis within the chosen category, see competitor-analysis. For chart movements within categories, see market-movers.
What it loads into context
Frontmatter
171 tokensAlways available to the agent
SKILL.md
1,973 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Initial Assessment
- Why Category Matters
- App Store Categories (memorize the structure)
- Google Play Categories
- Category Selection Framework
- Common Category Trade-offs
- When to Switch Categories
- Mechanics of Switching
- Output Template
- Category-Specific Notes
- Common Mistakes
- Cross-Skill Handoffs
Files
SKILL.mdcore8,861 bytes
Read SKILL.md
# Category & Subcategory Positioning
You are an App Store category strategist. Your goal is to recommend the **primary** and **secondary** category (App Store) or **category + tags** (Play Store) that maximize the user's discoverability, ranking potential, and featuring odds — and explain when a category switch is worth the disruption.
## Initial Assessment
1. Check for `app-marketing-context.md`
2. Ask for the **App ID** and **current categories**
3. Ask: **What does the app actually do** in 1 sentence (their words, not marketing)?
4. Ask: **Goal** — install volume, revenue, featuring, top-100 rank in a category?
5. Ask: **How long has the app been live** in the current category? (Recent switches reset some signals)
## Why Category Matters
View the complete source on GitHubcompetitor-analysis
When your agent uses it
When the user wants to analyze competitors' App Store strategy, find keyword gaps, or understand competitive positioning. Also use when the user mentions "competitor analysis", "competitive research", "keyword gap", "what are my competitors doing", or "compare my app to". For keyword-specific research, see keyword-research. For metadata writing, see metadata-optimization.
What it loads into context
Frontmatter
91 tokensAlways available to the agent
SKILL.md
1,266 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Initial Assessment
- Competitor Identification
- Analysis Framework
- Output Format
- Related Skills
Files
SKILL.mdcore5,417 bytes
Read SKILL.md
# Competitor Analysis
You are an expert in competitive intelligence for mobile apps. Your goal is to perform a thorough analysis of the user's competitors and identify actionable opportunities to outperform them.
## Initial Assessment
1. Check for `app-marketing-context.md` — read it for known competitors
2. Ask for the **user's App ID**
3. Ask for **competitor App IDs** (or help identify competitors)
4. Ask for **target country** (default: US)
5. Ask what they want to learn: keyword gaps, creative strategy, positioning, or all
## Competitor Identification
View the complete source on GitHubcompetitor-tracking
When your agent uses it
When the user wants to monitor competitor apps on an ongoing basis — tracking metadata changes, keyword shifts, screenshot updates, rating trends, or new features. Use when the user mentions "competitor monitoring", "track competitors", "competitor alert", "competitor changed their title", "watch a competitor app", "competitor weekly report", "competitive intelligence", or "what changed in competitor's listing". For a one-time deep competitive analysis, see competitor-analysis. For market-wide chart movements, see market-movers.
What it loads into context
Frontmatter
123 tokensAlways available to the agent
SKILL.md
1,529 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- One-Time Analysis vs Ongoing Tracking
- Setup: Define Your Watchlist
- What to Track
- Weekly Competitive Report Template
- Monthly Deep-Dive Triggers
- Automation Options
- Competitive Response Playbook
- Related Skills
Files
SKILL.mdcore6,387 bytesSKILL.mdcore6,387 bytesSKILL.mdcore6,387 bytesSKILL.mdcore6,387 bytesSKILL.mdcore6,387 bytesSKILL.mdcore6,387 bytesSKILL.mdcore6,387 bytes
Read SKILL.md
# Competitor Tracking
You set up and run ongoing competitor surveillance — catching metadata changes, keyword shifts, rating drops, and new feature launches before they impact your rankings.
## One-Time Analysis vs Ongoing Tracking
| | `competitor-analysis` skill | This skill (`competitor-tracking`) |
|---|---|---|
| **Frequency** | One-time deep dive | Weekly/monthly recurring |
| **Output** | Strategy document | Change log + alerts |
| **Focus** | Gap analysis, positioning | What changed and why it matters |
| **Data** | Snapshot | Delta (before vs after) |
## Setup: Define Your WatchlistView the complete source on GitHubcrash-analytics
When your agent uses it
When the user wants to monitor, triage, or reduce their app's crash rate — including setting up Crashlytics, prioritizing which crashes to fix first, interpreting crash data, and understanding how crashes affect App Store ranking. Use when the user mentions "crash", "crashlytics", "crash rate", "ANR", "app not responding", "crash-free sessions", "crash-free users", "symbolication", "stability", "firebase crashes", "app crashing", or "crash report". For overall analytics setup, see app-analytics.
What it loads into context
Frontmatter
138 tokensAlways available to the agent
SKILL.md
1,613 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why Crash Rate Is an ASO Signal
- Tools
- Crashlytics Setup
- Triage Framework
- Reading a Crash Report
- Symbolication
- App Store Connect Crash Data
- Release Strategy to Minimize Blast Radius
- Responding to Crash-Driven 1-Star Reviews
- Output Format
- Related Skills
Files
SKILL.mdcore6,271 bytesSKILL.mdcore6,271 bytes
Read SKILL.md
# Crash Analytics
You help triage, prioritize, and reduce app crashes — and understand how crash rate affects App Store discoverability and ratings.
## Why Crash Rate Is an ASO Signal
- **App Store ranking** — Apple's algorithm penalizes apps with high crash rates
- **App Store featuring** — High crash rate disqualifies editorial consideration
- **Ratings** — Crashes are the #1 cause of 1-star reviews
- **Retention** — A crash in the first session destroys Day 1 retention
**Target:** crash-free sessions > 99.5% | crash-free users > 99%
## ToolsView the complete source on GitHubcreator-ugc-marketing
When your agent uses it
When the user wants to plan, brief, source, or measure organic creator / influencer / UGC marketing for their app — including TikTok creators, Instagram Reels, YouTube Shorts, micro-influencers, paid creator briefs, UGC ad creative for Meta/TikTok, affiliate programs, and seeding strategy. Use when the user mentions "creators", "influencers", "TikTok marketing", "UGC", "user-generated content", "creator briefs", "creator outreach", "influencer marketing", "Reels", "Shorts", "creator gifting", "seeding", "affiliate", "Whop", "TikTok Spark Ads", "Instagram collab posts", or "I want my app to go viral on TikTok". For paid social ad campaigns (Meta/TikTok ad accounts), see ua-campaign. For PR / press, see press-and-pr. For viral in-app loops, see referral-program.
What it loads into context
Frontmatter
214 tokensAlways available to the agent
SKILL.md
2,067 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Initial Assessment
- Strategy Tiers (by budget)
- The Creator Brief Template
- Hook Angles That Work for Apps
- Sourcing Creators
- UGC for Paid Ads (the multiplier)
- Disclosure & Compliance
- Measurement
- Output Template
- Common Mistakes
- Cross-Skill Handoffs
Files
SKILL.mdcore7,948 bytes
Read SKILL.md
# Creator & UGC Marketing
You are an app creator-marketing specialist. Your goal is to help the user plan and execute a creator program that produces both organic install lift AND a library of UGC-style ad creative they can scale on paid.
## Initial Assessment
1. Check for `app-marketing-context.md`
2. Ask: **What's the app's "show, don't tell" hook?** (the visual moment that makes someone go "wait, what is that?")
3. Ask: **Budget tier:** gifting only / $500–5k / $5k–50k / $50k+
4. Ask: **Primary platform:** TikTok / IG Reels / YouTube Shorts / mix
5. Ask: **Audience:** Gen Z / Millennials / niche (parents, fitness, etc.)
6. Ask: **Goal weighting:** organic installs vs ad creative library vs both
## Strategy Tiers (by budget)View the complete source on GitHubcustom-product-pages
When your agent uses it
When the user wants to design, deploy, or measure Apple Custom Product Pages (CPP) — the alternate App Store product pages with different screenshots, preview videos, and promo text shown to users coming from specific URLs (typically ad campaigns or social posts). Use when the user mentions "Custom Product Page", "CPP", "alternate product page", "App Store URL variant", "ASA CPP", "campaign-specific landing page", "product page per audience", "App Store Connect CPP", "ppoUrl", "?cpp=" parameter, or "show different screenshots to different ad audiences". For App Store A/B tests on the default page, see ab-test-store-listing. For paid ad campaigns that route to CPPs, see apple-search-ads or ua-campaign.
What it loads into context
Frontmatter
172 tokensAlways available to the agent
SKILL.md
1,691 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- What CPPs Are (and Aren't)
- Initial Assessment
- When CPPs Are Worth It
- CPP Strategy Patterns
- Anatomy of a CPP
- Output Template
- CPP + ASA: The Unlock
- CPP + Social Ads
- Measurement
- Common Mistakes
- Cross-Skill Handoffs
Files
SKILL.mdcore7,042 bytes
Read SKILL.md
# Custom Product Pages (CPP)
You are an Apple Custom Product Pages specialist. Your goal is to help the user ship 1–35 CPP variants that match the messaging of upstream traffic sources, lifting tap-through-to-install rate by 10–40% vs the default product page.
## What CPPs Are (and Aren't)
| CPPs are | CPPs are NOT |
|---|---|
| Up to **35 variants** of your product page | A/B tests (use Product Page Optimization for that) |
| Tied to a **unique URL** Apple generates | Shown organically (only via your URL) |
| Different **screenshots, preview videos, and promotional text** | Different title, subtitle, keywords, description, icon, or price |
| Reviewable separately by Apple (1–3 days) | Instant — every change waits for review |
| Reportable in **App Store Connect → Analytics → Custom Product Pages** | Measurable via ASA / MMPs separately |
View the complete source on GitHubin-app-events
When your agent uses it
When the user wants to create, plan, or optimize App Store In-App Events — the event cards that appear on the Today tab, search results, and your product page. Use when the user mentions "in-app event", "App Store event", "event card", "Today tab", "live event", "challenge", "game event", "seasonal event card", or wants visibility beyond organic search. For general ASO, see aso-audit. For seasonal keyword strategy, see seasonal-aso.
What it loads into context
Frontmatter
121 tokensAlways available to the agent
SKILL.md
1,595 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- What In-App Events Are
- Event Types
- Event Card Specs
- Planning Workflow
- Optimization Tips
- Output Format
- Common Mistakes
- Related Skills
Files
SKILL.mdcore6,662 bytes
Read SKILL.md
# In-App Events
You help the user plan, write, and optimize **App Store In-App Events** — event cards that surface in search, the Today tab, and the product page, driving installs and re-engagement without paid media.
## What In-App Events Are
In-App Events are time-limited content cards on the App Store. They appear:
- **Today tab** (editorial + algorithmic)
- **Search results** (alongside app results)
- **Your product page**
- **Personalized recommendations** (for lapsed users)
**Key advantage:** Existing users who haven't opened your app recently are notified of events. Non-users see them as discovery.
View the complete source on GitHubkeyword-research
When your agent uses it
When the user wants to discover, evaluate, or prioritize App Store keywords. Also use when the user mentions "keyword research", "find keywords", "search volume", "keyword difficulty", "keyword ideas", or "what keywords should I target". For implementing keywords into metadata, see metadata-optimization. For auditing current keyword performance, see aso-audit.
What it loads into context
Frontmatter
90 tokensAlways available to the agent
SKILL.md
1,214 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Initial Assessment
- Research Process
- Output Format
- Tips for the User
- Related Skills
Files
SKILL.mdcore5,394 bytes
Read SKILL.md
# Keyword Research
You are an expert ASO keyword researcher with deep knowledge of App Store search behavior, keyword indexing, and ranking algorithms. Your goal is to help the user discover high-value keywords and build a prioritized keyword strategy.
## Initial Assessment
1. Check for `app-marketing-context.md` — read it for app context, competitors, and goals
2. Ask for the **App ID** (to understand current rankings)
3. Ask for **target country** (default: US)
4. Ask for **seed keywords** — 3-5 words that describe the app's core function
5. Ask about **intent**: Are they optimizing for downloads, revenue, or brand awareness?
## Research Process
View the complete source on GitHublocalization
When your agent uses it
When the user wants to localize their App Store listing for international markets. Also use when the user mentions "localization", "translate my app", "international markets", "expand to new countries", "localize metadata", or "which countries should I target". For keyword research in specific markets, see keyword-research. For metadata writing, see metadata-optimization.
What it loads into context
Frontmatter
91 tokensAlways available to the agent
SKILL.md
1,385 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Initial Assessment
- Market Prioritization
- Localization Checklist
- Localization Workflow
- Output Format
- Related Skills
Files
SKILL.mdcore6,104 bytes
Read SKILL.md
# App Store Localization
You are an expert in App Store internationalization and localization strategy. Your goal is to help the user expand to new markets by localizing their App Store presence effectively.
## Initial Assessment
1. Check for `app-marketing-context.md` — read it for current markets and languages
2. Ask for the **App ID** (to see current localizations)
3. Ask: **Is the app itself localized** (UI, content) or just the store listing?
4. Ask: **Which markets** are they considering?
5. Ask: **Budget** — professional translation or AI-assisted?
## Market Prioritization
View the complete source on GitHubmarket-movers
When your agent uses it
When the user wants to track App Store chart rank changes, find top gainers and losers, detect breakout apps entering the top 100, or identify apps dropping out of charts. Also use when the user mentions "chart movers", "rank changes", "who's rising", "who's falling", "new chart entries", "top gainers", or "market shifts". For broader market overview, see market-pulse. For competitive keyword analysis, see competitor-analysis.
What it loads into context
Frontmatter
113 tokensAlways available to the agent
SKILL.md
1,132 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Initial Assessment
- Data Collection
- Analysis Framework
- Actionable Insights
- Output Format
- Related Skills
Files
SKILL.mdcore4,705 bytes
Read SKILL.md
# Market Movers Analysis
You are an expert in App Store chart dynamics. Your goal is to analyze rank changes between chart snapshots, identify significant movements, and provide actionable insights about what's driving gains and losses.
## Initial Assessment
1. Check for `app-marketing-context.md` — read it for the user's app and category
2. Ask for **chart type**: top-free (default), top-paid, or top-grossing
3. Ask for **category**: all charts or specific genre (e.g. Games, Productivity)
4. Ask for **country** (default: US)
5. Ask what they want: full overview, gainers only, losers only, or new entries
## Data Collection
View the complete source on GitHubmarket-pulse
When your agent uses it
When the user wants a comprehensive App Store market overview, daily/weekly market briefing, or combined view of chart movements, trending keywords, featured apps, and new releases. Also use when the user mentions "market overview", "what's happening on the App Store", "market briefing", "weekly report", "market trends", or "state of the market". For chart-specific rank changes only, see market-movers. For keyword trends only, see keyword-research.
What it loads into context
Frontmatter
113 tokensAlways available to the agent
SKILL.md
1,302 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Initial Assessment
- Data Collection
- Market Briefing Framework
- Output Formats
- Recurring Use
- Related Skills
Files
SKILL.mdcore5,468 bytes
Read SKILL.md
# Market Pulse
You are an expert in App Store market analysis. Your goal is to provide a comprehensive market overview by combining multiple data signals: chart movements, trending keywords, featured apps, new releases, and category dynamics.
## Initial Assessment
1. Check for `app-marketing-context.md` — read it for the user's app, category, and competitors
2. Ask for **scope**: entire App Store or specific category
3. Ask for **country** (default: US)
4. Ask for **format**: quick briefing (default), detailed report, or competitive focus
## Data Collection
Gather data from multiple sources in parallel:View the complete source on GitHubmetadata-optimization
When your agent uses it
When the user wants to optimize App Store metadata — title, subtitle, keyword field, or description. Also use when the user mentions "optimize my title", "ASO metadata", "keyword field", "character limits", "app description", or "write my subtitle". For keyword discovery, see keyword-research. For full ASO audits, see aso-audit.
What it loads into context
Frontmatter
94 tokensAlways available to the agent
SKILL.md
1,403 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Initial Assessment
- Platform-Specific Limits
- Optimization Framework
- Output Format
- Common Mistakes to Flag
- Related Skills
Files
SKILL.mdcore6,026 bytes
Read SKILL.md
# Metadata Optimization
You are an expert ASO copywriter who specializes in crafting App Store metadata that maximizes both search visibility and conversion rate. Your goal is to write metadata that ranks for target keywords while compelling users to download.
## Initial Assessment
1. Check for `app-marketing-context.md` — read it for positioning and target audience
2. Ask for the **App ID** (to see current metadata)
3. Ask for **target keywords** (or suggest running `keyword-research` first)
4. Ask for **platform** (iOS / Android / Both)
5. Ask for **target country** (default: US)
## Platform-Specific Limits
View the complete source on GitHubmonetization-strategy
When your agent uses it
When the user wants to design or optimize their app's monetization — pricing, paywalls, subscriptions, or in-app purchases. Also use when the user mentions "pricing", "paywall", "subscription", "IAP", "how to monetize", "revenue optimization", "free trial", or "conversion to paid". For retention impact, see retention-optimization. For competitive pricing, see competitor-analysis.
What it loads into context
Frontmatter
103 tokensAlways available to the agent
SKILL.md
1,754 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Initial Assessment
- Monetization Models
- Paywall Design
- In-App Purchase Strategy
- Revenue Optimization
- Output Format
- Related Skills
Files
SKILL.mdcore6,745 bytes
Read SKILL.md
# Monetization Strategy
You are an expert in mobile app monetization with deep knowledge of subscription economics, paywall psychology, and pricing strategy. Your goal is to help the user maximize revenue while maintaining user satisfaction.
## Initial Assessment
1. Check for `app-marketing-context.md` — read it for context
2. Ask for **current monetization model** (free, freemium, paid, subscription, ads)
3. Ask for **current pricing** (if applicable)
4. Ask for **conversion rate** (free to paid, trial to subscription)
5. Ask for **category** (monetization norms vary dramatically)
6. Ask for **target audience** (willingness to pay varies)
## Monetization ModelsView the complete source on GitHubonboarding-optimization
When your agent uses it
When the user wants to improve their app's onboarding experience, increase activation rate, reduce Day 1 drop-off, or optimize the first-run flow. Use when the user mentions "onboarding", "first-run", "activation", "tutorial", "day 1 retention", "new user flow", "permission prompts", "sign-up conversion", "onboarding funnel", or "users dropping off early". For overall retention strategy, see retention-optimization. For paywall placement, see monetization-strategy.
What it loads into context
Frontmatter
121 tokensAlways available to the agent
SKILL.md
1,595 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- The Activation Principle
- Initial Assessment
- Onboarding Audit Framework
- Onboarding Patterns by App Type
- Funnel Benchmarks
- Personalization Questions
- Paywall Placement in Onboarding
- Output Format
- Related Skills
Files
SKILL.mdcore6,724 bytes
Read SKILL.md
# Onboarding Optimization
You optimize the first-run experience to maximize activation — the moment a new user completes the core action that predicts long-term retention.
## The Activation Principle
**Activation ≠ sign-up.** Activation is the first time the user gets real value from your app. Identify it before anything else.
| App Type | Activation Event |
|----------|-----------------|
| Fitness | First workout completed |
| Productivity | First task or project created |
| Social | First connection made or content posted |
| Finance | First account linked or budget set |View the complete source on GitHubpaywall-optimization
When your agent uses it
When the user wants to design, test, or optimize their app's paywall — layout, copy, pricing display, trial offers, plan structure, hard vs soft paywall, paywall placement, or paywall A/B tests. Use when the user mentions "paywall", "paywall design", "paywall conversion", "trial-to-paid", "soft paywall", "hard paywall", "paywall A/B test", "paywall copy", "plan picker", "annual vs monthly display", "best paywall", "RevenueCat paywall", "Superwall", "Adapty", or "my paywall isn't converting". For overall pricing strategy and monetization model choice, see monetization-strategy. For trial nurture, dunning, and churn, see subscription-lifecycle. For where in the onboarding the paywall fires, see onboarding-optimization.
What it loads into context
Frontmatter
197 tokensAlways available to the agent
SKILL.md
1,839 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Initial Assessment
- Diagnose Before You Redesign
- The 7-Element Paywall Audit
- Paywall Placement Strategy
- Pricing Display Patterns
- A/B Testing Playbook
- Output Template
- Common Mistakes
- Cross-Skill Handoffs
Files
SKILL.mdcore7,141 bytes
Read SKILL.md
# Paywall Optimization
You are a paywall conversion specialist with deep knowledge of subscription app pricing psychology, A/B testing, and the major paywall frameworks (RevenueCat, Superwall, Adapty, native StoreKit). Your goal is to diagnose paywall under-performance and ship a higher-converting variant within 1–2 release cycles.
## Initial Assessment
1. Check for `app-marketing-context.md` — read it for app, audience, and price-point context
2. Ask for the **App ID** and **paywall framework** (RevenueCat / Superwall / Adapty / native)
3. Ask for current **paywall view → trial start** and **trial → paid** rates (last 30 days)
4. Ask for a **screenshot of the current paywall** (or 2–3 if there are variants)
5. Ask for **plan structure** — monthly, annual, lifetime, weekly? What price points?
If RevenueCat is connected, pull subscription metrics first. If `asc-metrics` is available, cross-check trial counts.
View the complete source on GitHubpress-and-pr
When your agent uses it
When the user wants to get press coverage, media mentions, or editorial features for their app — including writing press releases, pitching journalists, getting on "best apps" lists, or building an app press kit. Use when the user mentions "press", "PR", "media coverage", "TechCrunch", "journalist", "press release", "app press kit", "get featured in media", "editorial coverage", "review from a blogger", or "app launch announcement". For Apple editorial featuring, see app-store-featured. For launch strategy, see app-launch.
What it loads into context
Frontmatter
135 tokensAlways available to the agent
SKILL.md
1,752 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why Press Still Matters
- Target Media Tiers
- What Makes a Story
- Press Kit
- Press Release Structure
- Pitching Journalists
- Embargo Strategy
- Product Hunt Launch
- Output Format
- Related Skills
Files
SKILL.mdcore7,169 bytes
Read SKILL.md
# Press & PR for Apps
You help indie developers and app teams get genuine media coverage — which drives installs, backlinks, and App Store credibility.
## Why Press Still Matters
- **Web referral** in App Store Connect directly tracks installs from press links
- **Backlinks** from high-authority sites (TechCrunch, The Verge) improve web presence
- **Social proof** — "As seen on…" on your product page improves conversion
- **Apple editorial** — press coverage increases editorial featuring consideration
- **Organic amplification** — articles get shared, creating discovery beyond the original publication
## Target Media Tiers
View the complete source on GitHubrating-prompt-strategy
When your agent uses it
When the user wants to improve their app's star rating, increase ratings volume, optimize when and how they prompt users for a review, or recover from a bad rating period. Use when the user mentions "app rating", "star rating", "review prompt", "SKStoreReviewRequest", "In-App Review API", "ask for review", "low rating", "rating drop", "get more reviews", or "recover from 1-star". For responding to reviews, see review-management. For overall ASO health, see aso-audit.
What it loads into context
Frontmatter
131 tokensAlways available to the agent
SKILL.md
1,572 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why Ratings Matter for ASO
- The Core Rule
- iOS — SKStoreReviewRequest
- Android — Play In-App Review API
- Timing Framework
- Pre-Prompt Survey (Recommended)
- Version-Gating (iOS)
- Recovering from a Rating Drop
- Prompt Frequency
- Output Format
- Related Skills
Files
SKILL.mdcore6,637 bytes
Read SKILL.md
# Rating Prompt Strategy
You optimize when, how, and to whom an app shows review prompts — maximizing high ratings while minimizing negative ones. Ratings are an App Store ranking signal and a conversion factor on the product page.
## Why Ratings Matter for ASO
- **Search ranking** — Apps with higher ratings rank better for competitive keywords
- **Conversion** — Rating stars are visible in search results; a 4.8 beats 4.2 at a glance
- **iOS:** Rating resets per version (you can request a reset in App Store Connect)
- **Android:** Ratings are permanent and cumulative — one bad period is hard to recover
## The Core Rule
**Only prompt users who have experienced value.** Prompting too early produces low ratings. Prompting at a success moment produces 4–5 star ratings.View the complete source on GitHubreferral-program
When your agent uses it
When the user wants to design, launch, or optimize an in-app referral / invite / share-to-earn program — including reward structure, mechanics, fraud prevention, deep link setup, and viral coefficient measurement. Use when the user mentions "referral program", "invite a friend", "refer and earn", "share to earn", "viral loop", "viral coefficient", "K-factor", "double-sided rewards", "give X get X", "referral rewards", "invite link", "share sheet", "Branch referrals", "in-app invites", or "how to make my app go viral". For deep link infrastructure that referrals depend on, see attribution-setup. For organic content-driven virality (UGC, creator), see creator-ugc-marketing.
What it loads into context
Frontmatter
173 tokensAlways available to the agent
SKILL.md
1,981 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Initial Assessment
- Is a Referral Program Right for You?
- Reward Structure Patterns
- Reward Sizing
- The Viral Coefficient
- Mechanics Checklist
- Fraud Prevention
- Output Template
- Tooling
- Common Mistakes
- Cross-Skill Handoffs
Files
SKILL.mdcore8,155 bytes
Read SKILL.md
# Referral Program
You are a referral / viral growth specialist. Your goal is to help the user ship a referral program that drives a measurable lift in install volume — typically 5–20% of net-new installs once mature — without inviting fraud or eroding unit economics.
## Initial Assessment
1. Check for `app-marketing-context.md`
2. Ask: **What's the core value users would invite friends for?** (multiplayer, shared workspace, social, savings, status)
3. Ask: **What's your CAC** for a paid install? (sets the upper bound on referral reward)
4. Ask: **What's your ARPU / LTV** for a converted user?
5. Ask: **Do you have an MMP / deep link infra** already? (Branch, AppsFlyer OneLink, Adjust)
6. Ask: **Target audience** — does the product have natural sharing moments?
If LTV is unclear, route to `asc-metrics` first. You can't size rewards without knowing payback.View the complete source on GitHubretention-optimization
When your agent uses it
When the user wants to reduce churn, improve user engagement, or increase lifetime value. Also use when the user mentions "retention", "churn", "users leaving", "engagement", "DAU/MAU", "user activation", or "why are users uninstalling". For onboarding-specific issues, see app-launch. For monetization, see monetization-strategy.
What it loads into context
Frontmatter
96 tokensAlways available to the agent
SKILL.md
1,574 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Initial Assessment
- Retention Benchmarks
- Retention Framework
- Churn Prevention Tactics
- Output Format
- Related Skills
Files
SKILL.mdcore5,854 bytes
Read SKILL.md
# Retention Optimization
You are an expert in mobile app retention and engagement strategy. Your goal is to diagnose retention issues and provide a prioritized plan to keep users coming back.
## Initial Assessment
1. Check for `app-marketing-context.md` — read it for context
2. Ask for **current retention metrics** (Day 1, Day 7, Day 30 if available)
3. Ask for **app category** (benchmarks vary dramatically)
4. Ask about **monetization model** (retention strategy differs for free vs subscription)
5. Ask about **current engagement features** (push notifications, streaks, etc.)
## Retention Benchmarks
View the complete source on GitHubreview-management
When your agent uses it
When the user wants to analyze, respond to, or improve their app reviews and ratings. Also use when the user mentions "reviews", "ratings", "negative reviews", "how to get more reviews", "review response", or "my rating is dropping". For broader ASO audit, see aso-audit. For retention issues causing bad reviews, see retention-optimization.
What it loads into context
Frontmatter
93 tokensAlways available to the agent
SKILL.md
1,370 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Initial Assessment
- Review Analysis Framework
- Rating Improvement Strategy
- Review Mining for Product Insights
- Output Format
- Related Skills
Files
SKILL.mdcore5,987 bytes
Read SKILL.md
# Review Management
You are an expert in app review strategy and reputation management. Your goal is to help the user turn reviews into a growth lever — improving ratings, gaining insights, and building user trust.
## Initial Assessment
1. Check for `app-marketing-context.md` — read it for context
2. Ask for the **App ID** (to fetch current reviews)
3. Ask for **target country** (default: US)
4. Ask about their **current rating** and **trend** (improving or declining?)
5. Ask if they **currently respond** to reviews
## Review Analysis Framework
View the complete source on GitHubscreenshot-optimization
When your agent uses it
When the user wants to design, optimize, or evaluate App Store screenshots and preview videos. Also use when the user mentions "screenshots", "app preview", "product page design", "screenshot design", "creative assets", or "what should my screenshots show". For A/B testing screenshots, see ab-test-store-listing. For full ASO audit, see aso-audit.
What it loads into context
Frontmatter
97 tokensAlways available to the agent
SKILL.md
1,238 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Initial Assessment
- Screenshot Psychology
- Screenshot Strategy Framework
- Design Best Practices
- App Preview Video
- Output Format
- Related Skills
Files
SKILL.mdcore5,217 bytes
Read SKILL.md
# Screenshot Optimization
You are an expert in App Store creative optimization with deep knowledge of what converts browsers into downloaders. Your goal is to help the user design screenshots that maximize conversion rate.
## Initial Assessment
1. Check for `app-marketing-context.md` — read it for positioning and audience
2. Ask for the **App ID** (to see current screenshots)
3. Ask for **target audience** — who is browsing the App Store for this?
4. Ask for **top 3 features** they want to highlight
5. Ask if they have a **designer** or need guidance for DIY
## Screenshot Psychology
View the complete source on GitHubseasonal-aso
When your agent uses it
When the user wants to optimize their App Store listing for seasonal events, holidays, or trending moments — including keyword opportunities, metadata updates, screenshot theming, and timing strategy. Use when the user mentions "seasonal", "holiday", "Christmas", "New Year", "Valentine's Day", "summer", "back to school", "seasonal keywords", "trending now", "limited time", or wants to capitalize on a calendar event. For general keyword research, see keyword-research. For full metadata rewrites, see metadata-optimization.
What it loads into context
Frontmatter
131 tokensAlways available to the agent
SKILL.md
1,438 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Key Principle
- Seasonal Calendar (iOS — US)
- Workflow
- Output Format
- Seasonal vs Evergreen Trade-offs
- Trending Moments (Non-Calendar)
- Related Skills
Files
SKILL.mdcore5,659 bytesSKILL.mdcore5,659 bytes
Read SKILL.md
# Seasonal ASO
You help the user identify and act on seasonal keyword opportunities and listing optimizations tied to calendar events, holidays, and trending moments.
## Key Principle
**Seasonal rankings are competitive and time-sensitive.** Metadata takes 1–3 days to index. Plan changes 2 weeks before the event; revert 3–5 days after peak.
## Seasonal Calendar (iOS — US)
| Event | Peak Window | Keywords to target |
|-------|-------------|-------------------|
| New Year | Dec 26 – Jan 7 | "new year", "resolution", "goals", "habit", "fresh start" |
| Valentine's Day | Feb 1–14 | "valentine", "love", "couples", "romantic", "gift" |View the complete source on GitHubsubscription-lifecycle
When your agent uses it
When the user wants to optimize their subscription business end-to-end — from trial start through renewal, cancellation, and win-back. Use when the user mentions "subscription lifecycle", "trial conversion", "churn", "cancellation", "win-back", "lapsed subscribers", "dunning", "billing retry", "grace period", "renewal rate", "subscriber LTV", or "resubscribe". For paywall design and pricing strategy, see monetization-strategy. For subscription analytics dashboards, see app-analytics.
What it loads into context
Frontmatter
127 tokensAlways available to the agent
SKILL.md
1,908 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- The Subscription Lifecycle
- Key Metrics at Each Stage
- Stage 1 — Trial Optimization
- Stage 2 — Reducing Voluntary Churn
- Stage 3 — Involuntary Churn (Failed Payments)
- Stage 4 — Win-Back Campaigns
- Output Format
- Related Skills
Files
SKILL.mdcore7,819 bytes
Read SKILL.md
# Subscription Lifecycle
You optimize every stage of the subscription journey: trial → paid → renewal → cancellation recovery → win-back.
## The Subscription Lifecycle
```
Install → Trial start → [Trial period] → Conversion → Renewal → ... → Cancel → Win-back
↓ ↓ ↓ ↓
No convert Voluntary Involuntary Lapsed
(nurture) (exit survey) (dunning) (campaign)
```
## Key Metrics at Each StageView the complete source on GitHubua-campaign
When your agent uses it
When the user wants to plan or optimize paid user acquisition campaigns. Also use when the user mentions "Apple Search Ads", "user acquisition", "paid ads", "UA", "ad campaign", "install campaign", "Facebook ads for apps", "TikTok ads", or "cost per install". For organic growth, see aso-audit. For launch-specific UA, see app-launch.
What it loads into context
Frontmatter
97 tokensAlways available to the agent
SKILL.md
1,754 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Initial Assessment
- Channel Selection
- Apple Search Ads (Priority Channel)
- Meta (Facebook/Instagram) Campaigns
- Google UAC (Universal App Campaigns)
- Key Metrics & Optimization
- Output Format
- Related Skills
Files
SKILL.mdcore6,697 bytes
Read SKILL.md
# User Acquisition Campaigns
You are an expert in mobile app user acquisition across all major ad platforms. Your goal is to help the user plan, launch, and optimize paid campaigns that drive profitable installs.
## Initial Assessment
1. Check for `app-marketing-context.md` — read it for context
2. Ask for **monthly UA budget** (this determines channel strategy)
3. Ask for **target CPI** (cost per install) or **target ROAS**
4. Ask for **current LTV** (lifetime value per user)
5. Ask for **target audience** (demographics, interests, behaviors)
6. Ask for **target countries**
7. Ask for **app category** (affects channel selection)
View the complete source on GitHubweb-to-app-funnel
When your agent uses it
When the user wants to design or optimize the funnel that takes web visitors into installing and onboarding the app — including smart app banners, web-to-app deep links, deferred deep links, web onboarding (Stripe-paid web flow before app install), QR codes, "open in app" CTAs, and the trade-off between paying on web vs in-app. Use when the user mentions "web to app", "smart app banner", "Stripe before app", "web paywall before install", "Branch web SDK", "web funnel for app", "AppsFlyer OneLink web", "Universal Links", "App Links", "QR code to app", "open in app", "deferred deep link from web", or "should I sell on web first then push to app". For pure in-app onboarding, see onboarding-optimization. For deep link infra, see attribution-setup.
What it loads into context
Frontmatter
198 tokensAlways available to the agent
SKILL.md
2,066 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Initial Assessment
- Why Web-to-App Matters in 2025
- The Three Web-to-App Patterns
- Pattern B (Web Payment) — The Mechanic
- Apple / Google Compliance
- Smart Banners & Open-in-App
- Quiz Funnel Mechanics (Pattern B)
- Output Template
- Common Mistakes
- Cross-Skill Handoffs
Files
SKILL.mdcore8,631 bytesSKILL.mdcore8,631 bytes
Read SKILL.md
# Web-to-App Funnel
You are a web-to-app conversion specialist. Your goal is to design a funnel where web traffic (paid or organic) converts to app installs and activated users with maximum efficiency, optionally paying on web first to bypass App Store fees on subscriptions.
## Initial Assessment
1. Check for `app-marketing-context.md`
2. Ask: **What web traffic** does the user have or plan? (SEO, paid search, social ads with web destination, podcast, newsletter)
3. Ask: **Monetization model** — subscription (web payment is huge lever), IAP, ads, free
4. Ask: **Current web property** — landing page, full marketing site, none
5. Ask: **Markets** — US-only or global? (web payment rules differ in EU/Korea)
6. Ask: **Current funnel metrics** if available (web visit → install → activate → paid)
## Why Web-to-App Matters in 2025View the complete source on GitHubSkills included
- ab-test-store-listing
- android-aso
- app-analytics
- app-clips
- app-icon-optimization
- app-launch
- app-marketing-context
- app-preview-video
- app-rejection-recovery
- app-store-featured
- apple-search-ads
- asc-metrics
- aso-audit
- aso-router
- attribution-setup
- category-positioning
- competitor-analysis
- competitor-tracking
- crash-analytics
- creator-ugc-marketing
- custom-product-pages
- in-app-events
- keyword-research
- localization
- market-movers
- market-pulse
- metadata-optimization
- monetization-strategy
- onboarding-optimization
- paywall-optimization
- press-and-pr
- rating-prompt-strategy
- referral-program
- retention-optimization
- review-management
- screenshot-optimization
- seasonal-aso
- subscription-lifecycle
- ua-campaign
- web-to-app-funnel
Repository facts
- License
- MIT
- Created
- Feb 27, 2026
- Last pushed
- Oct 6, 2026
- Forks
- 141
- Open issues
- 0
- Project activity
- Active
Rank over the last 12 weeks
Now #500 · best #415 · down 57 in 30 days
- #493 on Nov 2
- #495 on Nov 3
- #497 on Nov 4
- #496 on Nov 5
- #498 on Nov 6
- #500 since Nov 7
78 earlier periods
- #389 on Aug 2
- #403 on Aug 8
- #401 on Aug 9
- #413 on Aug 10
- #410 on Aug 11
- #406 on Aug 12
- #414 on Aug 13
- #416 on Aug 14
- #418 on Aug 16
- #420 on Aug 17
- #424 on Aug 18
- #428 on Aug 19
- #422 on Aug 20
- #426 on Aug 21
- #415 on Aug 22
- #429 on Aug 23
- #432 from Aug 24 to Aug 25
- #429 on Aug 26
- #436 on Aug 27
- #434 on Aug 28
- #429 on Aug 29
- #421 on Aug 30
- #434 on Aug 31
- #440 on Sep 1
- #431 on Sep 2
- #435 on Sep 3
- #423 on Sep 4
- #429 on Sep 5
- #430 on Sep 6
- #438 on Sep 7
- #445 on Sep 8
- #442 from Sep 9 to Sep 10
- #438 on Sep 11
- #436 on Sep 12
- #435 on Sep 13
- #449 on Sep 14
- #445 on Sep 15
- #450 on Sep 16
- #445 on Sep 17
- #428 on Sep 18
- #419 on Sep 19
- #425 on Sep 20
- #427 on Sep 21
- #434 on Sep 22
- #426 on Sep 23
- #418 on Sep 24
- #419 on Sep 25
- #416 on Sep 26
- #429 on Sep 27
- #433 on Sep 28
- #443 on Sep 29
- #438 on Sep 30
- #436 on Oct 1
- #433 on Oct 2
- #420 on Oct 3
- #417 on Oct 4
- #427 on Oct 5
- #435 on Oct 6
- #440 on Oct 7
- #443 on Oct 8
- #448 on Oct 9
- #440 on Oct 10
- #439 on Oct 11
- #450 on Oct 12
- #449 from Oct 13 to Oct 15
- #455 on Oct 16
- #448 on Oct 17
- #452 on Oct 18
- #462 on Oct 19
- #465 on Oct 20
- #471 on Oct 21
- #465 on Oct 22
- #463 on Oct 23
- #453 on Oct 24
- #484 on Oct 25
- #489 on Oct 28
- #490 on Oct 29
- #492 from Oct 30 to Nov 1
Before you install
Network or broad shellAutomated signals, not a guarantee
Checked Nov 3, 2026
Not fully analyzed: some files were too long, unreadable or missing. This never lowers the level.
Show 18 notes
skills/android-aso/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/apple-search-ads/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/asc-metrics/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/asc-metrics/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/asc-metrics/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/attribution-setup/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/attribution-setup/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/attribution-setup/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/attribution-setup/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/competitor-tracking/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/competitor-tracking/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/competitor-tracking/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/competitor-tracking/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/competitor-tracking/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/competitor-tracking/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/crash-analytics/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/seasonal-aso/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedskills/web-to-app-funnel/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzed
- No broad tool permissions
- No dangerous shell commands
- 37 network referencesin 7 files: tools/integrations/appeeky-connect.md:5 .claude-plugin/marketplace.json:3 .claude-plugin/plugin.json:8 and 4 more
- No hidden or obfuscated text
- No instruction overrides
- No executable scripts
- No access to secrets
- No requests to vote in Hot
Show all 37 signals by file
.claude-plugin/marketplace.json
- Network accessline 3
"owner": { "name": "Appeeky", "url": "https://appeeky.com" - Network accessline 4
"name": "Appeeky", "url": "https://appeeky.com" }, - Network accessline 5
"url": "https://appeeky.com" - Network accessline 14
"description": "40 ASO and app marketing skills for indie developers, app marketers, and growth teams. Covers keyword research, metadata optimization, competitor analysis, market intelligence, screenshots, reviews, localization, user acquis - Network accessline 15
"source": "./", "homepage": "https://github.com/appeeky/aso-skills", "license": "MIT", - Network accessline 16
"homepage": "https://github.com/appeeky/aso-skills",
.claude-plugin/plugin.json
- Network accessline 8
"name": "Appeeky", "email": "hey@appeeky.com", "url": "https://appeeky.com" - Network accessline 9
"email": "hey@appeeky.com", "url": "https://appeeky.com" }, - Network accessline 10
"url": "https://appeeky.com" - Network accessline 11
}, "homepage": "https://github.com/appeeky/aso-skills", "repository": "https://github.com/appeeky/aso-skills", - Network accessline 12
"homepage": "https://github.com/appeeky/aso-skills", - Network accessline 13
"repository": "https://github.com/appeeky/aso-skills",
skills/app-clips/SKILL.md
- Network accessline 72
https://yourdomain.com/clip/[experience]
skills/app-store-featured/SKILL.md
skills/asc-metrics/SKILL.md
- Network accessline 18
If ASC is not connected, prompt the user to connect it at [appeeky.com/settings](https://appeeky.com) and return.
skills/competitor-tracking/SKILL.md
tools/integrations/appeeky-connect.md
- Network accessline 5
**Base URL:** `https://api.appeeky.com` - Network accessline 9
> **Requires:** Connect your ASC API key and Vendor Number in [appeeky.com → Settings → Integrations](https://appeeky.com). Data syncs nightly (and on manual sync). Up to 90 days of history. - Network accessline 43
curl "https://api.appeeky.com/v1/connect/metrics?from=2026-02-19&to=2026-03-21" \ - Network accessline 117
curl "https://api.appeeky.com/v1/connect/metrics/apps/6759740679?from=2026-02-19&to=2026-03-21" \ - Network accessline 133
[Credential-related source omitted] - Network accessline 134
[Credential-related source omitted] - Network accessline 135
"https://api.appeeky.com/v1/connect/metrics" - Network accessline 137
[Credential-related source omitted] - Network accessline 138
[Credential-related source omitted] - Network accessline 139
"https://api.appeeky.com/v1/connect/metrics/apps/$APP_ID" - Network accessline 145
[Credential-related source omitted] - Network accessline 146
[Credential-related source omitted] - Network accessline 147
"https://api.appeeky.com/v1/connect/metrics/apps/$APP_ID?from=2026-03-01&to=2026-03-21" - Network accessline 149
[Credential-related source omitted] - Network accessline 150
[Credential-related source omitted] - Network accessline 151
"https://api.appeeky.com/v1/connect/metrics/apps/$APP_ID?from=2026-02-01&to=2026-02-21" - Network accessline 157
[Credential-related source omitted] - Network accessline 158
"https://api.appeeky.com/v1/connect/metrics/apps/$APP_ID?from=2026-01-01"
How the signals fit together
Facts from a static read of the files at the pinned commit. They describe what the code does, not why.
Some files could not be read; the facts below still hold.
Signal confidence: 25 facts
- Network access in code of the SKILL.mdapp-clips/SKILL.md:72High confidence
- Network access in prose of the SKILL.mdapp-store-featured/SKILL.md:96Low confidence
- Network access in prose of the SKILL.mdapp-store-featured/SKILL.md:97Low confidence
- Network access in prose of the SKILL.mdasc-metrics/SKILL.md:18Low confidence
- Network access in code of the SKILL.mdcompetitor-tracking/SKILL.md:149High confidence
- Network access in code of the SKILL.mdcompetitor-tracking/SKILL.md:150High confidence
- Network access in code of the SKILL.mdcompetitor-tracking/SKILL.md:151High confidence
- Network access in prose of documentationtools/integrations/appeeky-connect.md:5Low confidence
- Network access in prose of documentationtools/integrations/appeeky-connect.md:9Low confidence
- Network access in code of documentationtools/integrations/appeeky-connect.md:43Low confidence
- Network access in code of documentationtools/integrations/appeeky-connect.md:117Low confidence
- Network access in code of documentationtools/integrations/appeeky-connect.md:133Low confidence
- Network access in code of documentationtools/integrations/appeeky-connect.md:134Low confidence
- Network access in code of documentationtools/integrations/appeeky-connect.md:135Low confidence
- Network access in code of documentationtools/integrations/appeeky-connect.md:137Low confidence
- Network access in code of documentationtools/integrations/appeeky-connect.md:138Low confidence
- Network access in code of documentationtools/integrations/appeeky-connect.md:139Low confidence
- Network access in code of documentationtools/integrations/appeeky-connect.md:145Low confidence
- Network access in code of documentationtools/integrations/appeeky-connect.md:146Low confidence
- Network access in code of documentationtools/integrations/appeeky-connect.md:147Low confidence
- Network access in code of documentationtools/integrations/appeeky-connect.md:149Low confidence
- Network access in code of documentationtools/integrations/appeeky-connect.md:150Low confidence
- Network access in code of documentationtools/integrations/appeeky-connect.md:151Low confidence
- Network access in code of documentationtools/integrations/appeeky-connect.md:157Low confidence
- Network access in code of documentationtools/integrations/appeeky-connect.md:158Low confidence
Works with
| Agent | Status | Evidence | Install to |
|---|---|---|---|
| Claude Code | Native | Manifest .claude-plugin/marketplace.json | .claude/skills/<skill-name>/ |
| Codex | Native | Manifest AGENTS.md | .agents/skills/<skill-name>/ |
| Cursor | Compatible | Standard SKILL.md skills/ab-test-store-listing/SKILL.md | .cursor/skills/<skill-name>/ |
| Gemini CLI | Compatible | Standard SKILL.md skills/ab-test-store-listing/SKILL.md | .gemini/skills/<skill-name>/ |
| GitHub Copilot | Compatible | Standard SKILL.md skills/ab-test-store-listing/SKILL.md | .github/skills/<skill-name>/ |
| OpenCode | Compatible | Standard SKILL.md skills/ab-test-store-listing/SKILL.md | .opencode/skills/<skill-name>/ |
- Native The repository ships a manifest, folder or frontmatter field for this agent.
- Compatible A standard SKILL.md that this agent can read.
- Unknown No evidence either way.
Derived automatically from paths, manifests and frontmatter. Not tested on each agent.
Explore alternatives and comparisons
Add this badge to your README
It updates every night and links to this page.
[](https://hotskills.dev/skill/appeeky-aso-skills/)