# Github Star Velocity

> Github Star Velocity is an Agent Skill for research published in the Tracer-Cloud/opensre repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Compute GitHub repository star velocity over a rolling time window using the stargazers API.

- Skill name: `github-star-velocity`
- Category: [Research](https://www.openparable.com/skill/research/1)
- Source: https://github.com/Tracer-Cloud/opensre/blob/HEAD/tools/system/python_execution_tool/skills/github-star-velocity/SKILL.md
- Repository: Tracer-Cloud/opensre (8,511 GitHub stars when collected)

## SKILL.md

# GitHub Star Velocity

Use this skill when the user asks for GitHub star velocity, stars gained in the
last N hours, star growth rate, or similar metrics for a repository.

## Prerequisites

1. Set `allow_network: true` on `execute_python_code`.
2. Read `GITHUB_TOKEN` from the subprocess environment (injected when GitHub
   credentials are configured). Never print the token.
3. Parse `owner/repo` from the repository URL or user input.

## API approach

1. Fetch current `stargazers_count` from `GET /repos/{owner}/{repo}`.
2. Fetch stargazers with timestamps from
   `GET /repos/{owner}/{repo}/stargazers?per_page=100` using
   `Accept: application/vnd.github.v3.star+json`.
3. Each entry includes `starred_at`. Count stars where `starred_at` is within
   the requested window (for example, the last 24 hours).

## Critical pagination trap

Stargazers are returned **oldest first**, not newest first. Do **not** stop
after the first page when the newest entries on that page fall outside the
window — that produces a false zero.

Instead, paginate through **all** pages (follow the `Link` response header
until there is no `rel="next"`) and count every `starred_at` inside the window.

## Sanity check before reporting

Treat these results as suspicious and rerun with a full paginated scan before
answering:

- `0` stars in the last 24 hours for a repo with thousands of stars and recent
  activity
- Velocity that implies losing stars without an explicit unstar request
- Counts that disagree sharply with `stargazers_count` deltas when you have a
  recent baseline

When a result looks wrong, widen the scan (all pages), print the most recent
`starred_at` observed, and only then return the velocity.

## Output shape

Return:

- Total current stars
- Stars gained in the window
- Velocity (stars per hour and stars per day)
- Window start timestamp (UTC)
- Most recent `starred_at` in the window
- Optional hourly breakdown for the last 24 hours

---

Source: https://www.openparable.com/skill/research/github-star-velocity (OpenParable). Cite the canonical URL above.
