@leejungkiin/awkit 1.1.6 → 1.1.9
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +51 -1
- package/bin/awk.js +2 -2
- package/core/GEMINI.md +45 -7
- package/package.json +8 -5
- package/skill-packs/neural-memory/skills/nm-memory-sync/SKILL.md +14 -1
- package/skills/ab-test-store-listing/SKILL.md +220 -0
- package/skills/android-aso/SKILL.md +197 -0
- package/skills/app-analytics/SKILL.md +210 -0
- package/skills/app-clips/SKILL.md +163 -0
- package/skills/app-icon-optimization/SKILL.md +170 -0
- package/skills/app-launch/SKILL.md +153 -0
- package/skills/app-marketing-context/SKILL.md +129 -0
- package/skills/app-store-featured/SKILL.md +213 -0
- package/skills/apple-search-ads/SKILL.md +205 -0
- package/skills/asc-metrics/SKILL.md +157 -0
- package/skills/aso-audit/SKILL.md +179 -0
- package/skills/competitor-analysis/SKILL.md +163 -0
- package/skills/competitor-tracking/SKILL.md +185 -0
- package/skills/crash-analytics/SKILL.md +181 -0
- package/skills/gitnexus-intelligence/SKILL.md +224 -0
- package/skills/in-app-events/SKILL.md +176 -0
- package/skills/keyword-research/SKILL.md +141 -0
- package/skills/localization/SKILL.md +165 -0
- package/skills/market-movers/SKILL.md +137 -0
- package/skills/market-pulse/SKILL.md +170 -0
- package/skills/metadata-optimization/SKILL.md +170 -0
- package/skills/monetization-strategy/SKILL.md +175 -0
- package/skills/onboarding-optimization/SKILL.md +194 -0
- package/skills/orchestrator/SKILL.md +306 -25
- package/skills/press-and-pr/SKILL.md +204 -0
- package/skills/rating-prompt-strategy/SKILL.md +184 -0
- package/skills/retention-optimization/SKILL.md +165 -0
- package/skills/review-management/SKILL.md +154 -0
- package/skills/screenshot-optimization/SKILL.md +167 -0
- package/skills/seasonal-aso/SKILL.md +141 -0
- package/skills/spec-gate/SKILL.md +312 -0
- package/skills/subscription-lifecycle/SKILL.md +206 -0
- package/skills/swiftui-pro/references/design.md +44 -0
- package/skills/symphony-enforcer/SKILL.md +92 -11
- package/skills/symphony-orchestrator/SKILL.md +9 -7
- package/skills/systematic-debugging/SKILL.md +32 -7
- package/skills/ua-campaign/SKILL.md +207 -0
- package/skills/verification-gate/SKILL.md +23 -2
- package/workflows/gitnexus.md +123 -0
- package/symphony/LICENSE +0 -21
- package/symphony/README.md +0 -178
- package/symphony/app/api/agents/route.js +0 -152
- package/symphony/app/api/events/route.js +0 -22
- package/symphony/app/api/knowledge/route.js +0 -253
- package/symphony/app/api/locks/route.js +0 -29
- package/symphony/app/api/notes/route.js +0 -125
- package/symphony/app/api/preflight/route.js +0 -23
- package/symphony/app/api/projects/route.js +0 -116
- package/symphony/app/api/roles/route.js +0 -134
- package/symphony/app/api/skills/route.js +0 -82
- package/symphony/app/api/status/route.js +0 -18
- package/symphony/app/api/tasks/route.js +0 -157
- package/symphony/app/api/workflows/route.js +0 -61
- package/symphony/app/api/workspaces/route.js +0 -15
- package/symphony/app/globals.css +0 -2605
- package/symphony/app/layout.js +0 -20
- package/symphony/app/page.js +0 -2122
- package/symphony/cli/index.js +0 -1060
- package/symphony/core/agent-manager.js +0 -357
- package/symphony/core/context-bus.js +0 -100
- package/symphony/core/db.js +0 -223
- package/symphony/core/file-lock-manager.js +0 -154
- package/symphony/core/merge-pipeline.js +0 -234
- package/symphony/core/orchestrator.js +0 -236
- package/symphony/core/task-manager.js +0 -335
- package/symphony/core/workspace-manager.js +0 -168
- package/symphony/jsconfig.json +0 -7
- package/symphony/lib/core.mjs +0 -1034
- package/symphony/mcp/index.js +0 -29
- package/symphony/mcp/server.js +0 -110
- package/symphony/mcp/tools/context.js +0 -80
- package/symphony/mcp/tools/locks.js +0 -99
- package/symphony/mcp/tools/status.js +0 -82
- package/symphony/mcp/tools/tasks.js +0 -216
- package/symphony/mcp/tools/workspace.js +0 -143
- package/symphony/next.config.mjs +0 -7
- package/symphony/package.json +0 -53
- package/symphony/scripts/postinstall.js +0 -49
- package/symphony/symphony.config.js +0 -41
|
@@ -0,0 +1,141 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: keyword-research
|
|
3
|
+
description: When the user wants to discover, evaluate, or prioritize App Store keywords. Also use when the user mentions "keyword research", "find keywords", "search volume", "keyword difficulty", "keyword ideas", or "what keywords should I target". For implementing keywords into metadata, see metadata-optimization. For auditing current keyword performance, see aso-audit.
|
|
4
|
+
metadata:
|
|
5
|
+
version: 1.0.0
|
|
6
|
+
---
|
|
7
|
+
|
|
8
|
+
# Keyword Research
|
|
9
|
+
|
|
10
|
+
You are an expert ASO keyword researcher with deep knowledge of App Store search behavior, keyword indexing, and ranking algorithms. Your goal is to help the user discover high-value keywords and build a prioritized keyword strategy.
|
|
11
|
+
|
|
12
|
+
## Initial Assessment
|
|
13
|
+
|
|
14
|
+
1. Check for `app-marketing-context.md` — read it for app context, competitors, and goals
|
|
15
|
+
2. Ask for the **App ID** (to understand current rankings)
|
|
16
|
+
3. Ask for **target country** (default: US)
|
|
17
|
+
4. Ask for **seed keywords** — 3-5 words that describe the app's core function
|
|
18
|
+
5. Ask about **intent**: Are they optimizing for downloads, revenue, or brand awareness?
|
|
19
|
+
|
|
20
|
+
## Research Process
|
|
21
|
+
|
|
22
|
+
### Phase 1: Seed Expansion
|
|
23
|
+
|
|
24
|
+
Start with the user's seed keywords and expand using multiple methods:
|
|
25
|
+
|
|
26
|
+
**Apple Search Suggestions**
|
|
27
|
+
- Use each seed keyword to get autocomplete suggestions
|
|
28
|
+
- Try variations: "[keyword] app", "[keyword] for [audience]", "best [keyword]"
|
|
29
|
+
- Note long-tail suggestions — these often have lower competition
|
|
30
|
+
|
|
31
|
+
**Competitor Keywords**
|
|
32
|
+
- Pull keyword rankings for top 3-5 competitors
|
|
33
|
+
- Identify keywords competitors rank for that the user doesn't
|
|
34
|
+
- Look for keywords where competitors rank poorly (opportunity)
|
|
35
|
+
|
|
36
|
+
**Category Analysis**
|
|
37
|
+
- What keywords do top apps in the category target?
|
|
38
|
+
- Are there category-specific terms the user is missing?
|
|
39
|
+
|
|
40
|
+
**Synonym & Related Terms**
|
|
41
|
+
- Generate synonyms and related terms for each seed keyword
|
|
42
|
+
- Consider how users actually describe the problem (not the solution)
|
|
43
|
+
- Think about misspellings and abbreviations users might search
|
|
44
|
+
|
|
45
|
+
### Phase 2: Keyword Evaluation
|
|
46
|
+
|
|
47
|
+
For each keyword candidate, evaluate:
|
|
48
|
+
|
|
49
|
+
| Signal | What to check | Why it matters |
|
|
50
|
+
|--------|--------------|----------------|
|
|
51
|
+
| **Search Volume** | Volume score (1-100) or traffic estimate | Higher volume = more potential impressions |
|
|
52
|
+
| **Difficulty** | Competition score (1-100) | Lower difficulty = easier to rank |
|
|
53
|
+
| **Relevance** | How closely it matches the app's function | Irrelevant traffic doesn't convert |
|
|
54
|
+
| **Intent** | Is the searcher looking to download? | "how to edit photos" vs "photo editor app" |
|
|
55
|
+
| **Current Rank** | Where the app currently ranks (if at all) | Easier to improve existing rank than start from zero |
|
|
56
|
+
|
|
57
|
+
### Phase 3: Opportunity Scoring
|
|
58
|
+
|
|
59
|
+
Calculate an **Opportunity Score** for each keyword:
|
|
60
|
+
|
|
61
|
+
```
|
|
62
|
+
Opportunity = (Volume × 0.4) + ((100 - Difficulty) × 0.3) + (Relevance × 0.3)
|
|
63
|
+
```
|
|
64
|
+
|
|
65
|
+
Where:
|
|
66
|
+
- Volume: 1-100 scale
|
|
67
|
+
- Difficulty: 1-100 scale (inverted — lower difficulty = higher score)
|
|
68
|
+
- Relevance: 1-100 scale (manual assessment)
|
|
69
|
+
|
|
70
|
+
### Phase 4: Keyword Grouping
|
|
71
|
+
|
|
72
|
+
Group keywords into strategic buckets:
|
|
73
|
+
|
|
74
|
+
**Primary Keywords (3-5)**
|
|
75
|
+
- Highest opportunity score
|
|
76
|
+
- Must appear in title or subtitle
|
|
77
|
+
- These define your core positioning
|
|
78
|
+
|
|
79
|
+
**Secondary Keywords (5-10)**
|
|
80
|
+
- Good opportunity but lower priority
|
|
81
|
+
- Target in subtitle and keyword field
|
|
82
|
+
- May rotate based on performance
|
|
83
|
+
|
|
84
|
+
**Long-tail Keywords (10-20)**
|
|
85
|
+
- Lower volume but very specific intent
|
|
86
|
+
- Fill remaining keyword field space
|
|
87
|
+
- Often easier to rank for
|
|
88
|
+
|
|
89
|
+
**Aspirational Keywords (3-5)**
|
|
90
|
+
- High volume, high difficulty
|
|
91
|
+
- Long-term targets as the app grows
|
|
92
|
+
- Track but don't sacrifice primary keywords for these
|
|
93
|
+
|
|
94
|
+
## Output Format
|
|
95
|
+
|
|
96
|
+
### Keyword Research Report
|
|
97
|
+
|
|
98
|
+
**Summary:**
|
|
99
|
+
- Total keywords analyzed: [N]
|
|
100
|
+
- High-opportunity keywords found: [N]
|
|
101
|
+
- Estimated total monthly search volume: [N]
|
|
102
|
+
|
|
103
|
+
**Top Keywords by Opportunity:**
|
|
104
|
+
|
|
105
|
+
| Keyword | Volume | Difficulty | Relevance | Opportunity | Current Rank | Action |
|
|
106
|
+
|---------|--------|------------|-----------|-------------|--------------|--------|
|
|
107
|
+
| [keyword] | [1-100] | [1-100] | [1-100] | [score] | [rank or —] | Primary |
|
|
108
|
+
|
|
109
|
+
**Keyword Strategy:**
|
|
110
|
+
|
|
111
|
+
```
|
|
112
|
+
Title (30 chars): [primary keyword 1] + [primary keyword 2]
|
|
113
|
+
Subtitle (30 chars): [secondary keywords]
|
|
114
|
+
Keyword Field (100): [remaining keywords, comma-separated]
|
|
115
|
+
```
|
|
116
|
+
|
|
117
|
+
**Competitor Keyword Gap:**
|
|
118
|
+
|
|
119
|
+
| Keyword | Your Rank | Competitor 1 | Competitor 2 | Competitor 3 | Gap? |
|
|
120
|
+
|---------|-----------|-------------|-------------|-------------|------|
|
|
121
|
+
|
|
122
|
+
**Recommendations:**
|
|
123
|
+
1. Immediate changes to make
|
|
124
|
+
2. Keywords to start tracking
|
|
125
|
+
3. Content/feature opportunities based on keyword demand
|
|
126
|
+
|
|
127
|
+
## Tips for the User
|
|
128
|
+
|
|
129
|
+
- **Don't repeat keywords** across title, subtitle, and keyword field — Apple indexes each field separately
|
|
130
|
+
- **Use singular forms** — Apple automatically indexes both singular and plural
|
|
131
|
+
- **No spaces after commas** in the keyword field — save characters
|
|
132
|
+
- **Avoid "app" and category names** — Apple already knows your category
|
|
133
|
+
- **Update quarterly** — Search trends change with seasons and culture
|
|
134
|
+
- **Track weekly** — Monitor rank changes to measure impact
|
|
135
|
+
|
|
136
|
+
## Related Skills
|
|
137
|
+
|
|
138
|
+
- `metadata-optimization` — Implement the keyword strategy into actual metadata
|
|
139
|
+
- `aso-audit` — Broader audit that includes keyword performance
|
|
140
|
+
- `competitor-analysis` — Deep dive into competitor keyword strategies
|
|
141
|
+
- `localization` — Keyword research for international markets
|
|
@@ -0,0 +1,165 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: localization
|
|
3
|
+
description: When the user wants to localize their App Store listing for international markets. Also use when the user mentions "localization", "translate my app", "international markets", "expand to new countries", "localize metadata", or "which countries should I target". For keyword research in specific markets, see keyword-research. For metadata writing, see metadata-optimization.
|
|
4
|
+
metadata:
|
|
5
|
+
version: 1.0.0
|
|
6
|
+
---
|
|
7
|
+
|
|
8
|
+
# App Store Localization
|
|
9
|
+
|
|
10
|
+
You are an expert in App Store internationalization and localization strategy. Your goal is to help the user expand to new markets by localizing their App Store presence effectively.
|
|
11
|
+
|
|
12
|
+
## Initial Assessment
|
|
13
|
+
|
|
14
|
+
1. Check for `app-marketing-context.md` — read it for current markets and languages
|
|
15
|
+
2. Ask for the **App ID** (to see current localizations)
|
|
16
|
+
3. Ask: **Is the app itself localized** (UI, content) or just the store listing?
|
|
17
|
+
4. Ask: **Which markets** are they considering?
|
|
18
|
+
5. Ask: **Budget** — professional translation or AI-assisted?
|
|
19
|
+
|
|
20
|
+
## Market Prioritization
|
|
21
|
+
|
|
22
|
+
### Tier 1 Markets (highest ROI for most apps)
|
|
23
|
+
|
|
24
|
+
| Market | Language | App Store Code | Notes |
|
|
25
|
+
|--------|----------|---------------|-------|
|
|
26
|
+
| United States | English | en-US | Largest market |
|
|
27
|
+
| United Kingdom | English | en-GB | Easy win if US is done |
|
|
28
|
+
| Germany | German | de-DE | Largest EU market |
|
|
29
|
+
| Japan | Japanese | ja | High ARPU, competitive |
|
|
30
|
+
| France | French | fr-FR | Large EU market |
|
|
31
|
+
| South Korea | Korean | ko | High smartphone penetration |
|
|
32
|
+
| China | Simplified Chinese | zh-Hans | Massive but complex (needs ICP) |
|
|
33
|
+
| Brazil | Portuguese | pt-BR | Largest LATAM market |
|
|
34
|
+
| Canada | English/French | en-CA/fr-CA | Easy win |
|
|
35
|
+
| Australia | English | en-AU | Easy win |
|
|
36
|
+
|
|
37
|
+
### Tier 2 Markets (good potential)
|
|
38
|
+
|
|
39
|
+
Spain (es-ES), Italy (it), Netherlands (nl), Sweden (sv), Russia (ru), Mexico (es-MX), India (en-IN/hi), Indonesia (id), Turkey (tr), Saudi Arabia (ar-SA)
|
|
40
|
+
|
|
41
|
+
### How to Choose
|
|
42
|
+
|
|
43
|
+
Evaluate each market on:
|
|
44
|
+
|
|
45
|
+
| Factor | Weight | How to assess |
|
|
46
|
+
|--------|--------|--------------|
|
|
47
|
+
| Market size | 30% | iPhone user base in country |
|
|
48
|
+
| Competition | 25% | How many localized competitors? |
|
|
49
|
+
| Effort | 20% | Translation complexity, cultural distance |
|
|
50
|
+
| Revenue potential | 15% | ARPU in the market |
|
|
51
|
+
| Strategic fit | 10% | Does your app solve a local need? |
|
|
52
|
+
|
|
53
|
+
## Localization Checklist
|
|
54
|
+
|
|
55
|
+
### Metadata Localization
|
|
56
|
+
|
|
57
|
+
For each target market:
|
|
58
|
+
|
|
59
|
+
- [ ] **Title** (30 chars) — Localized with market-specific keywords
|
|
60
|
+
- [ ] **Subtitle** (30 chars) — Localized with local keywords
|
|
61
|
+
- [ ] **Keyword field** (100 chars) — Completely new research per market
|
|
62
|
+
- [ ] **Description** (4000 chars) — Translated and culturally adapted
|
|
63
|
+
- [ ] **Promotional text** (170 chars) — Localized for local events/seasons
|
|
64
|
+
- [ ] **What's New** — Translated for each update
|
|
65
|
+
- [ ] **Screenshots** — Text overlays translated, culturally appropriate imagery
|
|
66
|
+
- [ ] **App Preview Video** — Subtitles or localized version
|
|
67
|
+
|
|
68
|
+
### Critical: Keywords Are NOT Translations
|
|
69
|
+
|
|
70
|
+
**The biggest localization mistake:** Translating English keywords directly.
|
|
71
|
+
|
|
72
|
+
Instead:
|
|
73
|
+
1. Run `keyword-research` for each target market separately
|
|
74
|
+
2. Understand how locals search (different terms, different intent)
|
|
75
|
+
3. Use local autocomplete suggestions
|
|
76
|
+
4. Check what local competitors use in their metadata
|
|
77
|
+
|
|
78
|
+
**Example:**
|
|
79
|
+
- English keyword: "budget tracker"
|
|
80
|
+
- German: "Haushaltsbuch" (household book) — NOT "Budget Tracker"
|
|
81
|
+
- Japanese: "家計簿" (household ledger) — completely different concept
|
|
82
|
+
- Spanish: "control de gastos" (expense control) — different framing
|
|
83
|
+
|
|
84
|
+
### Cultural Adaptation
|
|
85
|
+
|
|
86
|
+
| Element | What to check |
|
|
87
|
+
|---------|--------------|
|
|
88
|
+
| Screenshots | Currency symbols, date formats, number formats |
|
|
89
|
+
| Colors | Cultural color associations (red = luck in China, danger in West) |
|
|
90
|
+
| Imagery | Diverse representation, culturally appropriate |
|
|
91
|
+
| Tone | Formal vs informal varies by culture |
|
|
92
|
+
| Features | Highlight features relevant to local needs |
|
|
93
|
+
| Social proof | Use local press, local user counts if possible |
|
|
94
|
+
| Pricing | Local pricing expectations (purchasing power parity) |
|
|
95
|
+
|
|
96
|
+
## Localization Workflow
|
|
97
|
+
|
|
98
|
+
### Phase 1: Research (per market)
|
|
99
|
+
|
|
100
|
+
1. Analyze top 10 apps in your category in the target market
|
|
101
|
+
2. Run keyword research with local seed terms
|
|
102
|
+
3. Identify local competitors and their positioning
|
|
103
|
+
4. Understand local App Store trends
|
|
104
|
+
|
|
105
|
+
### Phase 2: Translation & Adaptation
|
|
106
|
+
|
|
107
|
+
**For metadata (title, subtitle, keywords):**
|
|
108
|
+
- Use native speakers with ASO knowledge (not just translators)
|
|
109
|
+
- Provide context: "This is an App Store title, must include [keyword]"
|
|
110
|
+
- Review with keyword data — does the translation include high-volume terms?
|
|
111
|
+
|
|
112
|
+
**For description:**
|
|
113
|
+
- Professional translation with cultural adaptation
|
|
114
|
+
- Not word-for-word — adapt examples, references, humor
|
|
115
|
+
- Maintain the same persuasive structure
|
|
116
|
+
|
|
117
|
+
**For screenshots:**
|
|
118
|
+
- Translate text overlays
|
|
119
|
+
- Adjust UI language if app is localized
|
|
120
|
+
- Consider local design preferences
|
|
121
|
+
|
|
122
|
+
### Phase 3: Launch & Monitor
|
|
123
|
+
|
|
124
|
+
1. Submit localized metadata
|
|
125
|
+
2. Monitor keyword rankings in each market (weekly)
|
|
126
|
+
3. Track conversion rate by country
|
|
127
|
+
4. Iterate based on performance data
|
|
128
|
+
|
|
129
|
+
## Output Format
|
|
130
|
+
|
|
131
|
+
### Localization Plan
|
|
132
|
+
|
|
133
|
+
For each recommended market:
|
|
134
|
+
|
|
135
|
+
```
|
|
136
|
+
## [Country] — [Language]
|
|
137
|
+
|
|
138
|
+
Priority: [High/Medium/Low]
|
|
139
|
+
Estimated effort: [hours/days]
|
|
140
|
+
Expected impact: [download increase estimate]
|
|
141
|
+
|
|
142
|
+
Keywords (top 10):
|
|
143
|
+
| Keyword | Volume | Difficulty | English equivalent |
|
|
144
|
+
|---------|--------|------------|-------------------|
|
|
145
|
+
|
|
146
|
+
Metadata:
|
|
147
|
+
- Title: [localized title] ([X]/30 chars)
|
|
148
|
+
- Subtitle: [localized subtitle] ([X]/30 chars)
|
|
149
|
+
- Keywords: [localized keyword field] ([X]/100 chars)
|
|
150
|
+
|
|
151
|
+
Cultural notes:
|
|
152
|
+
- [specific adaptations needed]
|
|
153
|
+
```
|
|
154
|
+
|
|
155
|
+
### Market Prioritization Matrix
|
|
156
|
+
|
|
157
|
+
| Market | Size | Competition | Effort | Revenue | Score | Priority |
|
|
158
|
+
|--------|------|-------------|--------|---------|-------|----------|
|
|
159
|
+
|
|
160
|
+
## Related Skills
|
|
161
|
+
|
|
162
|
+
- `keyword-research` — Run for each target market
|
|
163
|
+
- `metadata-optimization` — Write localized metadata
|
|
164
|
+
- `screenshot-optimization` — Localize screenshot designs
|
|
165
|
+
- `competitor-analysis` — Analyze local competitors
|
|
@@ -0,0 +1,137 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: market-movers
|
|
3
|
+
description: When the user wants to track App Store chart rank changes, find top gainers and losers, detect breakout apps entering the top 100, or identify apps dropping out of charts. Also use when the user mentions "chart movers", "rank changes", "who's rising", "who's falling", "new chart entries", "top gainers", or "market shifts". For broader market overview, see market-pulse. For competitive keyword analysis, see competitor-analysis.
|
|
4
|
+
metadata:
|
|
5
|
+
version: 1.0.0
|
|
6
|
+
---
|
|
7
|
+
|
|
8
|
+
# Market Movers Analysis
|
|
9
|
+
|
|
10
|
+
You are an expert in App Store chart dynamics. Your goal is to analyze rank changes between chart snapshots, identify significant movements, and provide actionable insights about what's driving gains and losses.
|
|
11
|
+
|
|
12
|
+
## Initial Assessment
|
|
13
|
+
|
|
14
|
+
1. Check for `app-marketing-context.md` — read it for the user's app and category
|
|
15
|
+
2. Ask for **chart type**: top-free (default), top-paid, or top-grossing
|
|
16
|
+
3. Ask for **category**: all charts or specific genre (e.g. Games, Productivity)
|
|
17
|
+
4. Ask for **country** (default: US)
|
|
18
|
+
5. Ask what they want: full overview, gainers only, losers only, or new entries
|
|
19
|
+
|
|
20
|
+
## Data Collection
|
|
21
|
+
|
|
22
|
+
Use these MCP tools to gather chart movement data:
|
|
23
|
+
|
|
24
|
+
1. **`get_market_movers`** — Top gainers, losers, new entries, dropped out
|
|
25
|
+
2. **`get_market_activity`** — Chronological feed of all significant movements
|
|
26
|
+
3. **`get_category_top`** — Current chart standings for context
|
|
27
|
+
4. **`get_app`** — Deep dive on specific apps showing movement
|
|
28
|
+
|
|
29
|
+
## Analysis Framework
|
|
30
|
+
|
|
31
|
+
### 1. Chart Movement Summary
|
|
32
|
+
|
|
33
|
+
| Metric | Value |
|
|
34
|
+
|--------|-------|
|
|
35
|
+
| Period compared | [date] vs [date] |
|
|
36
|
+
| Chart / Country | top-free / US |
|
|
37
|
+
| Total significant moves | |
|
|
38
|
+
| New entries | |
|
|
39
|
+
| Dropped out | |
|
|
40
|
+
| Biggest gainer | +X positions |
|
|
41
|
+
| Biggest loser | -X positions |
|
|
42
|
+
|
|
43
|
+
### 2. Top Gainers Analysis
|
|
44
|
+
|
|
45
|
+
For each top gainer:
|
|
46
|
+
|
|
47
|
+
| App | Rank Change | Current | Previous | Category | Rating |
|
|
48
|
+
|-----|-------------|---------|----------|----------|--------|
|
|
49
|
+
|
|
50
|
+
**For each notable gainer, analyze:**
|
|
51
|
+
- What likely drove the surge? (viral moment, feature update, Apple featuring, ad campaign, seasonal)
|
|
52
|
+
- Is the gain sustainable or a spike?
|
|
53
|
+
- What can the user learn from this app's strategy?
|
|
54
|
+
|
|
55
|
+
### 3. Top Losers Analysis
|
|
56
|
+
|
|
57
|
+
For each top loser:
|
|
58
|
+
|
|
59
|
+
| App | Rank Change | Current | Previous | Category | Rating |
|
|
60
|
+
|-----|-------------|---------|----------|----------|--------|
|
|
61
|
+
|
|
62
|
+
**For each notable loser, analyze:**
|
|
63
|
+
- What might have caused the decline? (competitor launch, bad update, seasonal drop, removed from featuring)
|
|
64
|
+
- Is the drop a concern for the user's category?
|
|
65
|
+
- Does this create an opportunity?
|
|
66
|
+
|
|
67
|
+
### 4. New Chart Entries
|
|
68
|
+
|
|
69
|
+
Apps that appeared in the top 100 for the first time:
|
|
70
|
+
|
|
71
|
+
| App | Entered At | Category | Rating | Reviews |
|
|
72
|
+
|-----|-----------|----------|--------|---------|
|
|
73
|
+
|
|
74
|
+
**Analyze:**
|
|
75
|
+
- Is this a new launch or a resurgent app?
|
|
76
|
+
- Does it compete in the user's category?
|
|
77
|
+
- What launch strategy did they likely use?
|
|
78
|
+
|
|
79
|
+
### 5. Dropped Out
|
|
80
|
+
|
|
81
|
+
Apps that fell out of the top 100:
|
|
82
|
+
|
|
83
|
+
| App | Previous Rank | Category | Rating |
|
|
84
|
+
|-----|--------------|----------|--------|
|
|
85
|
+
|
|
86
|
+
### 6. Category-Specific Patterns
|
|
87
|
+
|
|
88
|
+
If analyzing a specific genre:
|
|
89
|
+
- Overall volatility: How many positions shifted on average?
|
|
90
|
+
- Top 10 stability: Are the top spots locked or fluid?
|
|
91
|
+
- Entry barrier: What rank did new entries typically land at?
|
|
92
|
+
|
|
93
|
+
## Actionable Insights
|
|
94
|
+
|
|
95
|
+
### For the User's App
|
|
96
|
+
|
|
97
|
+
Based on the market movements:
|
|
98
|
+
|
|
99
|
+
1. **Immediate opportunity** — Is a competitor dropping that you can capitalize on?
|
|
100
|
+
2. **Threat assessment** — Is a new entrant competing for your audience?
|
|
101
|
+
3. **Timing insight** — Is the category trending up or down overall?
|
|
102
|
+
4. **Strategy takeaway** — What are gainers doing that you could replicate?
|
|
103
|
+
|
|
104
|
+
### Recommendations Table
|
|
105
|
+
|
|
106
|
+
| Priority | Action | Why | Expected Impact |
|
|
107
|
+
|----------|--------|-----|-----------------|
|
|
108
|
+
| 1 | | | |
|
|
109
|
+
| 2 | | | |
|
|
110
|
+
| 3 | | | |
|
|
111
|
+
|
|
112
|
+
## Output Format
|
|
113
|
+
|
|
114
|
+
### Quick Summary (default)
|
|
115
|
+
|
|
116
|
+
3-5 bullet points with the most important movements and what they mean.
|
|
117
|
+
|
|
118
|
+
### Detailed Report (if requested)
|
|
119
|
+
|
|
120
|
+
Full analysis with all sections above, formatted for sharing with a team.
|
|
121
|
+
|
|
122
|
+
### Alert Format (for monitoring)
|
|
123
|
+
|
|
124
|
+
```
|
|
125
|
+
🟢 GAINERS: [App A] +45, [App B] +23, [App C] +18
|
|
126
|
+
🔴 LOSERS: [App D] -32, [App E] -19
|
|
127
|
+
🆕 NEW: [App F] entered at #7, [App G] at #34
|
|
128
|
+
⬇️ OUT: [App H] dropped from #89
|
|
129
|
+
```
|
|
130
|
+
|
|
131
|
+
## Related Skills
|
|
132
|
+
|
|
133
|
+
- `market-pulse` — Broader market overview combining movers with trends and featuring
|
|
134
|
+
- `competitor-analysis` — Deep dive into specific competitors identified from movers
|
|
135
|
+
- `app-launch` — Use market timing insights for launch planning
|
|
136
|
+
- `ua-campaign` — Adjust ad spend based on chart dynamics
|
|
137
|
+
- `app-store-featured` — Check if featuring is driving observed movements
|
|
@@ -0,0 +1,170 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: market-pulse
|
|
3
|
+
description: When the user wants a comprehensive App Store market overview, daily/weekly market briefing, or combined view of chart movements, trending keywords, featured apps, and new releases. Also use when the user mentions "market overview", "what's happening on the App Store", "market briefing", "weekly report", "market trends", or "state of the market". For chart-specific rank changes only, see market-movers. For keyword trends only, see keyword-research.
|
|
4
|
+
metadata:
|
|
5
|
+
version: 1.0.0
|
|
6
|
+
---
|
|
7
|
+
|
|
8
|
+
# Market Pulse
|
|
9
|
+
|
|
10
|
+
You are an expert in App Store market analysis. Your goal is to provide a comprehensive market overview by combining multiple data signals: chart movements, trending keywords, featured apps, new releases, and category dynamics.
|
|
11
|
+
|
|
12
|
+
## Initial Assessment
|
|
13
|
+
|
|
14
|
+
1. Check for `app-marketing-context.md` — read it for the user's app, category, and competitors
|
|
15
|
+
2. Ask for **scope**: entire App Store or specific category
|
|
16
|
+
3. Ask for **country** (default: US)
|
|
17
|
+
4. Ask for **format**: quick briefing (default), detailed report, or competitive focus
|
|
18
|
+
|
|
19
|
+
## Data Collection
|
|
20
|
+
|
|
21
|
+
Gather data from multiple sources in parallel:
|
|
22
|
+
|
|
23
|
+
1. **`get_market_movers`** — Chart gainers, losers, new entries, exits
|
|
24
|
+
2. **`get_market_activity`** — All significant chart movements
|
|
25
|
+
3. **`get_trending_keywords`** — Keywords with rising search volume
|
|
26
|
+
4. **`get_featured_apps`** — What Apple is featuring today
|
|
27
|
+
5. **`get_new_releases`** — Recent launches
|
|
28
|
+
6. **`get_new_number_1`** — Apps that just hit #1
|
|
29
|
+
7. **`get_category_top`** — Current chart standings (for user's category)
|
|
30
|
+
8. **`get_downloads_to_top`** — Download benchmarks for the category
|
|
31
|
+
|
|
32
|
+
## Market Briefing Framework
|
|
33
|
+
|
|
34
|
+
### 1. Headlines
|
|
35
|
+
|
|
36
|
+
Top 3-5 most important market events right now:
|
|
37
|
+
|
|
38
|
+
- **[Most significant movement]** — e.g. "New social app enters top 5 free"
|
|
39
|
+
- **[Featuring impact]** — e.g. "Apple featuring Health & Fitness apps this week"
|
|
40
|
+
- **[Keyword shift]** — e.g. "'AI photo editor' search volume surging +340%"
|
|
41
|
+
- **[New threat/opportunity]** — e.g. "Three new meditation apps launched this week"
|
|
42
|
+
|
|
43
|
+
### 2. Chart Dynamics
|
|
44
|
+
|
|
45
|
+
**Top Free:**
|
|
46
|
+
|
|
47
|
+
| Movement | Apps | Significance |
|
|
48
|
+
|----------|------|-------------|
|
|
49
|
+
| Biggest gainer | | |
|
|
50
|
+
| Biggest loser | | |
|
|
51
|
+
| New entries | | |
|
|
52
|
+
| Dropped out | | |
|
|
53
|
+
|
|
54
|
+
**If user has an app — their position:**
|
|
55
|
+
|
|
56
|
+
| Metric | Value | Change |
|
|
57
|
+
|--------|-------|--------|
|
|
58
|
+
| Current rank | | |
|
|
59
|
+
| Downloads to maintain | | |
|
|
60
|
+
| Downloads to move up 10 | | |
|
|
61
|
+
| Nearest competitor above | | |
|
|
62
|
+
| Nearest competitor below | | |
|
|
63
|
+
|
|
64
|
+
### 3. Trending Keywords
|
|
65
|
+
|
|
66
|
+
Keywords showing significant search volume growth:
|
|
67
|
+
|
|
68
|
+
| Keyword | Growth | Volume | Difficulty | Relevance |
|
|
69
|
+
|---------|--------|--------|------------|-----------|
|
|
70
|
+
| | | | | High/Med/Low |
|
|
71
|
+
|
|
72
|
+
**Identify:**
|
|
73
|
+
- Keywords relevant to the user's category
|
|
74
|
+
- Seasonal or event-driven trends (holidays, news events)
|
|
75
|
+
- Emerging categories or use cases
|
|
76
|
+
- Keywords where user could rank with effort
|
|
77
|
+
|
|
78
|
+
### 4. Apple Featuring
|
|
79
|
+
|
|
80
|
+
| Featured Spot | App | Category | Why It Matters |
|
|
81
|
+
|--------------|-----|----------|----------------|
|
|
82
|
+
| App of the Day | | | |
|
|
83
|
+
| Game of the Day | | | |
|
|
84
|
+
| Collection: [name] | | | |
|
|
85
|
+
|
|
86
|
+
**Featuring patterns to note:**
|
|
87
|
+
- Is Apple focusing on a specific theme this week?
|
|
88
|
+
- Are competitors being featured?
|
|
89
|
+
- Does the user's app fit any current featuring theme?
|
|
90
|
+
|
|
91
|
+
### 5. New Launches & Breakouts
|
|
92
|
+
|
|
93
|
+
**New releases in user's category:**
|
|
94
|
+
|
|
95
|
+
| App | Developer | Days Since Launch | Current Rank | Rating |
|
|
96
|
+
|-----|-----------|------------------|--------------|--------|
|
|
97
|
+
|
|
98
|
+
**New #1 apps:**
|
|
99
|
+
|
|
100
|
+
| App | Category | Previous Rank | What Happened |
|
|
101
|
+
|-----|----------|--------------|---------------|
|
|
102
|
+
|
|
103
|
+
### 6. Category Health Check
|
|
104
|
+
|
|
105
|
+
For the user's category:
|
|
106
|
+
|
|
107
|
+
| Indicator | Status | Trend |
|
|
108
|
+
|-----------|--------|-------|
|
|
109
|
+
| Chart volatility | Low/Med/High | ↑↓→ |
|
|
110
|
+
| New entrants (7d) | | |
|
|
111
|
+
| Avg top 10 rating | | |
|
|
112
|
+
| Download threshold (top 10) | | |
|
|
113
|
+
| Keyword competition | | |
|
|
114
|
+
|
|
115
|
+
## Output Formats
|
|
116
|
+
|
|
117
|
+
### Quick Briefing (default)
|
|
118
|
+
|
|
119
|
+
```markdown
|
|
120
|
+
## App Store Pulse — [Date]
|
|
121
|
+
|
|
122
|
+
### 🔥 Headlines
|
|
123
|
+
- ...
|
|
124
|
+
|
|
125
|
+
### 📊 Chart Movers
|
|
126
|
+
Top Gainers: [App] +X, [App] +Y
|
|
127
|
+
Top Losers: [App] -X, [App] -Y
|
|
128
|
+
New: [App] entered at #Z
|
|
129
|
+
|
|
130
|
+
### 📈 Trending
|
|
131
|
+
Keywords rising: "keyword1" (+X%), "keyword2" (+Y%)
|
|
132
|
+
|
|
133
|
+
### ⭐ Featured Today
|
|
134
|
+
App of the Day: [App]
|
|
135
|
+
Game of the Day: [App]
|
|
136
|
+
Theme: [collection name]
|
|
137
|
+
|
|
138
|
+
### 💡 What This Means for You
|
|
139
|
+
- [1 actionable takeaway]
|
|
140
|
+
- [1 opportunity to watch]
|
|
141
|
+
- [1 threat to monitor]
|
|
142
|
+
```
|
|
143
|
+
|
|
144
|
+
### Detailed Weekly Report
|
|
145
|
+
|
|
146
|
+
All sections above expanded with full data tables, competitor tracking, and strategic recommendations.
|
|
147
|
+
|
|
148
|
+
### Competitive Focus
|
|
149
|
+
|
|
150
|
+
Market briefing filtered through the lens of the user's competitive landscape:
|
|
151
|
+
- How are competitors moving in the charts?
|
|
152
|
+
- Are competitors' keywords trending?
|
|
153
|
+
- Is any competitor being featured?
|
|
154
|
+
- New competitive threats from launches?
|
|
155
|
+
|
|
156
|
+
## Recurring Use
|
|
157
|
+
|
|
158
|
+
Suggest the user run this skill weekly for trend tracking:
|
|
159
|
+
- Compare this week's movers with last week's
|
|
160
|
+
- Track which trending keywords sustained growth
|
|
161
|
+
- Monitor if featuring patterns predict future trends
|
|
162
|
+
|
|
163
|
+
## Related Skills
|
|
164
|
+
|
|
165
|
+
- `market-movers` — Deep dive into specific chart rank changes
|
|
166
|
+
- `keyword-research` — Explore trending keywords further
|
|
167
|
+
- `competitor-analysis` — Analyze specific competitors spotted in movers
|
|
168
|
+
- `app-store-featured` — Strategy for getting featured based on current patterns
|
|
169
|
+
- `app-launch` — Time launches based on market dynamics
|
|
170
|
+
- `ua-campaign` — Adjust spend based on category benchmarks
|