USP

Unlike generic advice, these skills package battle-tested ASO frameworks and real App Store data into your AI agent, delivering specific, actionable recommendations for app growth. It transforms expert knowledge into an accessible, in-IDE…

Use cases

01Run an ASO audit for your app
02Find the best keywords for a meditation app
03Optimize your App Store title and subtitle
04Plan a Christmas In-App Event
05Set up a weekly competitor monitoring routine

Detected files (8)

skills/app-marketing-context/SKILL.mdskill

Show content (3655 bytes)

---
name: app-marketing-context
description: 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.
metadata:
  version: 1.0.0
---

# App Marketing Context

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.

## Initial Assessment

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.

## Context Document Structure

Create `app-marketing-context.md` with these sections:

### 1. App Overview

```markdown
## 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]
```

### 2. Value Proposition

Ask the user:
1. What problem does your app solve?
2. Who is your ideal user? (demographics, behavior, needs)
3. What makes your app different from alternatives?
4. What is your one-sentence elevator pitch?

```markdown
## 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]
```

### 3. Competitive Landscape

Ask the user:
1. Who are your top 3-5 competitors?
2. What do they do well?
3. Where do they fall short?

```markdown
## Competitors
| App | App ID | Strengths | Weaknesses |
|-----|--------|-----------|------------|
| [name] | [id] | [strengths] | [weaknesses] |
```

### 4. Current ASO State

If the user has an App ID, offer to pull current metadata:

```markdown
## Current ASO State
- **Title:** [current title]
- **Subtitle:** [current subtitle]
- **Keyword Field:** [if known]
- **Rating:** [stars] ([count] ratings)
- **Primary Keywords:** [top keywords they rank for]
```

### 5. Goals & KPIs

Ask the user:
1. What are your top 3 goals? (downloads, revenue, retention, rankings)
2. What metrics do you track?
3. What's your timeline?

```markdown
## Goals
1. [goal 1] — Target: [metric] by [date]
2. [goal 2] — Target: [metric] by [date]
3. [goal 3] — Target: [metric] by [date]
```

### 6. Resources & Constraints

```markdown
## Resources
- **Budget:** [monthly marketing budget, if any]
- **Team:** [solo / small team / marketing team]
- **Tools:** [analytics, ASA, MMP, etc.]
- **Constraints:** [any limitations — time, budget, technical]
```

### 7. Markets

```markdown
## Markets
- **Primary:** [country/region]
- **Secondary:** [countries/regions]
- **Languages:** [supported languages]
```

## Output

Save the completed document as `app-marketing-context.md` in the project root.

After creating it, summarize:
- Key strengths to leverage
- Obvious gaps to address
- Recommended next skills to use (e.g., `aso-audit`, `keyword-research`)

## Related Skills

All other skills reference this context. Start here before using:
- `aso-audit` — Full ASO health check
- `keyword-research` — Keyword discovery
- `competitor-analysis` — Deep competitive analysis

skills/android-aso/SKILL.mdskill

Show content (6805 bytes)

---
name: android-aso
description: When the user wants to optimize their Google Play Store listing — title, short description, full description, keywords, ratings, or Play Store-specific features. Use when the user mentions "Google Play", "Android", "Play Store", "Play Console", "short description", "full description indexed", "Google Play ASO", or wants Google Play-specific keyword, creative, or ratings strategy. For iOS App Store optimization, see aso-audit and metadata-optimization.
metadata:
  version: 1.0.0
---

# Android ASO (Google Play)

You are a Google Play ASO expert. Google Play's algorithm differs fundamentally from iOS — the full description is indexed, there is no hidden keyword field, and ratings are continuous (not version-reset).

## Key Differences vs iOS

| Factor | Google Play | Apple App Store |
|--------|------------|----------------|
| **Keyword indexing** | Title + Short desc + Full desc (all indexed) | Title + Subtitle + Keyword field only |
| **Hidden keyword field** | ✗ None | ✓ 100-char field |
| **Description indexed** | ✓ Full 4000 chars | ✗ Not indexed |
| **Ratings** | Continuous — never reset | Reset per version (can request reset) |
| **A/B testing** | Play Store Experiments (native) | Product Page Optimization |
| **Screenshots** | 2–8 per language | Up to 10 per language |
| **Feature graphic** | Required (1024×500px) | Not applicable |
| **Algorithm signals** | Installs, engagement, ratings, keywords | Keyword match, ratings, conversions |
| **Review indexing** | Reviews and replies indexed | Not indexed |

## Character Limits

| Field | Limit | Indexed | Weight |
|-------|-------|---------|--------|
| **Title** | 30 chars | ✓ | Highest |
| **Short description** | 80 chars | ✓ | High |
| **Full description** | 4000 chars | ✓ | Medium |
| **Developer name** | — | ✓ | Low |

## Initial Assessment

1. Check for `app-marketing-context.md`
2. Ask: **Do you have Play Console access?** (for actual keyword data)
3. Ask: **What is your current title and short description?**
4. Ask: **What are your 3 most important keywords?**
5. Ask: **What category is your app in?**

## Metadata Optimization

### Title (30 chars)

- Lead with your brand name or primary keyword — whichever is stronger
- Include 1 high-volume keyword naturally: `Brand – Keyword Descriptor`
- ✅ "Headspace: Meditation & Sleep" | ❌ "Best Meditation App for You"

### Short Description (80 chars)

- First thing users read on search results
- Pack your 2–3 most important keywords naturally in one compelling sentence
- ✅ "Guided meditation, sleep sounds & breathing exercises for stress relief"
- Do not repeat the title's primary keyword

### Full Description (4000 chars — indexed)

**Structure for algorithm + conversion:**

```
[Hook paragraph — 2–3 sentences]
Lead with the core value proposition. Include primary keyword in first 167 chars
(shown above the fold).

[Feature bullets — 5–8 items]
• [Feature]: [Benefit]
Use keywords naturally. Vary phrasing — don't repeat exact phrases.

[Social proof]
"Trusted by X million users" / awards / press mentions

[Call to action]
Download [App Name] today — [value prop].

[Keywords section — natural, not stuffed]
A paragraph using keyword variants, synonyms, and long-tail terms.
```

**Keyword density rule:** Target keyword should appear 3–5 times across the full description. Exact match + variants. Never stuff.

### Localization

Google Play indexes descriptions per language. Each locale is a fresh keyword opportunity — translate and localize, don't just auto-translate.

## Keyword Research for Play Store

Use Appeeky keyword tools, then adapt for Play:

```bash
GET /v1/keywords/metrics?keywords=meditation,mindfulness,sleep sounds&country=us
GET /v1/keywords/suggestions?term=meditation&country=us
```

**Play-specific considerations:**
- Long-tail phrases work well (full description is indexed)
- Semantic similarity matters — Google's algorithm understands synonyms
- User reviews and Q&A also get indexed — common words in reviews can signal keywords

## Feature Graphic (1024×500px)

Required for Play Store. Appears at the top of your listing when no video is present.

- Show the core use case in one image
- Text is legible — no tiny copy
- Brand-consistent with screenshots
- Works without text (text may be truncated on some surfaces)

## Ratings Strategy

Unlike iOS, Play ratings are **never reset** — every rating ever given counts.

**To improve your rating:**
1. Respond to every 1–3 star review (boosts score algorithmically)
2. Reply invites re-rating — users can update their review
3. Use `review-management` skill for response templates
4. Fix the issues mentioned in low ratings and reply: "Fixed in version X.X"

**Rating prompt timing** (see also `rating-prompt-strategy` skill):
- Prompt after a clear success moment, not on cold open
- Use the Play In-App Review API: `ReviewManager.requestReviewFlow()`

## Play Store Experiments (A/B Testing)

Native A/B testing for:
- Icon
- Feature graphic
- Screenshots (up to 3 variants)
- Short description (up to 3 variants)
- Full description (up to 3 variants)

Access: Play Console → Store listing experiments

**Test one element at a time. Run for minimum 7 days or 1,000 impressions.**

## Pre-Launch (Early Access)

Use Early Access to:
- Collect reviews before public launch
- Get indexed by Google before launch
- Get editorial consideration from Google Play

## Output Format

### Play Store Listing Draft

```
Title (30):     [text]
Short desc (80): [text]

Full Description:
[Hook — 2–3 sentences, primary keyword in first 167 chars]

✨ Features:
• [Feature]: [Benefit]
• [Feature]: [Benefit]
• [Feature]: [Benefit]
• [Feature]: [Benefit]
• [Feature]: [Benefit]

[Social proof paragraph]

[CTA sentence]

[Keyword-rich closing paragraph]

Keywords targeted: [list primary keywords used]
```

### ASO Audit (Play)

Score each field 1–10:

```
Title:             [N]/10 — [note]
Short description: [N]/10 — [note]
Full description:  [N]/10 — [note]
Screenshots:       [N]/10 — [note]
Feature graphic:   [N]/10 — [note]
Ratings:           [N]/10 — [note]
Overall:           [N]/60

Top 3 improvements:
1. [specific change with expected impact]
2. [specific change with expected impact]
3. [specific change with expected impact]
```

## Related Skills

- `aso-audit` — iOS-focused audit (compare approaches)
- `metadata-optimization` — iOS metadata (different field rules)
- `review-management` — Respond to Play reviews to recover rating
- `rating-prompt-strategy` — In-App Review API timing and strategy
- `ab-test-store-listing` — Play Experiments methodology
- `localization` — Per-language listing optimization

skills/app-analytics/SKILL.mdskill

Show content (6980 bytes)

---
name: app-analytics
description: When the user wants to set up, interpret, or improve their app analytics and tracking. Also use when the user mentions "analytics", "tracking", "metrics", "KPIs", "App Store Connect analytics", "install tracking", "funnel", "attribution", or "how is my app performing". For A/B testing, see ab-test-store-listing. For retention metrics, see retention-optimization.
metadata:
  version: 1.0.0
---

# App Analytics

You are an expert in mobile app analytics and measurement strategy. Your goal is to help the user set up meaningful tracking, interpret their data, and make data-driven decisions.

## Initial Assessment

1. Check for `app-marketing-context.md` — read it for context
2. Ask: **What analytics tools do you currently use?**
3. Ask: **What are your top 3 questions about your app's performance?**
4. Ask: **What decisions do you need data to make?**
5. Ask: **Do you run paid acquisition?** (attribution matters)

## Analytics Stack

### Essential Tools

| Tool | Purpose | Cost | Priority |
|------|---------|------|----------|
| **App Store Connect** | Store metrics, downloads, conversion | Free | Must have |
| **Firebase Analytics** | In-app events, funnels, audiences | Free | Must have |
| **Mixpanel / Amplitude** | Product analytics, cohorts, funnels | Free tier | Recommended |
| **RevenueCat** | Subscription analytics, paywall testing | Free tier | If subscriptions |
| **Adjust / AppsFlyer** | Attribution, UA measurement | Paid | If running ads |
| **Crashlytics** | Crash reporting, stability | Free | Must have |

### App Store Connect Analytics

**Key metrics available for free:**

| Metric | What it tells you |
|--------|------------------|
| **Impressions** | How many times your app appeared in search/browse |
| **Product Page Views** | How many users visited your product page |
| **App Units** | First-time downloads |
| **Conversion Rate** | Product Page Views → Downloads |
| **Proceeds** | Revenue after Apple's cut |
| **Sessions** | App opens |
| **Active Devices** | Unique devices using the app |
| **Retention** | Day 1, Day 7, Day 28 retention |
| **Crash Rate** | Crashes per session |

**Source types:**
- App Store Search
- App Store Browse
- Web Referral
- App Referral

## Key Metrics Framework

### Acquisition Metrics

| Metric | Formula | What it means |
|--------|---------|--------------|
| **Impressions** | — | Visibility in App Store |
| **Tap-Through Rate** | Taps / Impressions | Icon + title effectiveness |
| **Conversion Rate** | Downloads / Page Views | Product page effectiveness |
| **CPI** | Ad Spend / Installs | Cost efficiency of paid UA |
| **Organic %** | Organic / Total Installs | Health of organic growth |

### Engagement Metrics

| Metric | Formula | What it means |
|--------|---------|--------------|
| **DAU** | Daily Active Users | Daily engagement |
| **MAU** | Monthly Active Users | Monthly reach |
| **DAU/MAU** | DAU / MAU | Stickiness (>20% is good) |
| **Sessions/User** | Total Sessions / DAU | Engagement depth |
| **Session Length** | Avg time per session | Value delivery |

### Retention Metrics

| Metric | Formula | Benchmark |
|--------|---------|-----------|
| **Day 1** | Users Day 1 / Installs | 25-40% |
| **Day 7** | Users Day 7 / Installs | 10-20% |
| **Day 30** | Users Day 30 / Installs | 5-10% |
| **Churn Rate** | Lost Users / Start Users | < 5% monthly (subscriptions) |

### Revenue Metrics

| Metric | Formula | What it means |
|--------|---------|--------------|
| **ARPU** | Revenue / All Users | Average revenue per user |
| **ARPPU** | Revenue / Paying Users | Paying user value |
| **LTV** | ARPU × Avg Lifetime | Total user value |
| **Trial-to-Paid** | Conversions / Trial Starts | Paywall effectiveness |
| **MRR** | Monthly Recurring Revenue | Subscription health |
| **Churn Revenue** | Lost MRR / Start MRR | Revenue retention |

## Event Tracking Plan

### Core Events (track these minimum)

```
# Onboarding
onboarding_started
onboarding_step_completed (step_name, step_number)
onboarding_completed
onboarding_skipped

# Core Actions
[primary_action]_started
[primary_action]_completed
[primary_action]_failed (error_type)

# Monetization
paywall_viewed (source, variant)
trial_started (plan, source)
purchase_completed (plan, price, source)
purchase_failed (error_type)
subscription_renewed
subscription_cancelled (reason)

# Engagement
session_started (source)
feature_used (feature_name)
content_viewed (content_type, content_id)
share_tapped (content_type)
notification_received (type)
notification_tapped (type)

# Settings
settings_changed (setting_name, old_value, new_value)
notification_permission (granted: boolean)
```

### Event Naming Conventions

- Use `snake_case`
- Format: `[object]_[action]` (e.g., `photo_saved`, `workout_completed`)
- Be specific but not too granular
- Include relevant properties (but not PII)
- Consistent across platforms

## Dashboard Setup

### Executive Dashboard (check weekly)

```
┌─────────────────────────────────────────────┐
│  Weekly Summary                              │
├──────────────┬──────────────┬───────────────┤
│  Downloads   │  Revenue     │  DAU          │
│  [N] (+X%)   │  $[N] (+X%)  │  [N] (+X%)    │
├──────────────┼──────────────┼───────────────┤
│  Conversion  │  D1 Retention│  Rating       │
│  [X]% (+X%)  │  [X]% (+X%)  │  [X.X] ★      │
└──────────────┴──────────────┴───────────────┘
```

### Funnel Dashboard (check daily)

```
Impressions → Page Views → Downloads → Activation → Purchase
   [N]          [N]          [N]          [N]          [N]
        [X]%         [X]%         [X]%          [X]%
```

### Cohort Dashboard (check monthly)

Retention curves by:
- Install date cohort
- Acquisition source
- Country
- Subscription plan

## Output Format

### Analytics Audit

```
Current State:
- Tools in use: [list]
- Events tracked: [N]
- Key gaps: [list]

Recommendations:
1. [tracking gap to fix]
2. [metric to start monitoring]
3. [dashboard to create]
```

### Tracking Plan

Provide a complete event tracking plan with:
- Event name
- When it fires
- Properties to include
- Which tool tracks it

### Metric Interpretation

When the user shares data, provide:
- How their metrics compare to benchmarks
- What the trends indicate
- Specific actions to take based on the data

## Related Skills

- `ab-test-store-listing` — Measure test results
- `retention-optimization` — Interpret retention data
- `monetization-strategy` — Revenue metric optimization
- `ua-campaign` — Attribution and UA metrics

skills/ab-test-store-listing/SKILL.mdskill

Show content (7382 bytes)

---
name: ab-test-store-listing
description: When the user wants to A/B test App Store product page elements to improve conversion rate. Also use when the user mentions "A/B test", "product page optimization", "test my screenshots", "test my icon", "conversion rate optimization", "CPP", or "custom product pages". For screenshot design, see screenshot-optimization. For metadata optimization, see metadata-optimization.
metadata:
  version: 1.0.0
---

# A/B Test Store Listing

You are an expert in App Store product page optimization and A/B testing. Your goal is to help the user design, run, and interpret tests that improve their App Store conversion rate.

## Initial Assessment

1. Check for `app-marketing-context.md` — read it for context
2. Ask for the **App ID**
3. Ask for **current conversion rate** (if known from App Store Connect)
4. Ask for **daily impressions** (determines test duration)
5. Ask: **What do you want to test?** (icon, screenshots, description, etc.)

## What You Can Test

### Apple Product Page Optimization (PPO)

Apple's native A/B testing tool in App Store Connect.

| Element | Testable? | Notes |
|---------|-----------|-------|
| App icon | Yes | Up to 3 variants |
| Screenshots | Yes | Up to 3 variants |
| App preview video | Yes | Up to 3 variants |
| Description | No | Not testable via PPO |
| Title | No | Not testable via PPO |
| Subtitle | No | Not testable via PPO |

**Limitations:**
- Only tests against organic App Store traffic
- Minimum 90% confidence required to declare winner
- Tests run for 7-90 days
- Can only run one test at a time
- Traffic split is automatic (not configurable)

### Custom Product Pages (CPP)

35 custom product pages per app, each with unique:
- Screenshots
- App preview videos
- Promotional text

**Use for:**
- Different audiences (from different ad campaigns)
- Different value propositions
- Seasonal messaging
- Localized creative for specific markets

**Not a true A/B test** — CPPs are targeted pages linked from specific URLs/campaigns, not random traffic splits.

## Test Prioritization

### Impact × Effort Matrix

| Element | Impact on CVR | Effort | Priority |
|---------|--------------|--------|----------|
| First screenshot | Very High (15-30% lift possible) | Medium | 1 |
| App icon | High (10-20% lift possible) | Medium | 2 |
| Screenshot order | Medium (5-15% lift possible) | Low | 3 |
| Screenshot style | Medium (5-15% lift possible) | High | 4 |
| Preview video | Medium (5-10% lift possible) | High | 5 |

### What to Test First

**Always start with the first screenshot.** It has the highest impact because:
- It's the first thing users see in search results
- 80% of users never scroll past the first 3 screenshots
- Small improvements here affect every visitor

## Test Design Framework

### Step 1: Hypothesis

Write a clear hypothesis before each test:

```
If we [change], then [metric] will [improve/increase] because [reason].
```

**Examples:**
- "If we add social proof ('5M+ users') to the first screenshot, conversion rate will increase because it builds trust"
- "If we change the icon from blue to orange, tap-through rate will increase because it stands out more in search results"
- "If we show the app's AI feature first instead of the basic editor, conversion will increase because AI is the key differentiator"

### Step 2: Variants

Design 2-3 variants (including control):

| Variant | Description | Hypothesis |
|---------|-------------|------------|
| Control (A) | Current version | Baseline |
| Variant B | [specific change] | [why it might win] |
| Variant C | [different change] | [why it might win] |

**Rules for good variants:**
- Change ONE thing per test (isolate the variable)
- Make the change significant enough to detect (don't test subtle color shifts)
- Each variant should have a clear hypothesis
- Don't test more than 3 variants (dilutes traffic)

### Step 3: Sample Size

Calculate required test duration:

```
Daily impressions: [N]
Current conversion rate: [X]%
Minimum detectable effect: [Y]% (relative improvement)
Confidence level: 95%

Required sample per variant: ~[N] impressions
Estimated duration: [N] days
```

**Rules of thumb:**
- < 1000 daily impressions: Tests take 30-90 days (consider if worth it)
- 1000-5000 daily impressions: Tests take 14-30 days
- 5000+ daily impressions: Tests take 7-14 days
- Need at least 1000 impressions per variant for meaningful results

### Step 4: Run the Test

**In App Store Connect:**
1. Go to Product Page Optimization
2. Create a new test
3. Upload variant assets
4. Set test duration (recommend: let it run until statistical significance)
5. Monitor but don't stop early

### Step 5: Interpret Results

**Statistical significance:**
- Apple requires 90% confidence minimum
- Aim for 95% confidence before making decisions
- Look at the confidence interval, not just the point estimate

**What to look for:**
- Conversion rate lift (primary metric)
- Impression-to-tap rate (for icon tests)
- Download rate (for screenshot/video tests)
- Segment differences (new vs returning, country, source)

## Common Test Ideas

### Icon Tests

| Test | Control | Variant | Expected Impact |
|------|---------|---------|----------------|
| Color | Current color | Contrasting color | 5-20% TTR change |
| Style | Detailed | Simplified | 5-15% TTR change |
| Element | Current symbol | Different symbol | 5-20% TTR change |
| Background | Solid | Gradient | 3-10% TTR change |

### Screenshot Tests

| Test | Control | Variant | Expected Impact |
|------|---------|---------|----------------|
| First screenshot | Feature-focused | Benefit-focused | 10-30% CVR change |
| Social proof | No social proof | "5M+ users" badge | 5-15% CVR change |
| Text size | Small text | Large, bold text | 5-10% CVR change |
| Style | Light mode | Dark mode | 5-15% CVR change |
| Layout | Device frame | Full-bleed | 5-10% CVR change |
| Order | Current order | Reordered by benefit | 5-15% CVR change |

### Video Tests

| Test | Control | Variant | Expected Impact |
|------|---------|---------|----------------|
| Has video | No video | 15s feature demo | 5-15% CVR change |
| Hook | Feature demo | Problem/solution | 5-10% CVR change |
| Length | 30s | 15s | 3-8% CVR change |

## Output Format

### Test Plan

```
Test Name: [descriptive name]
Element: [icon / screenshots / video]
Hypothesis: If we [change], then [metric] will [improve] because [reason]

Variants:
- Control (A): [description]
- Variant B: [description]
- Variant C: [description] (optional)

Estimated Duration: [N] days
Required Impressions: [N] per variant
Success Metric: [conversion rate / tap-through rate]
Minimum Detectable Effect: [X]%
```

### Test Results Interpretation

When the user shares results:
1. Is it statistically significant? (confidence level)
2. What's the actual lift? (with confidence interval)
3. Are there segment differences?
4. What's the next test to run?
5. Estimated annual impact (downloads × lift)

### Testing Roadmap

Provide a 3-month testing calendar:
- Month 1: [highest impact test]
- Month 2: [second priority test]
- Month 3: [third priority test]

## Related Skills

- `screenshot-optimization` — Design screenshot variants
- `metadata-optimization` — Optimize non-testable elements
- `app-analytics` — Track conversion metrics
- `aso-audit` — Identify what to test first

skills/app-clips/SKILL.mdskill

Show content (5793 bytes)

---
name: app-clips
description: When the user wants to implement, optimize, or use App Clips for app discovery and conversion. Use when the user mentions "App Clip", "app clip code", "mini app", "instant app", "App Clip card", "App Clip link", "no download required", "instant experience", or wants to understand how App Clips appear in App Store search. For general App Store discoverability, see aso-audit. For marketing campaigns, see ua-campaign.
metadata:
  version: 1.0.0
---

# App Clips

You help plan, implement, and optimize App Clips — lightweight iOS experiences (max 15MB) that users can launch instantly without installing the full app.

## What App Clips Are

App Clips are small, focused pieces of your app that users can use without downloading the full app. They appear in:

- **App Store search results** — alongside your full app
- **Smart App Banners** on websites
- **QR codes** and App Clip codes (physical NFC/QR)
- **Safari** — when visiting a linked URL
- **Messages** — when a URL is shared in iMessages
- **Maps** — for location-based businesses
- **Nearby** — NFC and visual codes in the physical world
- **Siri suggestions**

## Size Limit

| Target | Limit |
|--------|-------|
| App Clip binary | **15MB** max (thinned, downloaded on demand) |
| App itself | No change |

This forces you to ship only the essential experience.

## Best Use Cases

| App Type | App Clip Experience |
|----------|-------------------|
| Parking/transit | Pay for parking or buy a ticket |
| Restaurant | View menu, order, or pay |
| Retail | Product preview or loyalty card |
| Fitness | Try a single workout |
| Games | Play a demo level |
| Finance | Calculator or quick quote |
| Events | Ticket purchase or check-in |
| Utilities | Use core feature once |

**The key question:** What is the minimum experience that demonstrates your app's core value?

## App Clip Discovery in the App Store

App Clips appear in **App Store search** as a separate card below your full app result — labeled "App Clip" with an "Open" button (not "Get").

- Users who tap "Open" launch the App Clip instantly
- After using it, they see a banner: "Get the full app"
- Conversion from App Clip user → full install is typically **3–5× higher** than cold organic traffic

**ASO implication:** The App Clip card inherits your app's title and description metadata. Optimizing your main listing improves App Clip discoverability too.

## Technical Requirements

### What to include in the App Clip

- Only the core experience
- Apple Pay or Sign in with Apple for authentication (no full account creation)
- No App Clip–only content — everything in the clip should also be in the full app
- Request only essential permissions (no push notifications in App Clips)

### URL scheme

Each App Clip is triggered by a URL:
```
https://yourdomain.com/clip/[experience]
```

Configure in App Store Connect → Your App → App Clip Experiences.

### Handoff to Full App

Always include a clear upgrade prompt:

```swift
// Show SKOverlay after the user gets value from the clip
let config = SKOverlay.AppClipConfiguration(position: .bottom)
let overlay = SKOverlay(configuration: config)
overlay.present(in: windowScene)
```

Show the overlay **after** the user has experienced value — not immediately.

## App Clip Experiences

You can configure multiple App Clip experiences (one per URL pattern):

| Experience | URL | Use Case |
|-----------|-----|---------|
| Default | `yourdomain.com` | General / App Store search |
| Location | `yourdomain.com/location/123` | Maps, NFC at specific location |
| Campaign | `yourdomain.com/promo/summer` | Marketing campaign |
| Feature | `yourdomain.com/feature/x` | Specific feature demo |

Each experience can have its own:
- Title (max 18 chars)
- Subtitle (max 13 chars)
- Header image (3000×2000px)
- Action button text

## App Clip Card Design

The card is shown before the App Clip launches:

| Field | Limit | Tips |
|-------|-------|------|
| Title | 18 chars | Clear action: "Order Coffee" not "App Name" |
| Subtitle | 13 chars | Reinforce the value: "Skip the line" |
| Header image | 3000×2000px | Show the outcome, not the UI |
| Action button | — | Use context-specific text: "Order", "Pay", "Play" |

## Measurement

Track in App Store Connect → App Analytics → App Clips:
- App Clip sessions
- App Clip cards displayed
- App Clip → full app conversions
- Unique App Clip users

## App Clip vs Full App Install Trade-offs

| | App Clip | Full Install |
|---|---------|-------------|
| User friction | Very low | Higher |
| Commitment | Low | High |
| Retention | Low (one-time use) | High |
| Conversion from Clip | — | 3–5× higher than cold traffic |
| Best for | Discovery + conversion | Retention + monetization |

## Implementation Checklist

```
Setup:
- [ ] App Clip target added to Xcode project
- [ ] App Clip < 15MB (use size report in Xcode)
- [ ] Associated Domains entitlement configured
- [ ] App Clip experience URLs registered in App Store Connect

UX:
- [ ] Core value delivered within 60 seconds
- [ ] Sign in with Apple or Apple Pay (no custom sign-up)
- [ ] SKOverlay shown post-value (not immediately)
- [ ] Clear data handoff when user installs full app

App Store Connect:
- [ ] Default App Clip experience configured
- [ ] Header image uploaded (3000×2000px)
- [ ] Title ≤ 18 chars, subtitle ≤ 13 chars
- [ ] Additional experiences for locations/campaigns (if applicable)
```

## Related Skills

- `aso-audit` — Clip discoverability depends on main app ASO
- `onboarding-optimization` — Apply same "value-first" principles to Clip experience
- `ua-campaign` — Drive traffic to App Clip URLs in paid campaigns
- `app-store-featured` — App Clips can support featuring eligibility

skills/app-icon-optimization/SKILL.mdskill

Show content (6006 bytes)

---
name: app-icon-optimization
description: When the user wants to design, test, or improve their app icon to increase tap-through rate and conversions in App Store search and browse. Use when the user mentions "app icon", "icon design", "icon A/B test", "icon variants", "tap-through rate", "icon conversion", "icon refresh", or wants to know what makes a good app icon. For screenshot optimization, see screenshot-optimization. For full listing A/B tests, see ab-test-store-listing.
metadata:
  version: 1.0.0
---

# App Icon Optimization

You help design, audit, and A/B test app icons to maximize tap-through rate (TTR) — the percentage of users who tap your app after seeing it in search results or browse.

## Why the Icon Is Your Most Impactful Asset

The icon is the **first thing users see** in search results — before the title, rating, or screenshots. A compelling icon can lift TTR by 20–40% with no other changes. In browse/charts, it's often the only visual element competing for attention.

## Icon Design Principles

### 1. Simplicity at Small Size

Icons render at 60×60pt (iPhone search results). At that size, detail disappears.

- Maximum 2 elements
- No text (illegible at small sizes; Apple discourages it)
- Strong silhouette recognizable at a glance
- Test at 60×60px before finalizing

### 2. Color Contrast Against the App Store Background

The App Store has a white/light background (light mode) and dark background (dark mode).

- High contrast on both modes
- Avoid white icons — they disappear in light mode
- Avoid very dark icons — they disappear in dark mode
- Consider adding a subtle shadow or border on your icon background

### 3. Category Visual Language

Match and differentiate from your category norms:

| Category | Common patterns | How to stand out |
|----------|----------------|-----------------|
| Productivity | Blue, clean, minimal | Warmer colors, bolder marks |
| Health/Fitness | Green, orange, energetic | Premium dark, sophisticated |
| Finance | Blue, green, conservative | Bold, distinctive mark |
| Games | Bright, characters, action | Premium/dark if competitors are loud |
| Social | Round shapes, soft colors | Sharp, distinctive if feed is soft |
| Meditation | Purple, blue, calm | Unexpected contrast color |
| Photo/Video | Gradient, camera | Single strong mark |

**Rule:** Look at your top 20 competitors' icons. Then design to be immediately distinguishable.

### 4. Recognizable Mark

The icon needs a single, memorable mark — not a scene or a composition. Ask:

> "Can someone describe this icon in 3 words?"

- ✅ "Red speech bubble" | ❌ "Someone using a phone with a gradient"
- ✅ "Bold orange flame" | ❌ "Abstract colorful shapes"

### 5. Brand Consistency

The icon is your brand mark in the App Store. It should:
- Match your app's primary color palette
- Be consistent with your splash screen, push notifications, and marketing
- Work as a favicon, social media avatar, and press kit asset

## Icon Sizes Required

| Platform | Size |
|----------|------|
| iPhone (App Store) | 1024×1024px (master) |
| iPhone (home screen) | 60×60pt @1x, @2x, @3x |
| iPad | 76×76pt @1x, @2x |
| Watch | 40×40pt – 44×44pt |
| Android adaptive icon | 108×108dp (safe zone 66×66dp) |

Submit a single 1024×1024px PNG (no transparency, no rounded corners — Apple applies the mask).

## A/B Testing Icons

### iOS — Product Page Optimization

1. App Store Connect → Your App → Product Page Optimization → Create Test
2. Create up to 3 icon variants
3. Set traffic allocation (20–33% per variant)
4. Run for minimum 7 days or until statistical significance

**Access:** App Store Connect → App Store → Product Page Optimization

### Android — Play Store Experiments

1. Play Console → Store listing experiments → New experiment
2. Upload up to 3 icon variants
3. Set traffic split
4. Google reports install conversion rate per variant

### What to Test

Test one variable at a time:

| Test | Variants |
|------|---------|
| Color scheme | Same mark, 3 different background colors |
| Mark style | Flat vs illustrated vs 3D |
| Dark vs light | Dark background vs light background |
| Character vs abstract | Character-based vs geometric/abstract |
| With vs without text | Mark only vs mark + short text |

### Reading Results

- **Primary metric:** Install conversion rate (impressions → installs)
- **Minimum sample:** 1,000+ impressions per variant for reliable signal
- **Significance threshold:** p < 0.05 or Appeeky/Play Console confidence indicator

## Icon Audit

Evaluate your current icon against:

```
Clarity at 60×60px:        [1–10]
  - Recognizable mark at small size?
  - No illegible text?

Color contrast:            [1–10]
  - Works on white (light mode)?
  - Works on dark backgrounds (dark mode)?

Category differentiation:  [1–10]
  - Stands out from top 10 competitor icons?

Simplicity:                [1–10]
  - Max 2 elements?
  - Describable in 3 words?

Brand alignment:           [1–10]
  - Consistent with app's visual identity?

Overall: [N]/50
```

## Brief for Icon Designer

When briefing a designer:

```
App: [name and one-line description]
Category: [category]
Primary audience: [who uses it]
Brand colors: [hex values]
Mood/feeling: [premium / playful / trustworthy / energetic / calm]

What the icon should convey: [core value or identity]
What to avoid: [don't replicate competitor X, avoid Y]

Competitors to differentiate from: [list 3–5 with icons]
Reference icons I like: [list 3–5 from other apps]

Deliverables:
- 3 distinct concepts at 1024×1024px
- Each concept tested at 60×60px mockup in App Store search context
- Final: PNG, no alpha, no rounded corners
```

## Related Skills

- `ab-test-store-listing` — Full A/B testing methodology
- `screenshot-optimization` — Complement the icon with strong screenshots
- `android-aso` — Android adaptive icon requirements
- `aso-audit` — Icon is one factor in the full ASO score

skills/app-launch/SKILL.mdskill

Show content (5784 bytes)

---
name: app-launch
description: When the user wants to plan a launch strategy for a new app or major update. Also use when the user mentions "app launch", "launch plan", "launch checklist", "pre-launch", "launch day", or "how to launch my app". For ongoing ASO after launch, see aso-audit. For paid acquisition during launch, see ua-campaign.
metadata:
  version: 1.0.0
---

# App Launch Strategy

You are an expert in mobile app launches with experience across indie apps and top-charting products. Your goal is to create a comprehensive launch plan that maximizes day-one visibility and sustains momentum.

## Initial Assessment

1. Check for `app-marketing-context.md` — read it for app context
2. Ask: **New app or major update?**
3. Ask: **Launch date** (or flexible?)
4. Ask: **Budget** (organic only, or paid acquisition available?)
5. Ask: **Pre-existing audience?** (email list, social following, existing app users)
6. Ask: **Target countries** (simultaneous or phased rollout?)

## Launch Timeline

### 8 Weeks Before Launch

**ASO Foundation:**
- [ ] Run `keyword-research` to identify target keywords
- [ ] Run `metadata-optimization` to craft title, subtitle, keyword field
- [ ] Run `competitor-analysis` to understand the landscape
- [ ] Design screenshots (run `screenshot-optimization`)
- [ ] Create app preview video (15-30 seconds)
- [ ] Write compelling description with strong first 3 lines
- [ ] Design a distinctive icon

**Pre-launch Page (if new app):**
- [ ] Set up App Store pre-order page
- [ ] Enable pre-order notifications
- [ ] Share pre-order link for early sign-ups

**Press & Community:**
- [ ] Build a press kit (screenshots, icon, description, founder story)
- [ ] Identify 20-30 relevant journalists, bloggers, YouTubers
- [ ] Draft personalized pitch emails
- [ ] Identify relevant communities (Reddit, Discord, forums, Twitter/X)

### 4 Weeks Before Launch

**Beta & Feedback:**
- [ ] TestFlight beta with 50-200 users
- [ ] Collect feedback and fix critical issues
- [ ] Ask beta testers to be ready to review on launch day
- [ ] Prepare FAQ and support documentation

**Content:**
- [ ] Write launch blog post
- [ ] Prepare social media content (10+ posts for launch week)
- [ ] Create demo video for social media
- [ ] Draft Product Hunt listing (if applicable)

**Technical:**
- [ ] Set up analytics (run `app-analytics`)
- [ ] Implement in-app rating prompt (show after positive experience)
- [ ] Set up crash reporting
- [ ] Test in-app purchases and subscriptions

### 1 Week Before Launch

**Final Prep:**
- [ ] Submit app for review (allow 2-3 days buffer)
- [ ] Schedule press embargo lift for launch day
- [ ] Prepare launch day social posts
- [ ] Brief beta testers on review timing
- [ ] Set up App Store Connect for phased release (or immediate)
- [ ] Prepare Apple Search Ads campaign (run `ua-campaign`)

### Launch Day

**Morning:**
- [ ] Release the app (or confirm phased release started)
- [ ] Send press emails with embargo lift
- [ ] Post on social media (personal + app accounts)
- [ ] Post on Product Hunt (if applicable)
- [ ] Post in relevant communities (Reddit, Discord, forums)
- [ ] Email your list

**Throughout the Day:**
- [ ] Monitor App Store Connect for download numbers
- [ ] Respond to every review (run `review-management`)
- [ ] Engage with social media mentions
- [ ] Monitor crash reports
- [ ] Share milestones ("We hit #X in [category]!")

**Evening:**
- [ ] Thank early adopters publicly
- [ ] Share day-one stats (if impressive)
- [ ] Plan tomorrow's content

### Week 1 After Launch

- [ ] Continue daily social posting
- [ ] Respond to all reviews
- [ ] Monitor keyword rankings (are you indexing?)
- [ ] Adjust Apple Search Ads bids based on performance
- [ ] Follow up with press who didn't respond
- [ ] Submit to App Store editorial for featuring (run `app-store-featured`)
- [ ] Analyze first-week metrics and adjust

### Month 1 After Launch

- [ ] Run full `aso-audit` with real data
- [ ] Adjust metadata based on actual keyword performance
- [ ] A/B test screenshots (run `ab-test-store-listing`)
- [ ] Plan first major update based on user feedback
- [ ] Evaluate paid acquisition ROI
- [ ] Set up ongoing keyword tracking

## Launch Amplification Tactics

### Free Channels
1. **Product Hunt** — Best for productivity, developer, and design tools
2. **Hacker News (Show HN)** — Best for technical or innovative apps
3. **Reddit** — Find 3-5 relevant subreddits, contribute before promoting
4. **Twitter/X** — Build-in-public thread, launch announcement
5. **LinkedIn** — If B2B or productivity app
6. **YouTube** — Demo video, "how I built this" story
7. **App review sites** — AppAdvice, MacStories, 9to5Mac, etc.

### Paid Channels
1. **Apple Search Ads** — Highest intent, start here
2. **Meta (Facebook/Instagram)** — Best for consumer apps
3. **TikTok** — Best for younger demographics
4. **Google Ads (UAC)** — Broad reach
5. **Influencer partnerships** — Micro-influencers (10K-100K) often best ROI

## Output Format

### Launch Plan Document

Provide a complete, dated checklist the user can follow. Include:
1. Timeline with specific dates (based on their launch date)
2. Prioritized task list for each phase
3. Channel strategy with specific tactics
4. Budget allocation (if paid channels available)
5. Success metrics and targets for week 1, month 1, month 3

## Related Skills

- `aso-audit` — Post-launch ASO health check
- `keyword-research` — Pre-launch keyword strategy
- `metadata-optimization` — Craft launch metadata
- `screenshot-optimization` — Design launch screenshots
- `ua-campaign` — Paid acquisition for launch
- `app-store-featured` — Editorial featuring strategy
- `review-management` — Handle launch-day reviews

.claude-plugin/marketplace.jsonmarketplace

Show content (1427 bytes)

{
  "name": "aso-skills",
  "owner": {
    "name": "Erencan",
    "url": "https://appeeky.com"
  },
  "metadata": {
    "description": "ASO & App Marketing skills for Claude Code — keyword research, metadata optimization, competitor analysis, and app growth",
    "version": "1.0.0",
    "repository": "https://github.com/eronred/aso-skills"
  },
  "plugins": [
    {
      "name": "aso-skills",
      "description": "17 ASO and app marketing skills for indie developers, app marketers, and growth teams. Covers keyword research, metadata optimization, competitor analysis, market intelligence, chart tracking, screenshot design, review management, localization, user acquisition, monetization, and more.",
      "source": "./",
      "strict": false,
      "skills": [
        "./skills/app-marketing-context",
        "./skills/aso-audit",
        "./skills/keyword-research",
        "./skills/metadata-optimization",
        "./skills/competitor-analysis",
        "./skills/app-launch",
        "./skills/screenshot-optimization",
        "./skills/review-management",
        "./skills/localization",
        "./skills/retention-optimization",
        "./skills/monetization-strategy",
        "./skills/ua-campaign",
        "./skills/app-store-featured",
        "./skills/app-analytics",
        "./skills/ab-test-store-listing",
        "./skills/market-movers",
        "./skills/market-pulse"
      ]
    }
  ]
}

README

ASO & App Marketing Skills

AI agent skills for App Store Optimization (ASO) and mobile app marketing. Built for indie developers, app marketers, and growth teams who want Cursor, Claude Code, or any Agent Skills-compatible AI assistant to help with keyword research, metadata optimization, competitor analysis, market intelligence, and app growth.

A web version is also available, powered by AI chats and our MCP: Appeeky Web.

Why This Exists

Most ASO knowledge lives in blog posts, courses, and expensive consultants. We packaged it into skills that any AI agent can use — so you get expert-level ASO guidance directly in your IDE.

Each skill contains battle-tested frameworks, scoring rubrics, and output templates. The agent reads the skill, pulls real data from the App Store (via Appeeky), and gives you actionable recommendations — not generic advice.

Quick Start

Cursor — Settings (Cmd+Shift+J) → Rules → Add Rule → Remote Rule (Github) → paste https://github.com/eronred/aso-skills

Claude Code — npx skills add eronred/aso-skills

Manual — git clone https://github.com/eronred/aso-skills.git && cp -r aso-skills/skills/* .cursor/skills/

Then ask your agent:

"Run an ASO audit for my app (id: 1617391485)"
"Find the best keywords for a meditation app"
"Optimize my App Store title and subtitle"
"How many downloads do I need to reach top 10 in Health & Fitness?"
"What apps are rising in the charts right now?"
"Give me a market briefing for the Games category"
"How are my downloads and revenue trending this month?"
"Help me plan a Christmas In-App Event"
"What seasonal keywords should I add in December?"
"Optimize my Google Play listing"
"My app rating dropped — how do I recover it?"
"Set up a weekly competitor monitoring routine for apps X, Y, Z"
"Help me pitch TechCrunch for my app launch"
"Build an Apple Search Ads campaign structure for my fitness app"
"My app has a crash affecting 2% of sessions — help me triage it"

Or invoke directly: /aso-audit, /keyword-research, /metadata-optimization, /market-movers, /market-pulse, /asc-metrics, /in-app-events, /seasonal-aso, /android-aso, /apple-search-ads, /competitor-tracking

Skills

ASO Core

Skill	What it does
`aso-audit`	Scores your listing across 10 factors (0-100), flags problems, gives a prioritized fix list
`keyword-research`	Finds keywords by volume × difficulty × relevance, groups them into primary/secondary/long-tail
`metadata-optimization`	Writes title, subtitle, keyword field, description — with 3 variants and character counts
`competitor-analysis`	Keyword gaps, creative teardown, positioning map, and specific opportunities to exploit
`seasonal-aso`	Seasonal keyword calendar, metadata swap strategy, timing checklist, and trending-moment tactics
`android-aso`	Google Play-specific ASO — indexed description strategy, short description, Play Experiments, rating recovery

Creative & International

Skill	What it does
`screenshot-optimization`	10-slot screenshot strategy with design briefs, text overlay copy, and competitor audit
`app-icon-optimization`	Icon design principles, A/B testing via PPO/Play Experiments, category differentiation, and icon briefs
`review-management`	Sentiment analysis, response templates (HEAR framework), rating improvement tactics
`localization`	Market prioritization matrix, per-country keyword research, cultural adaptation checklist

Growth

Skill	What it does
`app-launch`	8-week launch timeline with daily checklists, channel strategy, and press outreach templates
`ua-campaign`	Apple Search Ads, Meta, Google UAC — campaign structure, bidding, creative specs, budget allocation
`apple-search-ads`	Deep-dive ASA — campaign structure, match types, CPP routing, bid strategy, weekly optimization checklist
`app-store-featured`	Featuring readiness score, Apple tech checklist, pitch template, In-App Events calendar
`in-app-events`	Plan and write App Store In-App Events — copy, image brief, keyword strategy, submission timeline
`app-clips`	App Clip use cases, card design, URL scheme setup, SKOverlay handoff, and measurement
`press-and-pr`	Media targeting tiers, pitch templates, press kit checklist, embargo strategy, Product Hunt launch

Revenue & Retention

Skill	What it does
`monetization-strategy`	Pricing tiers, paywall timing/design, trial optimization, category benchmarks
`subscription-lifecycle`	Trial nurture sequences, voluntary/involuntary churn reduction, dunning, and win-back campaigns
`retention-optimization`	Activation → habit → engagement framework, push notification sequences, churn prevention
`onboarding-optimization`	First-run flow audit, activation event definition, permission prompt timing, sign-up friction reduction
`rating-prompt-strategy`	SKStoreReviewRequest / Play In-App Review timing, pre-prompt survey, version-gating, and rating recovery

Analytics & Testing

Skill	What it does
`app-analytics`	Event tracking plan, dashboard setup, KPI framework with category benchmarks
`ab-test-store-listing`	Hypothesis → variant design → sample size → interpretation for App Store A/B tests
`asc-metrics`	Analyze your exact App Store Connect data (downloads, revenue, subscriptions, countries) via Appeeky Connect
`crash-analytics`	Crashlytics setup, crash triage framework (P0–P3), symbolication, phased release strategy, rating recovery

Market Intelligence

Skill	What it does
`market-movers`	Identifies top chart gainers/losers, new entries, and dropped apps — explains what's driving changes
`market-pulse`	Full market briefing: chart movements + trending keywords + featured apps + new launches in one view
`competitor-tracking`	Weekly competitor surveillance — metadata changes, keyword shifts, rating trends, chart movement deltas

Foundation

Skill	What it does
`app-marketing-context`	Creates a context doc (app, audience, competitors, goals) that all other skills reference

How It Works

You: "Run an ASO audit for Headspace"

Agent:
  1. Reads aso-audit/SKILL.md (framework, scoring rubric, output template)
  2. Calls Appeeky API → fetches metadata, keywords, ratings, competitors
  3. Scores each factor (title: 8/10, subtitle: 6/10, keywords: 4/10...)
  4. Returns: ASO Score Card + Quick Wins + High-Impact Changes + Strategic Recs

Skills reference each other — aso-audit might suggest running keyword-research for deeper analysis, which then feeds into metadata-optimization for implementation.

Installation

Cursor

Method	Command
GitHub Import	Settings → Rules → Add Rule → Remote Rule → `https://github.com/eronred/aso-skills`
Project-level	`cp -r aso-skills/skills/* .cursor/skills/`
Global	`cp -r aso-skills/skills/* ~/.cursor/skills/`

Claude Code

Method	Command
CLI	`npx skills add eronred/aso-skills`
Specific skills	`npx skills add eronred/aso-skills --skill aso-audit keyword-research`
Manual	`cp -r aso-skills/skills/* .claude/skills/`

Any Agent

git submodule add https://github.com/eronred/aso-skills.git .agents/aso-skills

Works with any tool that supports the Agent Skills standard (.agents/skills/, .cursor/skills/, .claude/skills/, .codex/skills/).

Appeeky Integration

Skills work standalone with general ASO knowledge. Connect Appeeky for real-time App Store data:

{
  "mcpServers": {
    "appeeky": {
      "url": "https://mcp.appeeky.com/mcp",
      "headers": { "Authorization": "Bearer apk_your_key_here" }
    }
  }
}

With Appeeky connected, skills can pull live keyword rankings, competitor metadata, download estimates, trending keywords, and featured apps.

Appeeky Connect — First-Party ASC Data

The asc-metrics skill uses Appeeky Connect, a new integration that syncs your exact App Store Connect data (downloads, revenue, subscriptions, trials, IAP, and country breakdowns) into Appeeky nightly.

Connect once at appeeky.com → Settings → Integrations and then ask:

"How are my downloads trending this month?"
"What are my top 5 markets by revenue?"
"Compare this month's subscriptions to last month"

Requires Indie plan( coffee price: $8/month) or higher. See tools/integrations/appeeky-connect.md for the full API reference.

See tools/REGISTRY.md for the full capability matrix.

Contributing

PRs welcome — fix an inaccuracy, improve a framework, or add a new skill. See CONTRIBUTING.md.

License

MIT