analyzing-releases
Installation
SKILL.md
Analyzing Releases
Turn changelog data into competitive intelligence by analyzing release patterns across a cohort of related companies.
This is a reader workflow — it uses only the public, unauthenticated tools. There is no AI summarize/compare tool on the hosted MCP and no summary/compare command in the CLI; you fetch the raw release data and synthesize the analysis yourself.
Tools for each step
| Operation | CLI (reader) | MCP tool |
|---|---|---|
| Find what's indexed for a company | releases search <company> --json |
search (with type: ["orgs","catalog"]) |
| List a company's sources | releases list --query <company> --json |
list_catalog (scope with organization) |
| Latest releases (source or org) | releases tail <slug> --json · releases tail --org <org> --json |
get_latest_releases (organization / product, since/until) |
| Keyword/semantic release search | releases search <query> --json |
search with type: ["releases"] |
| Read one release in full | releases get <rel_id> --json |
get_release |
| Read a tracked CHANGELOG slice | releases admin source changelog <slug> --tokens <n> (key-gated; readers use MCP) |
get_catalog_entry with changelog_tokens / changelog_offset (keyless) |
All releases are indexed already — you don't need to (and as a reader can't) trigger fetches. If a company isn't in the registry at all, say so rather than trying to onboard it; onboarding is an operator task.