CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

76

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

87%

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

The body is dense, actionable, and well-organized with concrete specs and templates, excelling in conciseness, actionability, and structure; its only gap is the absence of explicit validation checkpoints in the submit workflow.

Suggestions

Add an explicit validation/checklist step to the Planning Workflow — e.g., after writing copy, verify the event name ≤30 chars, short ≤50 chars, long ≤120 chars, and image is 2160×1080px before submitting.

Include a submit-status feedback loop: after submitting in App Store Connect, check the review state and re-submit if rejected, so the workflow has an explicit fix→retry checkpoint.

Note that 'Submit 3–5 days before' and the Common Mistakes '4–5 days early' differ slightly (3–5 vs 4–5); reconcile to a single lead-time figure to avoid ambiguity.

DimensionReasoningScore

Conciseness

The body is lean and table-driven, jumping straight to specs, char limits, and ✅/❌ copy examples without explaining concepts Claude already knows; every token earns its place, matching the score-3 anchor.

3 / 3

Actionability

Provides fully concrete, copy-paste-ready guidance — exact char/pixel specs, ASC navigation steps, and a fill-in Event Brief template — matching the score-3 anchor for executable, specific instruction.

3 / 3

Workflow Clarity

The Planning Workflow is a clear 4-step sequence (Idea → Copy → Image → Submit), but it lacks explicit validation checkpoints or a fix→retry loop, matching the score-2 anchor of sequence present but checkpoints implicit; it is not 3 because no validation step is named.

2 / 3

Progressive Disclosure

No bundle files exist (references/scripts/assets are empty), and the single self-contained SKILL.md is well-organized with clearly signaled one-level-deep cross-skill pointers (app-marketing-context.md, keyword-research), so per the guidelines a simple well-organized skill scores 3.

3 / 3

Total

11

/

12

Passed

Description

100%

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

The description is strong across all dimensions: it specifies concrete actions, lists natural trigger terms users would say, explicitly covers both what and when, and clearly distinguishes itself from related skills with cross-references.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'create, plan, or optimize App Store In-App Events' — and specifies placements (Today tab, search results, product page), which matches the score-3 anchor of multiple specific concrete actions rather than the single-action score-2 anchor.

3 / 3

Completeness

Explicitly answers both 'what' (create/plan/optimize event cards) and 'when' via the 'Use when the user mentions...' clause, matching the score-3 anchor; it is not score 2 because 'when' is explicit rather than implied.

3 / 3

Trigger Term Quality

Provides broad natural-language coverage with quoted terms a user would actually say — 'in-app event', 'event card', 'Today tab', 'challenge', 'game event', 'seasonal event card' — matching the score-3 anchor for good coverage of natural terms.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche (App Store In-App Events) and adds explicit disambiguation ('For general ASO, see aso-audit. For seasonal keyword strategy, see seasonal-aso.'), making conflict with adjacent skills unlikely.

3 / 3

Total

12

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
Eronred/aso-skills
Reviewed

Table of Contents

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.