in-app-events
Plan an app Product's App Store In-App Events — one brief per event (name, descriptions, badge, dates, purpose) plus the month's calendar.
Written by Kwern, after the skill of the same name in Eronred's aso-skills, MIT. Updated 2026-09-24.
The file, as Kwern runs it
Nothing below is rewritten or cut. The description a model routes on comes first, then the file itself. The whole thing, frontmatter included, is at /skills/in-app-events.md.
description
Plan an app Product's App Store In-App Events — one brief per event (name, descriptions, badge, dates, purpose) plus the month's calendar. Use for "in-app event", "event card", "Today tab", "challenge", "launch event for the update". For holiday keyword and metadata timing use seasonal-aso; for editorial featuring use app-store-featured.
Plan the event cards that surface in search, on the Today tab, on the product page and as a notification to lapsed users. Output is a set of event briefs and an event calendar the User submits in App Store Connect.
Gather
read_context— positioning, ICP, roadmap moments (launches, seasons, milestones), target keywords, voice.app_store_listing— genres and the current version with its release notes, which decide the event types that fit and the update worth an event.connector_asc_in_app_eventswhen the ASC Connector exists — every event past, running and planned, with its badge, state, dates and territories (10 may be live or scheduled at once). Without it, assume none are scheduled and say so.connector_asc_analyticswhen the ASC Connector exists — impressions and downloads per source, the baseline an event's spike is measured against.connector_revenuecat_metricswhen the RevenueCat Connector exists — churned and lapsed subscriber counts, sizing the re-engagement upside.
Plan
Event types, field limits, copy rules, image direction and the mistakes to avoid are in references/event-specs.md; read it before writing a brief.
- Purpose per event — re-engagement (any badge; the notification to lapsed users is the main lever), acquisition (Challenge or Competition for Today tab reach), or feature launch (Major Update).
- Badge from category — the reference maps app category to the badges that perform.
- Copy — event name (30) leads with the benefit or action and carries 1–2 target keywords, written to work as a notification subject line; short description (50) answers "what's in it for me"; long description (120) says what, when and why.
- Timing — 7 to 31 days long, at least one event per month for recurring placement, submission 4–5 days before start for review.
- Calendar — the next month's slots with buffers, aligned with the moments
seasonal-asonames.
Output: event briefs + calendar
Per event: name with chars/30, badge, start → end, short description chars/50, long description chars/120, image direction (scene, style, key element; 2160×1080, legible at 390×195), purpose, KPI (sessions spike, downloads, event page views), submit-by date. Then the calendar by week, existing events from the Connector kept, moved or retired.
Done when every field is within its limit, every event has a submit-by date 4+ days before start, the month carries at least one event, and the Output names the data it lacked (scheduled events, baselines) when a Connector was absent.
Related Skills
seasonal-aso— the moments the calendar aligns with.screenshot-optimization— the same visual rules apply to the event image.app-store-featured— regular events raise editorial eligibility.churn-prevention— the lapsed users the notification reaches.
What it discloses
The Skill reads these files only when it needs them, so the model spends nothing on them the rest of the time.
references/event-specs.md
From your accounts to a proposal
- 01
Connect what it reads
Give the ASO agent the accounts it works on. Kwern never asks for a password, and an agent missing a connection says so instead of guessing.
- 02
The loop runs weekly
Before it writes a word it reads the foundation doc, which holds the positioning, the audience and the voice, and whatever its connectors return that day.
- 03
The in-app-events skill runs
The agent activates it when the run calls for it, and what the model then reads is the file on this page, word for word.
- 04
A proposal waits for you
Nothing is published and nothing is spent until you approve it. Approve and Kwern posts it where it holds the keys; where it does not, it hands you the text and the link.
The file, the agency, and the agent
| On your own | An agency | Kwern | |
|---|---|---|---|
| The method | Whatever you remember to do that week | Theirs, and you never get to read it | This file, open on this page |
| Who runs it | You, when there is time | An account manager, between other accounts | The ASO agent, weekly |
| What it reads | What you can pull by hand | What you remembered to send them | Your connected accounts and your foundation doc |
| What comes out | A draft, sometimes | A deck, and a report at the end of the month | A proposal you approve or throw away |
| What it costs | Your evenings | A retainer | One subscription, and the model on your own key |
Questions about in-app-events
Pair it with
The other skills the same agents reach for during a run.
Someone is asking for what you built today.
On Reddit, on X, in ChatGPT's answers. Kwern finds them every morning and drafts the reply in your voice; you decide what goes out.