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

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

75%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A dense, well-structured operational guide that earns its tokens: almost everything is App Store-specific data (limits, specs, timing, placement algorithm factors) plus ready-to-use output templates. The main deductions are minor internal duplication, an inconsistent submission lead time stated three different ways, and a single-file layout where a couple of reference tables could be split out for a leaner overview.

Suggestions

Reconcile the submission lead time into one figure — the body says '3-5 days before' (Step 4), '4-5 days early' (Common Mistakes), and '4 days before start' (Output Format).

De-duplicate the image spec (specs table vs. Step 3) and the monthly cadence advice (Optimization Tips vs. Common Mistakes); state each once and cross-reference.

Add an explicit validation checkpoint in Step 4: before submitting, verify the name/short/long copy lengths against the 30/50/120 char limits and confirm start/end dates leave review headroom.

Dimension	Reasoning	Score
Conciseness	Nearly every line carries App Store-specific facts Claude cannot be assumed to know (30-char name / 50-char short / 120-char long limits, 2160x1080 image, 31-day max, 10 concurrent events, 24-48h review time). Not a 5 because of duplicated content: the image spec appears in both the specs table and Step 3, and the 'one event per month' guidance appears in Optimization Tips and again in Common Mistakes.	4 / 5
Actionability	Concrete and executable throughout: exact field limits, ✅/❌ copy examples, an App Store Connect click-path, a thumbnail test at 390x195px, and a copy-paste-ready event brief and calendar template. Not a 5 because the submission lead time is stated three inconsistent ways ("3-5 days", "4-5 days early", template's "4 days before start") and there is no fully worked example of a completed event brief.	4 / 5
Workflow Clarity	The four-step planning workflow (idea selection by app category and goal, copy, image, submit) is clearly sequenced, with the thumbnail legibility test acting as a checkpoint. Not a 5 because there is no explicit pre-submit validation step (e.g., verify char counts against the limits before filling in App Store Connect); not a 3 because the sequence is coherent and checkpoints are mostly present — and the skill is neither destructive nor batch, so no hard cap applies.	4 / 5
Progressive Disclosure	The skill is a single self-contained file with no references/, scripts/, or assets/ bundle; sections are well-organized with headers, tables, and a Related Skills routing section, and there are no nested or dead references. Not a 5 because at ~165 lines some reference material (the event-type matrix and app-category mapping, or the keyword/notification optimization detail) could be split into one-level-deep reference files to keep SKILL.md a leaner overview.	4 / 5
	Total	16 / 20 Passed

Description

91%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: it explicitly states what the skill does and when to use it, with a rich set of natural trigger terms and explicit boundary routing to sibling ASO skills. The only weaknesses are slightly under-sold capability coverage (copy/image/submission work is in the body but not the description) and a couple of overly broad trigger words ("challenge", "game event").

Suggestions

Broaden the 'what' clause to mention the concrete deliverables the skill produces (event copy, card image direction, App Store Connect submission timing), not just 'create, plan, or optimize'.

Qualify the generic triggers 'challenge' and 'game event' (e.g., 'App Store challenge event') so they don't fire for in-app feature development or generic game-event requests.

Consider noting that event names/short descriptions are search-indexed, which is a distinctive capability separating this skill from general marketing skills.

Dimension	Reasoning	Score
Specificity	The description lists three concrete actions ("create, plan, or optimize App Store In-App Events") and grounds the domain with where the cards appear ("Today tab, search results, and your product page"). Not a 5 because it omits concrete actions the skill actually covers (writing event copy, image direction, App Store Connect submission); not a 3 because it names several specific actions rather than 1-2.	4 / 5
Completeness	Both what ("create, plan, or optimize App Store In-App Events — the event cards that appear on the Today tab, search results, and your product page") and when ("Use when the user mentions 'in-app event', ...") are explicitly and concretely answered, matching the anchor-5 example pattern exactly. Not below 5 since neither half is implicit or weak.	5 / 5
Trigger Term Quality	Comprehensive natural-term coverage with many synonyms: "in-app event", "App Store event", "event card", "Today tab", "live event", "challenge", "game event", "seasonal event card", plus the intent phrase "wants visibility beyond organic search". These are exactly the phrases a user planning App Store promotion would say; no file extensions exist for this domain, so nothing meaningful is missing.	5 / 5
Distinctiveness Conflict Risk	The App Store scoping plus explicit boundary routing ("For general ASO, see aso-audit. For seasonal keyword strategy, see seasonal-aso") makes it mostly distinct. Not a 5 because the generic triggers "challenge" and "game event" could fire for non-App Store requests (e.g., building an in-app challenge feature or a generic game event system); not a 3 since the domain framing and sibling-skill disambiguation keep overlap minor.	4 / 5
	Total	18 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: Eronred/aso-skills
Path: skills/in-app-events/SKILL.md
Commit: 8de1ee1

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.