/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
$ npx -y skills add eronred/aso-skills --skill app-marketing-context --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/app-marketing-context
Context preview
The summary Claude sees to decide when to auto-load this skill.
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
SKILL.md
app-marketing-context.SKILL.mdname: app-marketing-context
description: 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.
metadata:
version: 1.0.0
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
## 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?
## 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?
## 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:
## 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?
## 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
## 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
## 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
Read more
name: app-marketing-context description: 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. metadata: version: 1.0.0
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
## 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?
## 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?
## 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:
## 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?
## 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
## 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
## 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
AI agent skills for App Store Optimization (ASO) and mobile 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
Other skills on aso-skills.
- /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
Open skill - /android-aso
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
Open skill - /app-analytics
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
Open skill - /app-clips
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
Open skill - /app-icon-optimization
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
Open skill - /app-launch
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
Open skill

