CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

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.

A highly actionable, concise skill body with concrete API calls, character limits, and a dated timeline. Its only real gap is the absence of explicit validation/feedback checkpoints in the metadata-update workflow.

Suggestions

Add an explicit validation checkpoint to the workflow after metadata submission — e.g., 'Verify the update is live and indexed (1–3 days); if indexing fails, resubmit or revert' — to close the validate→fix→retry loop for the batch metadata operation.

Include a verification step in the timing checklist between T-5 (submit) and T-0 (peak) confirming keywords are indexed and rankings are moving before the event hits, so failures can be caught early.

Specify what to monitor during 'T-0: monitor rankings daily' (which keywords, against what baseline) so the monitoring step is actionable rather than implicit.

DimensionReasoningScore

Conciseness

Lean and token-efficient: it never explains concepts Claude already knows (no definition of ASO or the App Store), and every section — calendar table, char limits, output template — carries actionable reference value.

3 / 3

Actionability

Provides fully executable guidance: concrete API endpoints (GET /v1/keywords/metrics, /suggestions, /trending), exact character budgets (100/30/170), a dated T-14…T+5 checklist, and a copy-ready output brief template.

3 / 3

Workflow Clarity

The four-step sequence and timing checklist are clear, but the batch metadata-update workflow lacks explicit validation/verification checkpoints — there is only 'monitor rankings daily' and a revert, no validate-then-fix feedback loop, which caps the score per the batch-operations guideline.

2 / 3

Progressive Disclosure

No bundle files exist, so this is judged on organization: the body is split into well-signaled sections (Key Principle, Calendar, Workflow, Output Format, Trade-offs, Trending Moments, Related Skills) with one-level-deep references to app-marketing-context.md and sibling skills, giving easy navigation.

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.

A strong, specific description that clearly states capabilities, natural trigger terms, and when to use the skill, while distinguishing it from neighboring ASO skills. No meaningful weaknesses to address.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'keyword opportunities, metadata updates, screenshot theming, and timing strategy' — tied to a clear domain (seasonal App Store listing optimization), matching the top anchor.

3 / 3

Completeness

Explicitly answers both what (optimize listing for seasonal events with the four action categories) and when ('Use when the user mentions…'), with third-person voice throughout and no first/second-person phrasing to penalize.

3 / 3

Trigger Term Quality

Covers a broad set of natural terms users would actually say — 'seasonal', 'holiday', 'Christmas', 'New Year', 'Valentine's Day', 'summer', 'back to school', 'trending now', 'limited time' — plus the intent phrase 'capitalize on a calendar event'.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear seasonal-events niche and explicitly disambiguates from adjacent skills ('For general keyword research, see keyword-research. For full metadata rewrites, see metadata-optimization.'), making wrong-skill triggering 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.