Analyze release trends across multiple companies to produce competitive intelligence. Use when asked to compare companies, analyze a market segment, identify industry trends, forecast upcoming releases, or answer questions like "what is X shipping lately" or "how does X compare to Y." Also triggers on requests for competitive landscape analysis, feature gap analysis, or release velocity comparisons.
EnglishDecide whether an image or video found on a release page is editorial content (screenshots, demos, diagrams, product shots) or site chrome (avatars, logos, tracking pixels, decorative badges). Used during parsing to populate a release's media array.
EnglishHow to find, evaluate, and recommend the best ingestion method for changelog URLs — covers feed discovery, provider detection, GitHub API, markdown sources, and scraping…
EnglishHow to add, remove, list, validate, and manage changelog sources — covers ignored/blocked URLs, duplicate detection, and the validation…
EnglishHow the Releases fetch and parse pipeline works — covers feed vs scrape adapters, incremental vs bulk parsing, dry-run testing, crawl mode, content hashing, and…
EnglishUse the releases CLI to search, inspect, and manage the Releases.sh changelog registry from the terminal. Activate when the user mentions "releases CLI", runs a releases command, asks how to install the CLI, or wants to add/edit/fetch sources or organizations programmatically.
EnglishUse when the user asks about recent releases, changelogs, what's new in a library, breaking changes, version updates, or wants to compare products. Activates for questions like "what changed in Next.js 15?", "latest Tailwind releases", "compare Bun vs Deno releases".
EnglishCoordinate bulk playbook writing using parallel sub-agents — covers org discovery, prompt templates, model selection, batch dispatch, verification, and the parent-saves pattern for working around subagent permission limits. Local-only (Claude Code CLI) — managed agents do not yet support spawning sub-agents.
EnglishIncludes Analyzing Releases, Classify Media Relevance, Finding Changelogs, and other workflows.
Supported by the Atlas install prompt. Skill-specific requirements vary.
Pack stats
What’s included
Analyzing Releases
Analyze release trends across multiple companies to produce competitive intelligence. Use when asked to compare companies, analyze a market segment, identify industry trends, forecast upcoming releases, or answer questions like "what is X shipping lately" or "how does X compare to Y." Also triggers on requests for competitive landscape analysis, feature gap analysis, or release velocity comparisons.
Classify Media Relevance
Decide whether an image or video found on a release page is editorial content (screenshots, demos, diagrams, product shots) or site chrome (avatars, logos, tracking pixels, decorative badges). Used during parsing to populate a release's media array.
Finding Changelogs
How to find, evaluate, and recommend the best ingestion method for changelog URLs — covers feed discovery, provider detection, GitHub API, markdown sources, and scraping fallback
Managing Sources
How to add, remove, list, validate, and manage changelog sources — covers ignored/blocked URLs, duplicate detection, and the validation workflow
Parsing Changelogs
How the Releases fetch and parse pipeline works — covers feed vs scrape adapters, incremental vs bulk parsing, dry-run testing, crawl mode, content hashing, and enrichment
Releases CLI
Use the releases CLI to search, inspect, and manage the Releases.sh changelog registry from the terminal. Activate when the user mentions "releases CLI", runs a releases command, asks how to install the CLI, or wants to add/edit/fetch sources or organizations programmatically.
Releases MCP
Use when the user asks about recent releases, changelogs, what's new in a library, breaking changes, version updates, or wants to compare products. Activates for questions like "what changed in Next.js 15?", "latest Tailwind releases", "compare Bun vs Deno releases".
Seeding Playbooks
Coordinate bulk playbook writing using parallel sub-agents — covers org discovery, prompt templates, model selection, batch dispatch, verification, and the parent-saves pattern for working around subagent permission limits. Local-only (Claude Code CLI) — managed agents do not yet support spawning sub-agents.
Quick start
- Choose your skills. Select individual skills above, or choose the entire pack.
- Copy the install prompt. Use Copy install prompt above the list.
- Send it to your agent. Paste into your coding agent’s chat. Your agent reviews the source and guides the setup.
Try it with your agent
After installation, start with a request like:
Use the Analyzing Releases skill to help with my task.
Ask me for the context you need before getting started.Requirements & license
- A coding agent that can access your project files and install skills.
- Your agent checks each skill’s instructions, dependencies, and permissions during setup.
- Reported license for the skills shown: MIT. The author’s terms apply.