SKILLS/app-marketing-context/SKILL.md
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.
npx skillsauth add pinkpixel-dev/skills-collection-1 app-marketing-contextInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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.
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.
Create app-marketing-context.md with these sections:
## 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]
Ask the user:
## 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]
Ask the user:
## Competitors
| App | App ID | Strengths | Weaknesses |
|-----|--------|-----------|------------|
| [name] | [id] | [strengths] | [weaknesses] |
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]
Ask the user:
## Goals
1. [goal 1] — Target: [metric] by [date]
2. [goal 2] — Target: [metric] by [date]
3. [goal 3] — Target: [metric] by [date]
## Resources
- **Budget:** [monthly marketing budget, if any]
- **Team:** [solo / small team / marketing team]
- **Tools:** [analytics, ASA, MMP, etc.]
- **Constraints:** [any limitations — time, budget, technical]
## Markets
- **Primary:** [country/region]
- **Secondary:** [countries/regions]
- **Languages:** [supported languages]
Save the completed document as app-marketing-context.md in the project root.
After creating it, summarize:
aso-audit, keyword-research)All other skills reference this context. Start here before using:
aso-audit — Full ASO health checkkeyword-research — Keyword discoverycompetitor-analysis — Deep competitive analysistesting
When the user wants a full ASO health audit, review their App Store listing quality, or diagnose why their app isn't ranking. Also use when the user mentions "ASO audit", "ASO score", "why am I not ranking", "listing review", or "optimize my app store page". For keyword-specific research, see keyword-research. For metadata writing, see metadata-optimization.
testing
Clarify requirements before implementing. Use when serious doubts arise.
tools
Complete reference and build guide for ASI:One (ASI1) — the AI platform by Fetch.ai built for agentic, Web3-native applications. Use this skill IMMEDIATELY and ALWAYS when the user mentions ASI1, ASI:One, Fetch.ai AI API, building with ASI1, integrating ASI:One, asking about ASI1 models, tool calling with ASI1, ASI1 image generation, ASI1 agentic LLM, Agentverse, uagents, Agent Chat Protocol, structured output with ASI1, or OpenAI-compatible wrappers for ASI1. Also trigger when the user says things like "use ASI1 instead of OpenAI", "build an app with ASI:One", "ASI1 API", or references docs.asi1.ai. This skill covers everything needed to build production apps - setup, all models, all API features, tool calling, image gen, agentic orchestration, structured data, session management, streaming, LangChain integration, uagents / Agent Chat Protocol, and TypeScript/Node.js patterns.
data-ai
When the user wants to analyze their own app's actual performance data from App Store Connect — real downloads, revenue, IAP, subscriptions, trials, or country breakdowns synced via Appeeky Connect. Use when the user asks about "my downloads", "my revenue", "how is my app performing", "ASC data", "sales and trends", "my subscription numbers", "App Store Connect metrics", or wants to compare periods or top markets. For third-party app estimates, see app-analytics. For subscription analytics depth, see monetization-strategy.