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.
- Installs
- 2.4K
- Last 24h
- +15
- Trending rank
- #7090
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/appeeky/aso-skills --skill seasonal-aso- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads seasonal-aso automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
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=7
Filter 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 text
Output 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
What does the seasonal-aso skill do?
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.
How do I install seasonal-aso?
Run npx skills add https://github.com/appeeky/aso-skills --skill seasonal-aso in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/seasonal-aso/ (personal) or .claude/skills/seasonal-aso/ (project).
Which AI agents can use seasonal-aso?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is seasonal-aso safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains seasonal-aso?
It is published by appeeky in appeeky/aso-skills. It has 2,409 recorded installs.
More from appeeky/aso-skills
aso-audit
appeeky/aso-skills
When the user wants a full ASO health audit, review their App Store listing quality, or diagnose why their app isn't ranking. Also use when the user mentions "ASO audit", "ASO score", "why am I not ranking", "listing review", or "optimize my app store page". For keyword-specific research, see keyword-research. For metadata writing, see metadata-optimization.
keyword-research
appeeky/aso-skills
When the user wants to discover, evaluate, or prioritize App Store keywords. Also use when the user mentions "keyword research", "find keywords", "search volume", "keyword difficulty", "keyword ideas", or "what keywords should I target". For implementing keywords into metadata, see metadata-optimization. For auditing current keyword performance, see aso-audit.
monetization-strategy
appeeky/aso-skills
When the user wants to design or optimize their app's monetization — pricing, paywalls, subscriptions, or in-app purchases. Also use when the user mentions "pricing", "paywall", "subscription", "IAP", "how to monetize", "revenue optimization", "free trial", or "conversion to paid". For retention impact, see retention-optimization. For competitive pricing, see competitor-analysis.
metadata-optimization
appeeky/aso-skills
When the user wants to optimize App Store metadata — title, subtitle, keyword field, or description. Also use when the user mentions "optimize my title", "ASO metadata", "keyword field", "character limits", "app description", or "write my subtitle". For keyword discovery, see keyword-research. For full ASO audits, see aso-audit.
competitor-analysis
appeeky/aso-skills
When the user wants to analyze competitors' App Store strategy, find keyword gaps, or understand competitive positioning. Also use when the user mentions "competitor analysis", "competitive research", "keyword gap", "what are my competitors doing", or "compare my app to". For keyword-specific research, see keyword-research. For metadata writing, see metadata-optimization.
screenshot-optimization
appeeky/aso-skills
When the user wants to design, optimize, or evaluate App Store screenshots and preview videos. Also use when the user mentions "screenshots", "app preview", "product page design", "screenshot design", "creative assets", or "what should my screenshots show". For A/B testing screenshots, see ab-test-store-listing. For full ASO audit, see aso-audit.
Popular productivity & automation skills
agent-browser
vercel-labs/agent-browser
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.
lark-doc
open.feishu.cn
飞书云文档（Docx / Wiki）内容操作：读取、创建、编辑文档，插入或下载图片附件，以及操作思维笔记。用户提供文档 URL/token（包括 doubao.com 的 /docx/、/wiki/）时使用；按 URL 路径/token 而非域名路由；/page/ 是妙搭应用，非飞书云文档。文档内嵌资源按读取参考中的统一规则分流。独立评论操作走 lark-drive；随正文读取评论使用 docs +fetch。表格或 Base 内部数据操作不在本 skill。
lark-base
open.feishu.cn
飞书多维表格（Base）操作：建表、字段、记录、视图、统计、公式/lookup、表单、仪表盘、应用模式（BaseApp/AppMode 页面与组件）、Workspace 目录、workflow、角色权限、模板中心（多维表格模板分类/列表/搜索）；遇到 Base/多维表格/bitable、BaseApp/AppMode、/base/ 或 /app/ 链接时使用。BaseApp 不走 lark-apps；文件导入/导出转 lark-drive，认证/授权转 lark-shared。
lark-drive
open.feishu.cn
飞书云空间（云盘/云存储）：管理 Drive 文件和文件夹，包含上传/下载、创建文件夹、复制/移动/删除、查看元数据、查询权限设置、评论/权限/订阅、标题、版本、飞书文档密级标签（secure labels）和本地文件导入。用户需要整理云盘目录、处理云空间资源 URL/token、判断链接类型/真实 token/标题，或导入 Word/Markdown/Excel/CSV/PPTX/.base 为 docx/sheet/bitable/slides 时使用；doubao.com 云空间 URL/token 也按资源路径和 token 路由，不回退 WebFetch。不负责：文档内容编辑（走 lark-doc）、表格/Base 表内数据操作（走 lark-sheets/lark-base）、知识空间节点/成员管理（走 lark-wiki）、原生 Markdown 文件读写/patch/diff（走 lark-markdown）。
lark-shared
open.feishu.cn
Use for lark-cli setup/auth tasks: auth login/status/logout, user vs bot identity, business-domain permissions (--domain, including all/docs/drive), missing scopes, revoking authorization, or handling notice JSON.
lark-im
open.feishu.cn
飞书即时通讯：收发消息和管理群聊。发送和回复消息、搜索聊天记录、管理群聊成员、上传下载图片和文件、管理表情回复、发送应用内/短信/电话加急、发送和处理交互卡片（Interactive Card）、监听卡片按钮回调（card.action.trigger）。当用户需要发消息、查看或搜索聊天记录、下载聊天中的文件、查看群成员、搜索群、创建群聊或话题群、管理标记数据、管理 Feed 置顶（添加/移除/查询置顶会话）、管理标签数据、处理卡片回调时使用。