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.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionin-app-eventsExecute the skills CLI command in your project's root directory to begin installation:
Fetches in-app-events from eronred/aso-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate in-app-events. Access via /in-app-events in your agent's command palette.
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 environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
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
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
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
696
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
696
stars
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.
In-App Events are time-limited content cards on the App Store. They appear:
Key advantage: Existing users who haven't opened your app recently are notified of events. Non-users see them as discovery.
| 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" |
| 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.
app-marketing-context.md| 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 |
Event name (30 chars) — rules:
Short description (50 chars):
Long description (120 chars):
Spec: 2160×1080px, 2:1 ratio
Best practices:
+Submit 3–5 days before the desired start date to account for review time.
Apple's algorithm favors events that are:
Run at least one event per month to maintain algorithmic eligibility.
Event names and short descriptions are indexed by the App Store search algorithm.
keyword-research skill to validate which terms to includeUsers 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.
📅 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]
Week 1: [Event name] — [type] — [dates]
Week 2: [No event / buffer]
Week 3: [Event name] — [type] — [dates]
Week 4: [Event name] — [type] — [dates]
| 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 |
seasonal-aso — Align event timing with keyword seasonal peaksscreenshot-optimization — Apply same visual best practices to event imagesapp-store-featured — Events increase editorial feature eligibilityretention-optimization — Track re-engagement lift from eventsMake data-driven prioritization decisions faster
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
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ 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.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
Keeps context tight: in-app-events is the kind of skill you can hand to a new teammate without a long onboarding doc.
in-app-events is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
in-app-events has been reliable in day-to-day use. Documentation quality is above average for community skills.
I recommend in-app-events for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Useful defaults in in-app-events — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
in-app-events is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Keeps context tight: in-app-events is the kind of skill you can hand to a new teammate without a long onboarding doc.
in-app-events reduced setup friction for our internal harness; good balance of opinion and flexibility.
Solid pick for teams standardizing on skills: in-app-events is focused, and the summary matches what you get after install.
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