app-marketing-context
The app-marketing-context skill guides users through creating a comprehensive foundation document for app marketing and ASO projects. It checks for an existing context file, then systematically collects app overview, value proposition, competitive analysis, current ASO metrics, goals, and resource details through structured questioning. This context document serves as a reference point that all other ASO and marketing skills consult before providing recommendations.
git clone --depth 1 https://github.com/Eronred/aso-skills /tmp/app-marketing-context && cp -r /tmp/app-marketing-context/skills/app-marketing-context ~/.claude/skills/app-marketing-contextSKILL.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 Create `app-marketing-context.md` with these sections: ### 1. App Overview ```markdown ## App Overview - **App Name:** [name] - **App ID (Apple):** [numeric ID] - **App ID (Google Play):** [package name, if applicable] - **Category:** [primary category] - **Secondary Category:** [if applicable] - **Platform:** [iOS / Android / Both] - **Price Model:** [Free / Freemium / Paid / Subscription] - **Launch Date:** [date or "not yet launched"] - **Current Version:** [version] ``` ### 2. Value Proposition Ask the user: 1. What problem does your app solve? 2. Who is your ideal user? (demographics, behavior, needs) 3. What makes your app different from alternatives? 4. What is your one-sentence elevator pitch? ```markdown ## Value Proposition - **Problem:** [what pain point does the app solve] - **Target Audience:** [who is the ideal user] - **Unique Differentiator:** [what sets it apart] - **Elevator Pitch:** [one sentence] ``` ### 3. Competitive Landscape Ask the user: 1. Who are your top 3-5 competitors? 2. What do they do well? 3. Where do they fall short? ```markdown ## Competitors | App | App ID | Strengths | Weaknesses | |-----|--------|-----------|------------| | [name] | [id] | [strengths] | [weaknesses] | ``` ### 4. Current ASO State If the user has an App ID, offer to pull current metadata: ```markdown ## Current ASO State - **Title:** [current title] - **Subtitle:** [current subtitle] - **Keyword Field:** [if known] - **Rating:** [stars] ([count] ratings) - **Primary Keywords:** [top keywords they rank for] ``` ### 5. Goals & KPIs Ask the user: 1. What are your top 3 goals? (downloads, revenue, retention, rankings) 2. What metrics do you track? 3. What's your timeline? ```markdown ## Goals 1. [goal 1] — Target: [metric] by [date] 2. [goal 2] — Target: [metric] by [date] 3. [goal 3] — Target: [metric] by [date] ``` ### 6. Resources & Constraints ```markdown ## Resources - **Budget:** [monthly marketing budget, if any] - **Team:** [solo / small team / marketing team] - **Tools:** [analytics, ASA, MMP, etc.] - **Constraints:** [any limitations — time, budget, technical] ``` ### 7. Markets ```markdown ## Markets - **Primary:** [country/region] - **Secondary:** [countries/regions] - **Languages:** [supported languages] ``` ## Output Save the completed document as `app-marketing-context.md` in the project root. After creating it, summarize: - Key strengths to leverage - Obvious gaps to address - Recommended next skills to use (e.g., `aso-audit`, `keyword-research`) ## Related Skills All other skills reference this context. Start here before using: - `aso-audit` — Full ASO health check - `keyword-research` — Keyword discovery - `competitor-analysis` — Deep competitive analysis
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.
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.
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.
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.
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.
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.
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).
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.