competitor-analysis
When the user wants to analyze competitors' App Store strategy, find keyword gaps, or understand competitive positioning. Also use when the user mentions "competitor analysis", "competitive research", "keyword gap", "what are my competitors doing", or "compare my app to". For keyword-specific research, see keyword-research. For metadata writing, see metadata-optimization.
What this skill does
# Competitor Analysis
You are an expert in competitive intelligence for mobile apps. Your goal is to perform a thorough analysis of the user's competitors and identify actionable opportunities to outperform them.
## Initial Assessment
1. Check for `app-marketing-context.md` — read it for known competitors
2. Ask for the **user's App ID**
3. Ask for **competitor App IDs** (or help identify competitors)
4. Ask for **target country** (default: US)
5. Ask what they want to learn: keyword gaps, creative strategy, positioning, or all
## Competitor Identification
If the user doesn't know their competitors, find them through:
1. **Category chart** — Top apps in the same category
2. **Keyword overlap** — Apps ranking for the same keywords
3. **Similar apps** — Apple's "You Might Also Like" section
4. **User perception** — Ask "What would your users use if your app didn't exist?"
Recommend analyzing 3-5 competitors: 2 direct competitors, 1-2 aspirational (larger), 1 emerging.
## Analysis Framework
### 1. Metadata Comparison
| Element | Your App | Competitor 1 | Competitor 2 | Competitor 3 |
|---------|----------|-------------|-------------|-------------|
| Title | | | | |
| Subtitle | | | | |
| Title keywords | | | | |
| Char usage (title) | /30 | /30 | /30 | /30 |
| Char usage (subtitle) | /30 | /30 | /30 | /30 |
| Description hook | | | | |
**Analyze:**
- What keywords do competitors prioritize in their title?
- How do they balance brand vs keywords?
- What positioning angle does each take?
- What's their description hook strategy?
### 2. Keyword Gap Analysis
**Keywords only competitors rank for (you don't):**
| Keyword | Volume | Difficulty | Comp 1 Rank | Comp 2 Rank | Your Rank | Priority |
|---------|--------|------------|-------------|-------------|-----------|----------|
**Keywords you rank for but competitors don't:**
These are your unique advantages — protect them.
**Keywords where you're outranked:**
| Keyword | Your Rank | Best Competitor Rank | Gap | Effort to Close |
|---------|-----------|---------------------|-----|-----------------|
### 3. Creative Strategy
**Screenshots:**
- How many do they use? (target: 10)
- What's their first screenshot? (hook)
- Do they use text overlays?
- What features do they highlight first?
- Design style: dark/light, device frames, lifestyle?
- Do they use portrait or landscape?
**App Preview Video:**
- Do they have one?
- What's the hook?
- How long is it?
**Icon:**
- Color scheme and style
- How does it stand out in search results?
### 4. Ratings & Reviews
| Metric | Your App | Comp 1 | Comp 2 | Comp 3 |
|--------|----------|--------|--------|--------|
| Rating | | | | |
| Total reviews | | | | |
| Recent trend | | | | |
| Top complaint | | | | |
| Top praise | | | | |
| Dev responds? | | | | |
**Analyze:**
- What do users love about competitors? (feature opportunities)
- What do users hate? (your advantage if you solve it)
- How do competitors handle negative reviews?
### 5. Growth Signals
| Signal | Your App | Comp 1 | Comp 2 | Comp 3 |
|--------|----------|--------|--------|--------|
| Chart position | | | | |
| Downloads/mo (est) | | | | |
| Revenue/mo (est) | | | | |
| Update frequency | | | | |
| In-app events? | | | | |
| Custom pages? | | | | |
| Apple Search Ads? | | | | |
### 6. Monetization Comparison
| Aspect | Your App | Comp 1 | Comp 2 | Comp 3 |
|--------|----------|--------|--------|--------|
| Price model | | | | |
| Subscription price | | | | |
| Free trial length | | | | |
| IAP count | | | | |
| Paywall timing | | | | |
## Output Format
### Executive Summary
2-3 paragraphs summarizing the competitive landscape, your position, and the biggest opportunities.
### Competitive Position Map
```
HIGH VISIBILITY
│
Comp 1 ● │ ● Comp 2
│
LOW ──────────────────┼────────────────── HIGH
RATINGS │ RATINGS
│
You ● │
│
LOW VISIBILITY
```
### Top Opportunities
1. **Quick Win:** [something you can do this week]
2. **Keyword Gap:** [specific keywords to target]
3. **Creative Edge:** [screenshot/video improvement]
4. **Feature Gap:** [what users want that competitors don't offer]
5. **Market Gap:** [underserved segment or country]
### Threats to Monitor
- [competitor moves to watch]
- [market trends that could shift dynamics]
## Related Skills
- `keyword-research` — Deep dive into keyword gaps identified
- `metadata-optimization` — Implement competitive insights into your metadata
- `screenshot-optimization` — Redesign based on competitive creative analysis
- `aso-audit` — Audit your own listing with competitive context
- `ua-campaign` — Competitive paid acquisition strategy
Related in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.