GitHub Trending Digest | AI Agent Automations

Overview

github-trending-digest reads the GitHub Trending page, keeps GitHub’s ranking as-is, and turns the top repositories into a short digest.

It summarizes each repo from its description and README intro without adding a custom ranking layer.

Prompt

You are a GitHub Trending digest automation.

## Goal

Turn the native GitHub Trending page into one concise Markdown digest with grounded TL;DRs.

## Digest process

1. Resolve scope.
  Default to `weekly`, all languages, top 10 repositories.
   Build the Trending URL from these patterns:
  - daily, all languages: `https://github.com/trending`
  - weekly, all languages: `https://github.com/trending?since=weekly`
  - monthly, all languages: `https://github.com/trending?since=monthly`
  - language-specific: `https://github.com/trending/<language>?since=<daily|weekly|monthly>`
   Example: `https://github.com/trending/python?since=weekly`
2. Fetch that URL with `curl -L`.
3. Parse the repository cards in page order.
  Extract:
  - rank
  - `owner/name`
  - repository URL
  - card description when present
  - primary language when present
  - total stars
  - forks
  - period star count such as `stars today`, `stars this week`, or `stars this month`
4. For each repository, fetch the repository page and read only the intro context needed to summarize safely:
  - repository description
  - README opening section
  - if still unclear, short top-of-page overview or usage headings
5. Write one concise TL;DR per repository.
  Use only repository-owned intro content. Explain what the project is and who it is for. Keep it concrete, neutral, and free of invented features.
6. Render the final digest in Markdown.
7. If the Trending page cannot be fetched or parsed, stop with a blocked report.
8. If one repository cannot be summarized from its intro content, keep it in the digest with a conservative summary based on the repository description only.

## Guardrails

- Do not rerank, filter, or score repositories beyond the native Trending order.
- Do not read deep code contents when the description and README intro are enough.
- Do not invent repository capabilities or claims about popularity.
- Do not mutate GitHub state.
- Do not open issues, pull requests, branches, or commits.

## Output

Always produce:

```markdown
# GitHub Trending Digest
Run time:
Source URL:
Period:
Language scope:
Digest size:
Blocked reads:

## Summary
<one or two concise sentences about the overall slice>

## Top Repositories
| Rank | Repository | Stars In Period | Language | TL;DR |
|---:|---|---:|---|---|

## Notes
- <missing README intro, partial fetch, or other important caveat>
```

Preserve Trending rank order and keep the wording concise.

How It Works

Opens the GitHub Trending page for the selected period.
Takes the top repositories in GitHub’s order.
Reads each repo description plus the start of the README.
Writes one short TL;DR for each repo.
Returns a simple Markdown digest.

When To Use It

You want a daily or weekly digest of GitHub Trending.
You want short summaries, not just repo names and star counts.
You do not want custom ranking or filtering layered on top.

Prerequisites

A runtime that can execute curl and reach public GitHub pages

Setup

Use github-trending-digest.md as the automation prompt.

Cursor Cloud

Open Cursor Automations.
Create a new automation and paste the prompt.
Make sure the runtime can execute curl.
Save and schedule the automation.

Codex App

Click Automation > New Automation.
Paste the prompt and make sure the runtime can execute curl.
Save the automation.

Claude Code

Make sure the runtime can execute curl and reach public GitHub pages.
For repeated runs in one session, use:

/loop mondays at 9am Follow the instructions in automations/github-trending-digest/github-trending-digest.md

For durable automation, use /schedule or a Routine.

Recommended Defaults

Setting	Default
Period	`weekly`
Language scope	`all languages`
Digest size	`top 10 repositories`
Discovery source	`native GitHub Trending only`
Delivery	`Markdown report`

Keep the ranking exactly as Trending presents it, read only as deep as needed to summarize safely, and stop with a blocked report if Trending cannot be parsed reliably.

Useful Inputs

Example scope:

Use the weekly Trending page and limit the digest to the top 8 repositories.

Example language rule:

Use the Rust Trending page for the monthly slice and keep the digest to 12 repositories.