in-app-events
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.
Skill by Necmttn
Install
Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.
npx agentmarket install skill/necmttn-in-app-events
Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.
Get the weekly diff
The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.
About
Use cases: security
Reviews
Write a reviewNo reviews yet. Installed it? Reviews come from verified installers only. How reviews work
Permissions: not checked yet.
What's inside
- Skill 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.
- License
- MIT
- Metadata
- version: 1.0.0
- Instructions
- 171 lines in SKILL.md · view on GitHub
Files (1)
- SKILL.md
SKILL.md (first lines)
# 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.
From Necmttn/skills, MIT.
Signals
- Stars
- 0
- Forks
- 0
- Open issues
- 25
- Last commit (this folder)
- Aug 25, 2026 (2 months ago)
From GitHub (fetched Oct 24, 2026).
Details
- Version
- 1.0.0
- License
- MIT
- Repository
- github.com/Necmttn/skills
- First seen
- Oct 24, 2026
- Last checked
- Oct 24, 2026
- Source
- GitHubgithub-graphql
Same skill elsewhere
Copies of this SKILL.md published by others; search shows only one of them.
More from Necmttn
- 0.785score
tune
Necmttn
Retrospective on one coding session that proposes changes to the agent's environment (hooks, checks, steering files, tool access) and files each as an ax…
SkillAFreshness: A★ 122Claude Code +9 - 0.779score
ax-repo
Necmttn
Star the ax repo, file an issue / bug report, or fork-and-open-a-PR against github.com/Necmttn/ax on the user's behalf, by shelling out to the `gh` CLI.
SkillAFreshness: A★ 122Claude Code +9 - 0.779score
efficient-dispatch
Necmttn
Model-routing orchestration for any expensive frontier model (Fable, Opus, GPT-5.x) - the main model keeps judgment and Q&A review, mechanical subagent…
SkillAFreshness: A★ 122Claude Code +9 - 0.779score
release-announcement
Necmttn
Draft or revise ax release announcements and website changelog pages.
SkillAFreshness: A★ 122Claude Code +9 - 0.779score
retro
Necmttn
Guided experiment-loop retrospective over the ax agent-experience graph.
SkillAFreshness: A★ 122Claude Code +9 - 0.779score
retro-meta
Necmttn
Deep retro of retros - investigation pass that surfaces improvements across older retros and the current ax setup.
SkillAFreshness: A★ 122Claude Code +9
Cite this page
in-app-events skill. Agent Mart. https://agentmart.dev/skills/necmttn-in-app-events (last updated 2026-10-24)