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

88%

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

82%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 well-structured, actionable body with concrete specs, copy rules, and output templates, and no padding of concepts Claude already knows. Weakest spot is workflow clarity, which lacks an explicit validation/feedback loop, and a slightly long single-file structure.

Suggestions

Add an explicit validation checkpoint to Step 4 (e.g., confirm the event cleared review and is scheduled before declaring done, with a retry path if rejected).

Tighten the 'Key advantage' and 'Re-engagement Notification' paragraphs to one-line value statements to push conciseness toward a 5.

Consider moving the full Event Types and Event Card Specs tables into a short referenced file if the skill grows, to keep SKILL.md a lean overview.

Dimension	Reasoning	Score
Conciseness	Lean and table-driven with no over-explanation of basic concepts; assumes Claude's competence. A few descriptive sentences ('Key advantage...', 'Re-engagement Notification' framing) could be tightened, keeping it at 4 rather than 5.	4 / 5
Actionability	Highly actionable: exact char limits, pixel specs, concrete copy rules with ✅/❌ examples, a UI submission path, and copy-paste output-format templates covering the common cases — matching the 5 anchor for an instruction-only skill.	5 / 5
Workflow Clarity	A clear 4-step planning workflow with sequenced steps and timing guidance ('Submit 3–5 days before'). No explicit validate→fix→retry feedback loop, but the task is not destructive or batch-oriented, so it stays at 4 rather than being capped.	4 / 5
Progressive Disclosure	Well-organized single self-contained file with clear section headers and cross-skill links (keyword-research, seasonal-aso) rather than nested bundle references; no bundle files exist to navigate. Sits at 4 because the file is fairly long and a couple of reference tables could conceivably live elsewhere, though inline placement is reasonable.	4 / 5
	Total	17 / 20 Passed

Description

95%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: third-person voice, concrete actions, explicit trigger phrases, and clear boundary guidance to adjacent skills. Minor room to broaden the action list beyond create/plan/optimize.

Dimension	Reasoning	Score
Specificity	Names the domain and three concrete actions ('create, plan, or optimize App Store In-App Events') plus where they surface, but the action list is not exhaustive — it omits measurement/iteration — so it sits at 4 rather than 5.	4 / 5
Completeness	Explicitly answers both 'what' (create/plan/optimize the event cards that appear on the Today tab, search results, product page) and 'when' (a 'Use when the user mentions...' clause with concrete trigger phrases), matching the 5 anchor.	5 / 5
Trigger Term Quality	Comprehensive natural trigger coverage including synonyms and variants ('in-app event', 'App Store event', 'event card', 'Today tab', 'live event', 'challenge', 'game event', 'seasonal event card', 'visibility beyond organic search'), matching the 5 anchor.	5 / 5
Distinctiveness Conflict Risk	Clear niche (App Store In-App Events) with distinct triggers plus explicit boundary routing ('For general ASO, see aso-audit. For seasonal keyword strategy, see seasonal-aso.'), giving minimal conflict risk per the 5 anchor.	5 / 5
	Total	19 / 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: 4df730f

Reviewed: 6 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.