package-release-snifferlisted

# Package Release Sniffer Use this skill to find newly published packages or meaningful package releases before they become general news. ## Workflow 1. Define the package ecosystem and freshness window before searching. 2. Check primary release surfaces first: registry package pages, registry APIs, release feeds, GitHub Releases, changelogs, model cards, and maintainer announcement posts that link to the package. 3. Record the package name, ecosystem, version, publish time, source URL, maintainer or organization, license signal, install surface, and why the release matters. 4. Prefer packages with concrete shipped artifacts: new package, major/minor version, security fix, SDK/API capability, model/runtime integration, benchmarked performance change, or developer workflow impact. 5. De-duplicate aliases across registry pages, GitHub repositories, model cards, and maintainer posts. 6. Mark uncertainty when publish time, package identity, maintainership, license, or artifact availability is unclear. ## Source Priority Use primary sources before secondary mentions: - npm package pages and npm registry metadata - PyPI project pages and release history - GitHub Releases, tags, changelogs, and repository package metadata - Hugging Face model, dataset, Space, and library release pages when they behave like package artifacts - crates.io, Go package/module pages, Maven Central, NuGet, Docker Hub, or similar registries when relevant - Maintainer blogs or docs only when they link