seasonal-aso

When the user wants to optimize their App Store listing for seasonal events, holidays, or trending moments — including keyword opportunities, metadata updates, screenshot theming, and timing strategy. Use when the user mentions "seasonal", "holiday", "Christmas", "New Year", "Valentine's Day", "summer", "back to school", "seasonal keywords", "trending now", "limited time", or wants to capitalize on a calendar event. For general keyword research, see keyword-research. For full metadata rewrites, see metadata-optimization.

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 highly actionable, well-structured skill body with concrete API calls, exact character budgets, and a copy-paste output template. It could tighten the time-sensitive calendar table (e.g., the "goals 2026" row) and add an explicit validate-then-swap checkpoint in the keyword research step.

Suggestions

Add an explicit validation gate in Step 2 (e.g., "Only proceed to metadata changes once a seasonal term shows a volume spike vs. its 30-day baseline and difficulty < 60") to give the workflow a feedback loop.

Move the year-specific "goals 2026" reference out of the static calendar or into a clearly marked current-year note so the table does not silently age.

Consider extracting the seasonal calendar into a references/ file so SKILL.md stays a lean overview with a one-level-deep pointer.

Dimension	Reasoning	Score
Conciseness	Lean and assumes Claude's competence (no preamble explaining ASO or the App Store); the seasonal calendar is dense reference data that earns its tokens, though the year-specific "goals 2026" and the bulky table are minor trim candidates.	4 / 5
Actionability	Fully executable guidance — concrete Appeeky API endpoints, exact character limits (100/30/170), a copy-paste-ready output brief template, and a day-offset timing checklist covering the common cases.	5 / 5
Workflow Clarity	A clear four-step sequence (Identify → Research → Plan → Timing) anchored by a T-14…T+5 checklist, with filter criteria acting as gates; minor validation gaps (no explicit "verify the volume spike before swapping a keyword" feedback loop).	4 / 5
Progressive Disclosure	Well-organized into clearly labeled sections with one-level-deep pointers to related skills; the inlined seasonal calendar is arguably reference material that could live in a separate file, but it is reasonable inline.	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, well-targeted description with explicit what/when structure, comprehensive natural trigger terms, and clear boundary guidance to sibling skills. The only minor weakness is that the listed capabilities are phrased at a slightly high level rather than as granular operations.

Dimension	Reasoning	Score
Specificity	Names the domain (seasonal ASO) and lists several concrete action areas — "keyword opportunities, metadata updates, screenshot theming, and timing strategy" — but each is stated at a high level rather than as fully specific operations, leaving minor gaps.	4 / 5
Completeness	Explicitly answers both what (optimize the listing for seasonal events across keyword/metadata/screenshot/timing) and when ("Use when the user mentions...") with concrete trigger phrases.	5 / 5
Trigger Term Quality	Comprehensive natural trigger terms users would actually say — "seasonal", "holiday", "Christmas", "New Year", "Valentine's Day", "summer", "back to school", "seasonal keywords", "trending now", "limited time" — plus the generic "capitalize on a calendar event".	5 / 5
Distinctiveness Conflict Risk	Clear niche (seasonal/calendar ASO) with distinct triggers and explicit boundary guidance routing general keyword research to keyword-research and full rewrites to metadata-optimization, minimizing conflict risk.	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/seasonal-aso/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.