in-app-events

eronred/aso-skills · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/eronred/aso-skills --skill in-app-events
0 commentsdiscussion
summary

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.

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

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
  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

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
how to use in-app-events

How to use in-app-events on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add in-app-events
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/eronred/aso-skills --skill in-app-events

The skills CLI fetches in-app-events from GitHub repository eronred/aso-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/in-app-events

Reload or restart Cursor to activate in-app-events. Access the skill through slash commands (e.g., /in-app-events) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.749 reviews
  • Neel Khan· Dec 24, 2024

    Keeps context tight: in-app-events is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Shikha Mishra· Dec 16, 2024

    in-app-events is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Nikhil Gill· Dec 16, 2024

    in-app-events has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Ganesh Mohane· Dec 12, 2024

    I recommend in-app-events for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Arya Anderson· Dec 12, 2024

    Useful defaults in in-app-events — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Naina Khan· Nov 15, 2024

    in-app-events is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Yash Thakker· Nov 7, 2024

    Keeps context tight: in-app-events is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Dev Singh· Nov 7, 2024

    in-app-events reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Chinedu Bhatia· Nov 7, 2024

    Solid pick for teams standardizing on skills: in-app-events is focused, and the summary matches what you get after install.

  • Daniel Taylor· Nov 3, 2024

    We added in-app-events from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

showing 1-10 of 49

1 / 5