AGENT SKILLBY ERONRED
Seasonal ASO
AT A GLANCE
Seasonal ASO is a go-to-market skill for AI agents. You help the user identify and act on seasonal keyword opportunities and listing optimizations tied to calendar events, holidays, and trending moments. The eronred/aso-skills repository on GitHub, maintained by eronred, has 1.6K stars and the MIT license. To add it, run npx skills add eronred/aso-skills --skill seasonal-aso
- SOURCE REPOSITORY
- eronred/aso-skills (opens GitHub in a new tab)
- REPO STARS
- SOURCE REPOSITORY
- LICENSE
- MIT
- CATEGORIES
- SKILL.MD SIZE
- 4.9 KB135 LINES
QUICK ANSWER
- WHAT IT IS01
- You help the user identify and act on seasonal keyword opportunities and listing optimizations tied to calendar events, holidays, and trending moments. It stands out by giving seasonal ASO a defined shape, so the agent asks for better context and returns a more usable result.
- INPUTS02
- Context the agent needs: your goals, audience, constraints, and any source material the skill asks for.
- OUTPUT03
- A ready-to-use result: the analysis, copy, or recommendations the agent produces.
INSTALL
One command adds this skill from its source repository.
npx skills add eronred/aso-skills --skill seasonal-asoREAD THE SKILL.MD BELOW BEFORE YOU RUN IT. SKILLS INSTRUCT YOUR AGENT.
SKILL.MD
The full file, as published in the source repository. Copy it, download it or open it on GitHub.
ON THIS PAGE · 12
Seasonal ASO#
You help the user identify and act on seasonal keyword opportunities and listing optimizations tied to calendar events, holidays, and trending moments.
Key Principle#
Seasonal rankings are competitive and time-sensitive. Metadata takes 1–3 days to index. Plan changes 2 weeks before the event; revert 3–5 days after peak.
Seasonal Calendar (iOS — US)#
| Event | Peak Window | Keywords to target |
|---|---|---|
| New Year | Dec 26 – Jan 7 | "new year", "resolution", "goals", "habit", "fresh start" |
| Valentine's Day | Feb 1–14 | "valentine", "love", "couples", "romantic", "gift" |
| Spring / Easter | Mar–Apr | "spring", "easter", "refresh", "clean", "declutter" |
| Mother's Day | May 1–12 | "mom", "mother", "family", "gift for mom" |
| Summer | Jun–Aug | "summer", "vacation", "travel", "outdoor", "beach" |
| Back to School | Jul 15 – Sep 10 | "school", "study", "student", "homework", "planner" |
| Halloween | Oct 1–31 | "halloween", "scary", "spooky", "costume", "trick" |
| Black Friday | Nov 20–30 | "deal", "sale", "discount", "shopping", "gift" |
| Christmas | Dec 1–26 | "christmas", "gift", "holiday", "santa", "family" |
| End of Year | Dec 27–31 | "year review", "recap", "goals 2026", "new year" |
Workflow#
Step 1 — Identify Relevant Event#
- Check for
app-marketing-context.md - Ask: Which event or season are you targeting?
- Ask: What does your app do? (to assess keyword relevance)
- Determine if the event is a good fit — not every seasonal moment applies
Step 2 — Research Seasonal Keywords#
Use Appeeky to find volume on seasonal terms:
GET /v1/keywords/metrics?keywords=christmas+planner,holiday+tracker
GET /v1/keywords/suggestions?term=christmas&country=us
GET /v1/keywords/trending?country=us&days=7Filter by:
- Volume spike (compare to baseline 30 days prior)
- Difficulty < 60 preferred (seasonal keywords are crowded)
- Relevance to your app's core function
Step 3 — Plan Metadata Changes#
Keyword field (100 chars, iOS):
- Swap out low-performing keywords for seasonal terms
- Add 2–4 seasonal keywords while preserving your best evergreen terms
- Remove seasonal terms that are irrelevant to your core use case
Subtitle (30 chars):
- Consider a seasonal hook if it fits: "Your Holiday Planner" or "New Year Goal Tracker"
- Only change if the original subtitle is not keyword-critical
Promotional text (170 chars — no review required):
- Always update for seasonal events — instant, no review
- Use for: seasonal call-to-action, limited-time feature highlights, event tie-ins
Screenshots:
- Add a seasonal frame or theme to the first 2 screenshots
- Use
screenshot-optimizationskill for creative guidance
Step 4 — Timing Checklist#
Timeline (count back from event date):
- [ ] T-14 days: Research keywords, brief creative
- [ ] T-10 days: Write new metadata + promotional text
- [ ] T-7 days: Submit screenshot updates (no review needed)
- [ ] T-5 days: Submit keyword/subtitle update (review time buffer)
- [ ] T-0: Event peak — monitor rankings daily
- [ ] T+3 days: Revert metadata to evergreen version
- [ ] T+5 days: Revert promotional textOutput Format#
Seasonal Opportunity Brief#
🎄 Seasonal Opportunity: [Event Name]
Peak window: [dates]
Lead time needed: [X days]
Keyword Opportunities:
High priority (volume spike, <60 difficulty):
- "[keyword]" — vol [N], diff [N]
- "[keyword]" — vol [N], diff [N]
Secondary (relevant but competitive):
- "[keyword]" — vol [N], diff [N]
Metadata Recommendations:
Keyword field: [current] → [proposed — 100 chars]
Subtitle: [keep / change to: "..."]
Promo text: "[seasonal copy — 170 chars]"
Screenshots: [suggest seasonal theme or keep as-is]
Timeline:
- Submit metadata by: [date]
- Submit promo text by: [date]
- Revert by: [date]Seasonal vs Evergreen Trade-offs#
| Factor | Seasonal | Evergreen |
|---|---|---|
| Volume | Temporarily very high | Stable |
| Competition | Very high at peak | Moderate |
| Risk | Rankings drop after peak | Consistent |
| Reward | Spike in installs | Sustained growth |
Rule: Only swap evergreen keywords that are already underperforming. Never sacrifice a high-ranking keyword for seasonal speculation.
Trending Moments (Non-Calendar)#
For viral/trending moments (news events, viral content, app store trends):
- Use
GET /v1/keywords/trending?country=us&days=3to spot emerging terms - Act within 24–48 hours (trending windows are short)
- Only update promotional text (instant, no review)
- Revert after the trend fades (typically 3–7 days)
Related Skills#
keyword-research— Deep keyword analysis for seasonal candidatesmetadata-optimization— Rewrite full metadata with seasonal termsscreenshot-optimization— Design seasonal screenshot themesmarket-pulse— Spot trending keywords and market movements in real time
FAQ
07 QUESTIONS
01What is the Seasonal ASO agent skill?
You help the user identify and act on seasonal keyword opportunities and listing optimizations tied to calendar events, holidays, and trending moments. It is listed under go-to-market in the 100xLab agent skills directory.
02How do I install Seasonal ASO in Cursor, Claude Code, or Codex?
Run npx skills add eronred/aso-skills --skill seasonal-aso in the project where you want it, then ask your agent for the skill by name. The --skill flag installs only Seasonal ASO, not every skill in the repository.
03What does the Seasonal ASO SKILL.md cover?
The SKILL.md includes sections on Key Principle, Seasonal Calendar (iOS — US), Workflow, Step 1 — Identify Relevant Event, Step 2 — Research Seasonal Keywords and Step 3 — Plan Metadata Changes. Read the full text on this page or in plain markdown at /resources/agent-skills/eronred-aso-skills--seasonal-aso--dmxe1r/raw.
04Which agents can use Seasonal ASO?
Seasonal ASO installs with the cross-agent skills installer (npx skills add), which sets it up for agents such as Claude Code, Cursor and Codex. Each agent loads the SKILL.md when you ask for the skill by name.
05What license is Seasonal ASO under?
The eronred/aso-skills repository declares the MIT license. Read the license file in the repository before you copy or redistribute the skill.
06Is Seasonal ASO free to use?
Reading, copying and installing Seasonal ASO costs nothing: it is published in a public GitHub repository under the MIT license. Reuse and redistribution follow that license.
07Where is the source of Seasonal ASO?
Seasonal ASO comes from https://github.com/eronred/aso-skills, which has 1.6K GitHub stars. The SKILL.md is at https://github.com/eronred/aso-skills/blob/HEAD/skills/seasonal-aso/SKILL.md. The author is eronred.
Need an agent workflow built around your stack?
Tell us the workflow you want automated. We reply within 4 working hours (IST).
ATTRIBUTION
Seasonal ASO was written by its original authors and is published in eronred/aso-skills (opens GitHub in a new tab) under the MIT license. All rights stay with the original authors.
100xLab did not write, maintain or endorse this skill. This page lists it for discovery. Repo stars belong to the source repository, not to the skill. Review any skill before you install it.