agentleFS
EronredEronred/aso-skills/skills/app-marketing-context/SKILL.md

app-marketing-context

Skill2.2k starsChanged 9 months agoMITView on GitHub

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.

5 other projects use a version of this.

Trending

Quiet since March.thin dataabout the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 1 mentionApr 2026: 0 mentionsMay 2026: 0 mentionsJun 2026: 0 mentionsJul 2026: 0 mentionsAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 0 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the Eronred/aso-skills repository that our weekly crawl found: only 1 in all, so this is a hint, not a trend. There is no adoption data for this file yet.

Most recently taken up by

Who's talking about Eronred/aso-skills

The biggest 1 of 1 mention linking to the repository that our crawl found. Each line is their own headline.

Used with

Projects with it also use revenue-analysis and review-analysis.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • trysonarSkill

    revenue-analysis

    When the user wants to estimate or benchmark app revenue and downloads — validating an app idea, sizing a niche, comparing monetization across apps, or reading their own App Store Connect sales on the App Store or Google Play. Also use when the user mentions "how much does this app make", "revenue estimate", "app downloads estimate", "market size", "is this niche profitable", or "my sales". For finding the apps to benchmark, see market-discovery. For full competitor teardowns, see competitor-analysis.

    Also in 3 projects that use this

  • liangdabiaoSkill

    review-analysis

    对亚马逊商品评论进行深度分析,自动识别产品痛点、分析退货原因,生成改进建议和客服回复模板。Invoke when user uses /review-analysis command with a product ASIN.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 4 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Check if app-marketing-context.md exists in the project root or .claude/ directory.

    line 14
  2. Distinctive:

    If it exists: Read it and ask if the user wants to update any section.

    line 16
  3. Very specific:

    Create app-marketing-context.md with these sections:

    line 22
  4. Distinctive:

    If the user has an App ID, offer to pull current metadata:

    line 71
  5. Distinctive:

    After creating it, summarize:

    line 119
  6. Distinctive:

    All other skills reference this context.

    line 126

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
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

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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.