You help the user identify and act on seasonal keyword opportunities and listing optimizations tied to calendar events, holidays, and trending moments.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionseasonal-asoExecute the skills CLI command in your project's root directory to begin installation:
Fetches seasonal-aso from eronred/aso-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate seasonal-aso. Access via /seasonal-aso in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
696
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
696
stars
You help the user identify and act on seasonal keyword opportunities and listing optimizations tied to calendar events, holidays, and trending moments.
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.
| 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" |
app-marketing-context.mdUse 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:
Keyword field (100 chars, iOS):
Subtitle (30 chars):
Promotional text (170 chars — no review required):
Screenshots:
screenshot-optimization skill for creative guidanceTimeline (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
🎄 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]
| 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):
GET /v1/keywords/trending?country=us&days=3 to spot emerging termskeyword-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 timeMake data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
seasonal-aso is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
We added seasonal-aso from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Solid pick for teams standardizing on skills: seasonal-aso is focused, and the summary matches what you get after install.
Keeps context tight: seasonal-aso is the kind of skill you can hand to a new teammate without a long onboarding doc.
Useful defaults in seasonal-aso — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
seasonal-aso has been reliable in day-to-day use. Documentation quality is above average for community skills.
Registry listing for seasonal-aso matched our evaluation — installs cleanly and behaves as described in the markdown.
seasonal-aso fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
We added seasonal-aso from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Registry listing for seasonal-aso matched our evaluation — installs cleanly and behaves as described in the markdown.
showing 1-10 of 50