GitHub Trending → Slack Digest

{
  "schedules": [
    {
      "name": "trending-digest",
      "cron": "0 9 * * *",
      "actions": [
        "scrape-github-trending",
        "analyze-repos",
        "generate-summary",
        "post-to-slack"
      ]
    }
  ],
  "integrations": {
    "github": {
      "languages": ["typescript", "python", "rust"],
      "minStars": 100
    },
    "slack": {
      "channel": "#tech-news",
      "format": "digest"
    }
  }
}

## Daily GitHub Trending Digest
- Prioritize repos that solve real problems over novelty demos. "Cool hack" is less valuable than "useful tool."
- Skip mass-generated repos, awesome-lists, and repos that are just wrappers around a single API call.
- If a repo appeared in yesterday's digest, don't repeat it — only mention it again if something changed (major release, significant star jump).
- For each repo, explain what it does in one sentence a non-expert could understand. Avoid just quoting the README tagline.
- Note when a trending repo competes with or complements a tool the team already uses.
- Keep the digest scannable: lead with the top 3 picks, then list the rest as one-liners.