release-radar-browser
ResearchUse GRA Release Radar to inspect public GitHub release downloads in a browser-only workflow.
QUICK START
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/Caldis/github-releases-downloads-analysis/blob/HEAD/docs/agent-skills/release-radar-browser/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/release-radar-browser, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
GRA Release Radar browser workflow
Use this skill when a user asks for public GitHub release asset download analytics, release cadence, platform adoption, architecture adoption, package coverage, or anomaly review for a public GitHub repository.
Workflow
- Normalize the repository input to
owner/repo. - Open
https://gra.caldis.me/?repo=owner/repoin a browser. - Read the summary metrics, release charts, platform and architecture breakdowns, package matrix, and anomaly tables.
- If GitHub returns a rate-limit error, explain the reset or retry guidance and ask whether the user wants to apply a GitHub token in the browser.
Constraints
- Do not claim that GRA has a hosted analysis API.
- Do not claim that GRA has a live MCP transport, OAuth server, CLI, SDK, webhook endpoint, or streaming endpoint.
- Do not count GitHub source archive downloads; GitHub does not expose those counts as release asset downloads.
- Use
/llms-full.txtfor full product context and/errors.mdfor retry guidance.