agentleFS
AppKittieAppKittie/aso-mcp-skills/skills/app-marketing-context/SKILL.md

app-marketing-context

Skill8 starsChanged 18 days agoMITView on GitHub

When the user wants to create a shared context document for their app that other skills can reference. Also use when the user mentions "set up my app", "configure my app context", "my app details", or before running any other skill for the first time. This skill creates app-marketing-context.md which all other skills read for background.

3 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 3 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When the app's strategy changes (new target market, repositioning)

    line 16
  2. Distinctive:

    When competitors shift significantly

    line 17
  3. Very specific:

    Ask the user for each section.

    line 21
  4. Very specific:

    Use get_app_detail if available:

    line 45
  5. Very specific:

    Running ads?: Use search_apps for Meta/Apple presence signals and search_ads(appSlug) for creative records

    line 50
  6. Distinctive:

    All other skills check for this file:

    line 102

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “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 setting up a shared context document that all AppKittie skills will reference. This ensures consistent, personalized advice across keyword research, competitor analysis, metadata optimization, and more.

When to Use

Run this skill:

  • First time using AppKittie skills for a specific app
  • When the app's strategy changes (new target market, repositioning)
  • When competitors shift significantly

Information to Gather

Ask the user for each section. If they have an App Store ID, use get_app_detail to pre-fill what you can.

1. App Identity

  • App name (brand)
  • App Store ID (numeric) or slug
  • One-sentence description — what does the app do?
  • Target platform — iOS only, or also Android?

2. Target Audience

  • Primary audience — who is the main user?
  • Secondary audience — any secondary segments?
  • User problems — what pain points does the app solve?
  • User language — how do users describe their problem? (important for keywords)

3. Competitive Landscape

  • Direct competitors — apps that do the same thing (list 3–5)
  • Indirect competitors — apps that solve the same problem differently
  • Key differentiators — what makes this app unique?

4. Current Performance

Use get_app_detail if available:

  • Downloads/month (estimated)
  • Revenue/month (estimated)
  • Rating and review count
  • Current keywords (if known)
  • Running ads? Use search_apps for Meta/Apple presence signals and search_ads(appSlug) for creative records

5. Goals

  • Primary goal — downloads, revenue, ratings, brand awareness?
  • Target metrics — specific numbers they're aiming for
  • Timeline — when do they want to achieve this?
  • Budget — any ad budget or is it organic only?

Output Format

Generate an app-marketing-context.md file:

# App Marketing Context

## App
- **Name:** [name]
- **App Store ID:** [id]
- **Description:** [one-sentence]
- **Category:** [primary genre]
- **Price:** [free/paid/subscription]

## Audience
- **Primary:** [description]
- **Secondary:** [description]
- **Pain points:** [list]
- **Language:** [how users describe the problem]

## Competitors
| App | Strengths | Weaknesses |
|-----|-----------|-----------|
| [comp1] | [strengths] | [weaknesses] |

## Current Performance
- **Downloads/mo:** [est.]
- **Revenue/mo:** [est.]
- **Rating:** [★] ([count] reviews)
- **Known keywords:** [list]

## Goals
- **Primary:** [goal]
- **Target:** [metrics]
- **Timeline:** [timeframe]
- **Budget:** [amount or "organic only"]

## Notes
[Any additional context]

Related Skills

All other skills check for this file:

  • keyword-research — uses audience language and competitors
  • metadata-optimization — uses brand, keywords, value prop
  • competitor-analysis — uses competitor list and differentiators
  • growth-analysis — uses current performance as baseline
  • ad-intelligence — uses budget and goals
  • revenue-analysis — uses revenue targets and pricing model
  • app-discovery — uses category and competitive context

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.