Agent skill

Seasonal Aso

Install Seasonal Aso

skills CLI

$ npx skills add appeeky/aso-skills --skill seasonal-aso -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install appeeky/aso-skills seasonal-aso --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/appeeky/aso-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/seasonal-aso .claude/skills/seasonal-aso && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "seasonal-aso" agent skill from https://github.com/appeeky/aso-skills/tree/main/skills/seasonal-aso into .claude/skills/seasonal-aso/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "seasonal-aso", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/appeeky/aso-skills/tree/main/skills/seasonal-aso

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add appeeky/aso-skills --skill seasonal-aso -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install appeeky/aso-skills seasonal-aso --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/appeeky/aso-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/seasonal-aso .agents/skills/seasonal-aso && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "seasonal-aso" agent skill from https://github.com/appeeky/aso-skills/tree/main/skills/seasonal-aso into .agents/skills/seasonal-aso/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "seasonal-aso", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add appeeky/aso-skills --skill seasonal-aso -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install appeeky/aso-skills seasonal-aso --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/appeeky/aso-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/seasonal-aso .cursor/skills/seasonal-aso && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "seasonal-aso" agent skill from https://github.com/appeeky/aso-skills/tree/main/skills/seasonal-aso into .cursor/skills/seasonal-aso/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "seasonal-aso", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/appeeky/aso-skills.git --path skills/seasonal-aso

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add appeeky/aso-skills --skill seasonal-aso -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install appeeky/aso-skills seasonal-aso --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/appeeky/aso-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/seasonal-aso .gemini/skills/seasonal-aso && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "seasonal-aso" agent skill from https://github.com/appeeky/aso-skills/tree/main/skills/seasonal-aso into .gemini/skills/seasonal-aso/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "seasonal-aso", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install appeeky/aso-skills seasonal-aso

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add appeeky/aso-skills --skill seasonal-aso -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/appeeky/aso-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/seasonal-aso .github/skills/seasonal-aso && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "seasonal-aso" agent skill from https://github.com/appeeky/aso-skills/tree/main/skills/seasonal-aso into .github/skills/seasonal-aso/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "seasonal-aso", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add appeeky/aso-skills --skill seasonal-aso -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install appeeky/aso-skills seasonal-aso --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/appeeky/aso-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/seasonal-aso .opencode/skills/seasonal-aso && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "seasonal-aso" agent skill from https://github.com/appeeky/aso-skills/tree/main/skills/seasonal-aso into .opencode/skills/seasonal-aso/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "seasonal-aso", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: seasonal-aso
GitHub stars: 2.2k
Token cost: ~1.4k tokens
SKILL.md length: 477 words
Files: 1
Skills in repo: 39
Repo updated: Oct 6, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Works in 4 steps: Identify Relevant Event → Research Seasonal Keywords → Plan Metadata Changes → …
Wants to optimize their App Store listing for seasonal events
SKILL.md covers Key Principle, Seasonal Calendar (iOS — US), Workflow and Output Format, plus 3 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Seasonal Aso is an agent skill from appeeky/aso-skills. 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…

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Marketing & SEO, covering App store release, Keyword research and Theming and dark mode. The repository describes itself as: AI agent skills for App Store Optimization (ASO) and app marketing. Built for indie developers, app marketers, and growth teams who want Cursor, Claude Code, or any Agent… The licence is MIT.

When your agent uses it

Wants to optimize their App Store listing for seasonal events
Trending moments — including keyword opportunities
Metadata updates
Screenshot theming

Example prompts

“seasonal”
“holiday”
“Christmas”
“/seasonal-aso”

Workflow steps

4 steps, taken from the step headings in SKILL.md.

Identify Relevant Event
Research Seasonal Keywords
Plan Metadata Changes
Timing Checklist

What it can do on your machine

Read from SKILL.md and the folder at commit 3919d7c. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Seasonal Aso loads about 1.4k tokens when it runs. Until then it costs about 135 tokens; SKILL.md has 477 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~135
When it runs · the whole SKILL.md, loaded when a task matches: ~1.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from appeeky/aso-skills at commit 3919d7c, republished under its MIT licence (© appeeky). 477 words, ~1,397 tokens.

Download SKILL.mdSave it as .claude/skills/seasonal-aso/SKILL.md (or your agent's skills folder).

name: seasonal-aso
description: 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.
metadata.version: 1.0.0

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:

bash

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

Show full SKILL.md (241 more words)Show less

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-optimization skill 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.

For viral/trending moments (news events, viral content, app store trends):

Use GET /v1/keywords/trending?country=us&days=3 to 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)

keyword-research — Deep keyword analysis for seasonal candidates
metadata-optimization — Rewrite full metadata with seasonal terms
screenshot-optimization — Design seasonal screenshot themes
market-pulse — Spot trending keywords and market movements in real time

Files

Just SKILL.md in skills/seasonal-aso of appeeky/aso-skills.

Open the folder on GitHubat commit 3919d7c

Compare with similar skills

Seasonal Aso next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Seasonal Aso compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Seasonal Aso this skillappeeky/aso-skills	2.2k	—	~1.4k	Automated safety check: Pass	MIT	4 days ago
Launch Asset Packageraaron-he-zhu/aaron-marketing-skills	2.9k	—	~3.2k	Automated safety check: Pass	Apache-2.0	today
Krankie Auditn0an/VivaDicta	130	—	~1.3k	Automated safety check: Pass	MIT	yesterday
Asc Aso AuditCamilleScholtz/swmpc	239	5 repos	~2.6k	Automated safety check: Pass	EUPL-1.2	4 days ago
SEO Keyword ClusteringAgriciDaniel/claude-seo	19k	2 repos	~3.3k	Automated safety check: Pass	MIT	6 days ago
Evaluate Skillevery-app/open-seo	23k	—	~1.8k	Automated safety check: Notes	MIT	2 days ago

Similar skills

Launch Asset Packager
aaron-he-zhu/aaron-marketing-skills
A skill your agent uses when the user asks to "package the launch assets", "build a press kit", or "prep the store listing and go-live checklist"; produces a tier-scoped launch asset manifest with…
2.9k GitHub stars~3.2k tokensUpdated today
Marketing & SEOAuto-check passed
Krankie Audit
n0an/VivaDicta
Run an ASO audit on canonical App Store metadata under ./metadata, then a krankie-based competitor keyword-gap analysis (no Astro subscription).
130 GitHub stars~1.3k tokensUpdated yesterday
MobileAuto-check passed
Asc Aso Audit
CamilleScholtz/swmpc
Run an offline ASO audit on canonical App Store metadata under ./Store and surface keyword gaps using Astro MCP.
239 GitHub starsUsed in 5 repos~2.6k tokens
MobileAuto-check passed
SEO Keyword Clustering
AgriciDaniel/claude-seo
Clusters keywords by how much their search results overlap and designs a hub-and-spoke content plan with an internal link matrix and an interactive cluster map.
19k GitHub starsUsed in 2 repos~3.3k tokens
Marketing & SEOAuto-check passed
Evaluate Skill
every-app/open-seo
Test a candidate OpenSEO skill end to end by running fresh, isolated Codex sessions against the local backend and scoring the reports they save.
23k GitHub stars~1.8k tokensUpdated 2 days ago
Marketing & SEOAuto-check: notes
SEO Content Brief Generator
AgriciDaniel/claude-seo
Builds research-backed SEO content briefs with competitor scoring, per-section word counts and page-type templates, for new pages or improving existing ones.
19k GitHub starsUsed in 2 repos~2.6k tokens
Marketing & SEOAuto-check passed

Questions about Seasonal Aso

What does Seasonal Aso 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. Seasonal Aso is an agent skill from appeeky/aso-skills. 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.

When should I use Seasonal Aso?

Seasonal Aso fits situations like: wants to optimize their App Store listing for seasonal events; trending moments — including keyword opportunities; metadata updates; screenshot theming.

How do I install Seasonal Aso in Claude Code?

Run `npx skills add appeeky/aso-skills --skill seasonal-aso -a claude-code`. Or copy the skill folder (skills/seasonal-aso in appeeky/aso-skills) into .claude/skills/seasonal-aso in your project. Claude Code loads it when a task matches its description.

How do I install Seasonal Aso in Codex?

Run `npx skills add appeeky/aso-skills --skill seasonal-aso -a codex`. Or copy the skill folder (skills/seasonal-aso in appeeky/aso-skills) into .agents/skills/seasonal-aso in your project. Codex loads it when a task matches its description.

Can I use Seasonal Aso in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add appeeky/aso-skills --skill seasonal-aso -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/seasonal-aso, .gemini/skills/seasonal-aso, .github/skills/seasonal-aso and .opencode/skills/seasonal-aso in your project.

What does Seasonal Aso need to run?

SKILL.md names no scripts, command-line tools or credentials: Seasonal Aso is instructions for the agent only.

Does Seasonal Aso access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Seasonal Aso safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Seasonal Aso use?

Seasonal Aso is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Seasonal Aso use?

About 1.4k tokens (SKILL.md is roughly 5.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Seasonal Aso?

Skills that share tags, products or a category with Seasonal Aso: Launch Asset Packager (aaron-he-zhu/aaron-marketing-skills, 2.9k stars), Krankie Audit (n0an/VivaDicta, 130 stars), Asc Aso Audit (CamilleScholtz/swmpc, 239 stars) and SEO Keyword Clustering (AgriciDaniel/claude-seo, 19k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Seasonal Aso?

appeeky (a GitHub organization) maintains it in appeeky/aso-skills, which has 2,163 GitHub stars. The repository holds 39 skills in this directory. The repository was last updated on October 6, 2026.

Source: appeeky/aso-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Seasonal Aso

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Seasonal ASO

Key Principle

Seasonal Calendar (iOS — US)

Workflow

Step 1 — Identify Relevant Event

Step 2 — Research Seasonal Keywords

Step 3 — Plan Metadata Changes

Step 4 — Timing Checklist

Output Format

Seasonal Opportunity Brief

Seasonal vs Evergreen Trade-offs

Trending Moments (Non-Calendar)

Related Skills

Files

Compare with similar skills

Similar skills

More from appeeky/aso-skills

Related

Questions about Seasonal Aso