in-app-events — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited in-app-events (Agent Skill) and scored it 45/100 (orange). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 1 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 1 flagged
A base64 string of 128+ characters appears in a documentation file. Encoded prompt injection hides the hostile instruction in base64 — invisible to keyword filters — and relies on the agent's ability to decode it at runtime. There is no normal authoring reason to embed a multi-hundred-byte base64 blob in skill docs.
*.sig, SIGNATURES) outside the documentation.Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
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 events~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.