App Marketing Context
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.
MCP get_skill({ skillId: "app-marketing-context-f8e3620c" })Use this skill with your agent
Create a free account and connect via MCP
# 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
Related Skills
More skills in Business, Marketing & Sales
Ab Testing
When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program," or "experiment playbook." Use this whenever someone is comparing two approaches and wants to measure which performs better, or when they want to build a systematic experimentation practice. For tracking implementation, see analytics. For page-level conversion optimization, see cro.
Ab Test Setup
When the user wants to plan, design, or implement an A/B test or experiment. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "conversion experiment," "statistical significance," or "test this." For tracking implementation, see analytics-tracking.
Ab Test Setup
Ab Test Setup linked from Corey Haines marketing skills, with the upstream skill instructions available on GitHub.
Ab Test Store Listing
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.
Account Research
Research a company or person and get actionable sales intel. Works standalone with web search, supercharged when you connect enrichment tools or your CRM. Trigger with "research [company]", "look up [person]", "intel on [prospect]", "who is [name] at [company]", or "tell me about [company]".
Account Research
Research a company using Common Room data. Triggers on 'research [company]', 'tell me about [domain]', 'pull up signals for [account]', 'what's going on with [company]', or any account-level question.
Explore Other Categories
Skills from other categories with shared topics
App Rejection Recovery
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.
Crash Analytics
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.
Agent Protocol
Inter-agent communication protocol for C-suite agent teams. Defines invocation syntax, loop prevention, isolation rules, and response formats. Use when C-suite agents need to query each other, coordinate cross-functional analysis, or run board meetings with multiple agent roles.