@leejungkiin/awkit 1.1.4 → 1.1.7

package/skills/competitor-analysis/SKILL.md

@@ -0,0 +1,163 @@
+---
+name: competitor-analysis
+description: 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.
+metadata:
+  version: 1.0.0
+---
+
+# 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

package/skills/competitor-tracking/SKILL.md

@@ -0,0 +1,185 @@
+---
+name: competitor-tracking
+description: When the user wants to monitor competitor apps on an ongoing basis — tracking metadata changes, keyword shifts, screenshot updates, rating trends, or new features. Use when the user mentions "competitor monitoring", "track competitors", "competitor alert", "competitor changed their title", "watch a competitor app", "competitor weekly report", "competitive intelligence", or "what changed in competitor's listing". For a one-time deep competitive analysis, see competitor-analysis. For market-wide chart movements, see market-movers.
+metadata:
+  version: 1.0.0
+---
+
+# Competitor Tracking
+
+You set up and run ongoing competitor surveillance — catching metadata changes, keyword shifts, rating drops, and new feature launches before they impact your rankings.
+
+## One-Time Analysis vs Ongoing Tracking
+
+| | `competitor-analysis` skill | This skill (`competitor-tracking`) |
+|---|---|---|
+| **Frequency** | One-time deep dive | Weekly/monthly recurring |
+| **Output** | Strategy document | Change log + alerts |
+| **Focus** | Gap analysis, positioning | What changed and why it matters |
+| **Data** | Snapshot | Delta (before vs after) |
+
+## Setup: Define Your Watchlist
+
+1. Check for `app-marketing-context.md`
+2. Ask: **Who are your top 3–5 competitors?** (get App IDs if possible)
+3. Ask: **How often do you want to review?** (weekly recommended)
+4. Ask: **What are you most concerned about?** (keywords, ratings, creative, pricing)
+
+Use Appeeky to identify competitors if unknown:
+```bash
+GET /v1/keywords/ranks?keyword=meditation&country=us&limit=10
+GET /v1/apps/:id/intelligence  # check competitors array
+```
+
+## What to Track
+
+### Metadata Changes
+
+Check weekly using Appeeky:
+```bash
+GET /v1/apps/:id  # title, subtitle, description
+```
+
+Watch for:
+- **Title changes** — new keyword being targeted, repositioning
+- **Subtitle changes** — testing new hooks or keywords
+- **Description changes** — messaging strategy shift (Google Play especially)
+- **Screenshot updates** — new creative direction or A/B test winner shipped
+
+### Keyword Ranking Changes
+
+```bash
+GET /v1/apps/:id/keywords  # their ranking keywords
+GET /v1/keywords/ranks?keyword=[shared keyword]  # who's ranking where
+```
+
+Watch for:
+- Keywords they're newly ranking for (they optimized for this — should you?)
+- Keywords they dropped (opportunity to capture)
+- A competitor jumping above you for a shared keyword
+
+### Ratings and Reviews
+
+```bash
+GET /v1/apps/:id/reviews?sort=recent&limit=20
+GET /v1/apps/:id  # current rating
+```
+
+Watch for:
+- Rating drop (they shipped a bad update — opportunity to highlight your stability)
+- Surge of 1-stars around a specific complaint (user pain point you could solve)
+- New positive reviews praising a feature you don't have
+
+### Chart Positions
+
+```bash
+GET /v1/market/movers?genre=[genre_id]&country=us
+GET /v1/categories/:id/top?country=us&limit=25
+```
+
+Watch for:
+- A competitor entering or exiting top 10 in your category
+- New competitor entering your space from a chart rise
+
+### Pricing and Paywall
+
+Manually check every 4–6 weeks:
+- Trial length changes
+- Price changes (lower = aggressive growth; higher = LTV optimization)
+- New paywall format or plans
+
+## Weekly Competitive Report Template
+
+Run this analysis every Monday:
+
+```
+Competitive Update — Week of [Date]
+
+Apps tracked: [list names]
+
+CHANGES DETECTED:
+━━━━━━━━━━━━━━━━━
+[Competitor Name]
+  Metadata: [changed / no change]
+    → [specific change if any]
+  Top keywords: [gained X / lost Y / stable]
+  Rating: [X.X → X.X] ([+/-N] ratings this week)
+  Chart position: [#N → #N in category]
+  New reviews theme: [if notable]
+
+[Repeat per competitor]
+
+OPPORTUNITIES IDENTIFIED:
+1. [Competitor X dropped keyword Y — consider targeting it]
+2. [Competitor X has surge of complaints about Z — your strength]
+3. [Competitor X raised price — positioning opportunity]
+
+THREATS:
+1. [Competitor X now ranks #3 for [keyword] — we're at #8]
+2. [New entrant spotted: [name] — check their metadata]
+
+ACTION ITEMS:
+1. [Specific response to a change]
+2. [Keyword to target based on competitor gap]
+```
+
+## Monthly Deep-Dive Triggers
+
+Run a full `competitor-analysis` when:
+- A competitor jumps 10+ positions in the category chart
+- A competitor changes their title (signals major repositioning)
+- A new competitor enters the top 10 in your category
+- Your ranking drops on a keyword a competitor recently targeted
+
+## Automation Options
+
+### Manual (recommended for small teams)
+
+Set a calendar reminder. Run the Appeeky API calls above. Fill the template.
+
+### Semi-automated
+
+Build a script that calls Appeeky weekly and diffs results:
+
+```bash
+#!/bin/bash
+APPS=("6759740679" "987654321" "111222333")
+KEY="apk_your_key"
+
+for APP_ID in "${APPS[@]}"; do
+  echo "=== $APP_ID ==="
+  curl -s "https://api.appeeky.com/v1/apps/$APP_ID" \
+    -H "X-API-Key: $KEY" | jq '.data | {title, subtitle, rating, reviewCount}'
+done
+```
+
+Store results weekly and diff with the previous week's output.
+
+### Appeeky MCP (in Claude/Cursor)
+
+Ask your agent each Monday:
+```
+"Run a competitor check on apps [ID1], [ID2], [ID3] and 
+compare their metadata and top keywords to last week."
+```
+
+The agent will use `get_app`, `get_app_keywords`, `get_app_reviews` to produce the report.
+
+## Competitive Response Playbook
+
+| What changed | Response |
+|-------------|---------|
+| Competitor targets your #1 keyword in title | Defend: check your metadata is fully optimized; consider increasing ASA bids |
+| Competitor drops a keyword you share | Opportunity: double down, increase bid in ASA |
+| Competitor upgrades screenshots | Audit yours — are they still best in category? |
+| Competitor rating drops below 4.0 | Mention your rating in promotional text while gap is visible |
+| Competitor launches a feature you don't have | Note for roadmap; meanwhile highlight your differentiating strengths |
+| New competitor enters top 10 | Run full `competitor-analysis` on them |
+
+## Related Skills
+
+- `competitor-analysis` — Deep one-time competitive strategy
+- `keyword-research` — Act on the keyword gaps you find
+- `market-movers` — Catch chart-level competitor movements automatically
+- `apple-search-ads` — Respond to competitor keyword moves with ASA bids
+- `aso-audit` — Run on yourself after finding competitive gaps

package/skills/crash-analytics/SKILL.md

@@ -0,0 +1,181 @@
+---
+name: crash-analytics
+description: When the user wants to monitor, triage, or reduce their app's crash rate — including setting up Crashlytics, prioritizing which crashes to fix first, interpreting crash data, and understanding how crashes affect App Store ranking. Use when the user mentions "crash", "crashlytics", "crash rate", "ANR", "app not responding", "crash-free sessions", "crash-free users", "symbolication", "stability", "firebase crashes", "app crashing", or "crash report". For overall analytics setup, see app-analytics.
+metadata:
+  version: 1.0.0
+---
+
+# Crash Analytics
+
+You help triage, prioritize, and reduce app crashes — and understand how crash rate affects App Store discoverability and ratings.
+
+## Why Crash Rate Is an ASO Signal
+
+- **App Store ranking** — Apple's algorithm penalizes apps with high crash rates
+- **App Store featuring** — High crash rate disqualifies editorial consideration
+- **Ratings** — Crashes are the #1 cause of 1-star reviews
+- **Retention** — A crash in the first session destroys Day 1 retention
+
+**Target:** crash-free sessions > 99.5% | crash-free users > 99%
+
+## Tools
+
+| Tool | What it provides | Setup |
+|------|-----------------|-------|
+| **Firebase Crashlytics** | Real-time crashes, ANRs, symbolicated stack traces | Add `FirebaseCrashlytics` pod/SPM package |
+| **App Store Connect** | Crash rate trend, crashes per session | Built-in, no code needed |
+| **Xcode Organizer** | Aggregated crash logs from TestFlight + App Store | Xcode → Window → Organizer → Crashes |
+| **MetricKit** | On-device diagnostics, hang rate, launch time | iOS 13+, automatic |
+
+**Recommended:** Crashlytics (real-time alerts + search) + App Store Connect (trend validation)
+
+## Crashlytics Setup
+
+### iOS (Swift)
+
+```swift
+// AppDelegate or @main App struct
+import FirebaseCore
+import FirebaseCrashlytics
+
+@main
+struct MyApp: App {
+    init() {
+        FirebaseApp.configure()
+        // Crashlytics is auto-initialized
+    }
+}
+```
+
+### Non-fatal errors (track without crashing)
+
+```swift
+// Log a non-fatal error
+Crashlytics.crashlytics().record(error: error)
+
+// Log a custom key for debugging context
+Crashlytics.crashlytics().setCustomValue(userId, forKey: "user_id")
+Crashlytics.crashlytics().setCustomValue(screenName, forKey: "current_screen")
+```
+
+### Android (Kotlin)
+
+```kotlin
+// build.gradle (app)
+implementation("com.google.firebase:firebase-crashlytics:18.x.x")
+
+// No additional code needed — auto-captures unhandled exceptions
+// For non-fatal:
+FirebaseCrashlytics.getInstance().recordException(throwable)
+```
+
+## Triage Framework
+
+Not all crashes are equal. Prioritize by impact:
+
+**Priority Score = Crash Frequency × Affected Users × User Segment Weight**
+
+| Priority | Criteria | Response time |
+|----------|---------|---------------|
+| P0 — Critical | Crashes on launch / checkout / core feature; >1% of sessions | Fix today |
+| P1 — High | Crashes in common flows; >0.1% of sessions | Fix this release |
+| P2 — Medium | Edge case crashes; <0.1% of sessions | Fix next release |
+| P3 — Low | Rare, non-blocking crashes; <0.01% of sessions | Backlog |
+
+### Crashlytics Dashboard Triage
+
+1. Sort by **"Impact"** (unique users affected), not frequency
+2. Group: `onboarding`, `checkout`, `core feature`, `background`, `launch`
+3. Assign P0/P1 to the top 3–5 issues
+4. Set a **velocity alert** in Crashlytics for any issue affecting >0.5% of users
+
+## Reading a Crash Report
+
+```
+Fatal Exception: com.example.NullPointerException
+  at com.example.UserProfileVC.loadData:87
+  at com.example.HomeVC.viewDidLoad:45
+
+Keys:
+  user_id: 12345
+  current_screen: "home"
+  app_version: "2.3.1"
+  os_version: "iOS 17.3"
+```
+
+**Steps to debug:**
+1. Open the file and line in Xcode (`UserProfileVC.swift:87`)
+2. Check what can be nil at that point
+3. Reproduce with the user context (OS version, device, screen)
+4. Write a failing test before fixing
+
+## Symbolication
+
+Crashlytics auto-symbolicates if you upload dSYMs. If you see unsymbolicated traces:
+
+```bash
+# Manually upload dSYMs
+./Pods/FirebaseCrashlytics/upload-symbols -gsp GoogleService-Info.plist -p ios MyApp.app.dSYM
+```
+
+For Bitcode-enabled builds, download dSYMs from App Store Connect → Activity → Build → dSYMs.
+
+## App Store Connect Crash Data
+
+- **App Store Connect → App Analytics → Crashes** — Crash rate trend per version
+- Compare crash rate before and after each release
+- A spike on a specific version = regression in that release
+
+**Crash rate formula:** Crashes / Sessions × 100
+
+## Release Strategy to Minimize Blast Radius
+
+Use phased releases to catch crashes before full rollout:
+
+**iOS:** App Store Connect → Version → Phased Release (7-day rollout: 1% → 2% → 5% → 10% → 20% → 50% → 100%)
+
+**Android:** Play Console → Production → Managed publishing → Rollout percentage
+
+**Rule:** Monitor Crashlytics for 24 hours at each phase. If crash rate increases >0.2%, pause rollout.
+
+## Responding to Crash-Driven 1-Star Reviews
+
+1. Identify the app version where crash-related 1-stars appeared
+2. Fix the crash
+3. Reply to each crash-related review: "Fixed in version X.X — please update"
+4. After update ships, use `rating-prompt-strategy` to recover rating
+
+## Output Format
+
+### Crash Audit Report
+
+```
+Stability Report — [App Name] v[version] ([period])
+
+Crash-free sessions: [X]%  (target: >99.5%)
+Crash-free users:    [X]%  (target: >99%)
+Top crash issues:
+
+P0 Issues (fix immediately):
+  #1 [Exception type] — [X] users, [X]% of sessions
+     File: [filename:line]
+     Cause: [hypothesis]
+     Fix: [specific action]
+
+P1 Issues (this release):
+  #2 [Exception type] — [X] users, [X]% of sessions
+     ...
+
+Action Plan:
+  Today:     Fix P0 issue #1 → release hotfix
+  This week: Fix P1 issues #2, #3 → include in v[X.X]
+  Monitoring: Set velocity alert at 0.5% session threshold
+```
+
+## Related Skills
+
+- `app-analytics` — Full analytics stack; Crashlytics is one piece
+- `rating-prompt-strategy` — Recover rating after fixing crash-driven 1-stars
+- `review-management` — Respond to crash-related reviews
+- `retention-optimization` — Crashes on Day 1 destroy retention metrics
+- `app-store-featured` — Crash rate > 2% disqualifies editorial featuring

package/skills/in-app-events/SKILL.md

@@ -0,0 +1,176 @@
+---
+name: in-app-events
+description: When the user wants to create, plan, or optimize App Store In-App Events — the event cards that appear on the Today tab, search results, and your product page. Use when the user mentions "in-app event", "App Store event", "event card", "Today tab", "live event", "challenge", "game event", "seasonal event card", or wants visibility beyond organic search. For general ASO, see aso-audit. For seasonal keyword strategy, see seasonal-aso.
+metadata:
+  version: 1.0.0
+---
+
+# In-App Events
+
+You help the user plan, write, and optimize **App Store In-App Events** — event cards that surface in search, the Today tab, and the product page, driving installs and re-engagement without paid media.
+
+## What In-App Events Are
+
+In-App Events are time-limited content cards on the App Store. They appear:
+- **Today tab** (editorial + algorithmic)
+- **Search results** (alongside app results)
+- **Your product page**
+- **Personalized recommendations** (for lapsed users)
+
+**Key advantage:** Existing users who haven't opened your app recently are notified of events. Non-users see them as discovery.
+
+## Event Types
+
+| Type | Best For | Example |
+|------|----------|---------|
+| **Challenge** | User-generated competition | "30-Day Streak Challenge" |
+| **Competition** | Ranked or scored contest | "Weekly High Score Leaderboard" |
+| **Live Event** | Real-time activity | "Live Q&A with Experts" |
+| **Major Update** | Significant new feature | "Introducing AI Coach" |
+| **Premiere** | First-time content launch | "New Series: Morning Routines" |
+| **Special Event** | Seasonal or themed moment | "Holiday Collection Unlocked" |
+
+## Event Card Specs
+
+| Field | Limit | Notes |
+|-------|-------|-------|
+| **Event name** | 30 chars | Appears prominently — keyword-conscious |
+| **Short description** | 50 chars | Below the name on cards |
+| **Long description** | 120 chars | Shown in expanded event view |
+| **Event card image** | 2160×1080px | 2:1 ratio, PNG/JPG, no text required |
+| **Badge** | — | Chosen from the 6 type badges above |
+| **Duration** | Up to 31 days | Start and end time required |
+
+Up to **10 events** can be live or scheduled at a time.
+
+## Planning Workflow
+
+### Step 1 — Event Idea Selection
+
+1. Check for `app-marketing-context.md`
+2. Evaluate event type based on app category:
+
+| App Type | Best Event Types |
+|----------|----------------|
+| Games | Challenge, Competition, Major Update |
+| Fitness | Challenge, Live Event, Major Update |
+| Productivity | Major Update, Premiere |
+| Social / Community | Live Event, Challenge |
+| Streaming / Content | Premiere, Special Event |
+| Utility | Major Update, Special Event |
+
+3. Identify the primary goal:
+   - **Re-engagement** → Use notification-triggering events (any type)
+   - **New user acquisition** → Focus on Today tab visibility (Challenge or Competition)
+   - **Feature launch** → Major Update type
+
+### Step 2 — Write Event Copy
+
+**Event name (30 chars) — rules:**
+- Lead with the user benefit or action, not your app name
+- Include relevant keywords where natural
+- ✅ "30-Day Habit Challenge" | ❌ "AppName Challenge 2026"
+
+**Short description (50 chars):**
+- Answer "what's in it for me?" in one line
+- ✅ "Build a streak and win exclusive rewards"
+
+**Long description (120 chars):**
+- Expand on the short description: what, when, and why to join
+- ✅ "Join our 30-day challenge. Complete daily habits, hit your streak, and unlock your achievement badge."
+
+### Step 3 — Event Card Image
+
+Spec: 2160×1080px, 2:1 ratio
+
+**Best practices:**
+- No text needed (name/description appear as overlay) — but a short tagline is allowed
+- High contrast, bold visual that works at small thumbnail size
+- Show the outcome or reward, not just the app UI
+- Test thumbnail at 390×195px to verify legibility
+
+### Step 4 — Submit in App Store Connect
+
+1. App Store Connect → Your App → In-App Events → `+`
+2. Fill all required fields + upload image
+3. Submit for review (typically 24–48 hours)
+4. Schedule start/end times
+
+**Submit 3–5 days before** the desired start date to account for review time.
+
+## Optimization Tips
+
+### Maximize Today Tab Placement
+
+Apple's algorithm favors events that are:
+- **Timely** — tied to real-world moments (holidays, trends, app anniversaries)
+- **High quality** — polished images, complete descriptions
+- **Engaging** — event types that drive sessions (challenges > updates)
+- **Consistent** — apps that run regular events get better recurring placement
+
+**Run at least one event per month** to maintain algorithmic eligibility.
+
+### Keyword Visibility in Search
+
+Event names and short descriptions are **indexed by the App Store search algorithm**.
+
+- Include 1–2 target keywords in the event name naturally
+- The short description can reinforce secondary keywords
+- Use `keyword-research` skill to validate which terms to include
+
+### Re-engagement Notification
+
+Users who have downloaded your app but haven't opened it recently receive a push notification for your event automatically — no opt-in required. This is the highest-value feature of In-App Events.
+
+**Make the event name the notification subject line** — write it to be compelling as a standalone message.
+
+## Output Format
+
+### Event Brief
+
+```
+📅 Event: [Name — 30 chars]
+   Type:  [Badge type]
+   Dates: [Start] → [End]
+
+Copy:
+  Short:  [50 chars]
+  Long:   [120 chars]
+
+Image direction:
+  Visual: [describe the scene/concept]
+  Style:  [photography / illustration / abstract]
+  Key element: [the reward, the action, the outcome]
+
+Goals:
+  Primary: [re-engagement / acquisition / feature launch]
+  KPIs: [sessions spike, downloads, event page views]
+
+Submit by: [date — 4 days before start]
+```
+
+### Event Calendar (monthly)
+
+```
+Week 1:  [Event name] — [type] — [dates]
+Week 2:  [No event / buffer]
+Week 3:  [Event name] — [type] — [dates]
+Week 4:  [Event name] — [type] — [dates]
+```
+
+## Common Mistakes
+
+| Mistake | Fix |
+|---------|-----|
+| App name in event name | Lead with the user benefit |
+| Generic image (screenshot of UI) | Show the reward/outcome visually |
+| Events shorter than 7 days | Minimum 7 days for Today tab consideration |
+| Submitting day-of | Submit 4–5 days early for review |
+| No recurring schedule | Run 1+ events/month for sustained placement |
+
+## Related Skills
+
+- `seasonal-aso` — Align event timing with keyword seasonal peaks
+- `screenshot-optimization` — Apply same visual best practices to event images
+- `app-store-featured` — Events increase editorial feature eligibility
+- `retention-optimization` — Track re-engagement lift from events