agentleFS
EronredEronred/aso-skills/skills/in-app-events/SKILL.md

in-app-events

Skill2.2k starsChanged 9 months agoMITView on GitHub

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.

1 other project uses a version of this.

Trending

Quiet since March.thin dataabout the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 1 mentionApr 2026: 0 mentionsMay 2026: 0 mentionsJun 2026: 0 mentionsJul 2026: 0 mentionsAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 0 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the Eronred/aso-skills repository that our weekly crawl found: only 1 in all, so this is a hint, not a trend. There is no adoption data for this file yet.

Most recently taken up by

Who's talking about Eronred/aso-skills

The biggest 1 of 1 mention linking to the repository that our crawl found. Each line is their own headline.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    No text needed (name/description appear as overlay) — but a short tagline is allowed

    line 87
  2. Distinctive:

    Test thumbnail at 390×195px to verify legibility

    line 90
  3. Very specific:

    Use keyword-research skill to validate which terms to include

    line 119

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

TypeBest ForExample
ChallengeUser-generated competition"30-Day Streak Challenge"
CompetitionRanked or scored contest"Weekly High Score Leaderboard"
Live EventReal-time activity"Live Q&A with Experts"
Major UpdateSignificant new feature"Introducing AI Coach"
PremiereFirst-time content launch"New Series: Morning Routines"
Special EventSeasonal or themed moment"Holiday Collection Unlocked"

Event Card Specs

FieldLimitNotes
Event name30 charsAppears prominently — keyword-conscious
Short description50 charsBelow the name on cards
Long description120 charsShown in expanded event view
Event card image2160×1080px2:1 ratio, PNG/JPG, no text required
Badge—Chosen from the 6 type badges above
DurationUp to 31 daysStart 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 TypeBest Event Types
GamesChallenge, Competition, Major Update
FitnessChallenge, Live Event, Major Update
ProductivityMajor Update, Premiere
Social / CommunityLive Event, Challenge
Streaming / ContentPremiere, Special Event
UtilityMajor Update, Special Event
  1. 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

MistakeFix
App name in event nameLead with the user benefit
Generic image (screenshot of UI)Show the reward/outcome visually
Events shorter than 7 daysMinimum 7 days for Today tab consideration
Submitting day-ofSubmit 4–5 days early for review
No recurring scheduleRun 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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.