Skip to content
Back to search

github-curator

SkillWorks with Claude CodeGitHub

Claude plugin that recommends what to do with each repo on a GitHub account (keep, publish, archive, make private or delete) on a scorecard that quotes its evidence. It also triages every repo at once, and lists stargazers, forks, your pull requests to other projects and traffic history. It only recommends: it changes no repo and contacts no one.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/tcrossland--github-curator/badge.svg)](/listings/tcrossland--github-curator)

HTML

<a href="/listings/tcrossland--github-curator"><img src="/api/listings/tcrossland--github-curator/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

To update, upload the new release's zip the same way; claude.ai asks you to confirm before it replaces the version you have. A Claude Code session that was already open keeps the version it started with, even after the new one reaches its disk: a skill invoked again returns the text it loaded first. Start a new session to use the new version.

The skills run as `/github-curator:repo-review`, `/github-curator:stargazers`, `/github-curator:forks`, `/github-curator:contributions` and `/github-curator:traffic`.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/plugin.json · Manifest · 10 lines
  1. {
  2. "name": "github-curator",
  3. "version": "0.5.0",
  4. "description": "Claude plugin that recommends what to do with each repo on a GitHub account (keep, publish, archive, make private or delete) on a scorecard that quotes its evidence. It also triages every repo at once, and lists stargazers, forks, your pull requests to other projects and traffic history. It only recommends: it changes no repo and contacts no one.",
  5. "author": {
  6. "name": "Tomas Crossland",
  7. "url": "https://github.com/tcrossland"
  8. },
  9. "license": "Apache-2.0"
  10. }
README.md · README · 62 lines
  1. # github-curator
  2. github-curator is a [Claude plugin](https://claude.com/docs/plugins/build.md) that recommends what to do with each repo on a GitHub account: keep it, publish it, archive it, make it private or delete it, and whether to pin it to the profile. Each finding on its scorecard quotes the line it's based on, from a file or the repo's settings, and a script checks every quote from a file against that file. It only recommends; you make the changes.
  3. I built it to sort out my own GitHub account, which had years of forks, experiments and half-finished work on it: to see it the way a potential employer or collaborator meets it, and to find out how far a Claude plugin can go on work whose every claim can be checked. One thing it showed me: my first triages counted a fork's commits on its default branch only, and of the 52 forks I deleted on that count, 17 held commits of mine on other branches, such as `develop`. GitHub keeps a deleted fork's commits with the original project, where they can still be fetched by hash, and the review now counts every branch. The figures are in `docs/github-facts.md` in its repository.
  4. <picture>
  5. <source media="(prefers-color-scheme: dark)" srcset="https://github.com/tcrossland/github-curator/raw/main/docs/images/scorecard-finding-dark.png">
  6. <img alt="The first question on this repo's own scorecard, marked pass: the finding, and the two README lines it quotes, each with its file and line number" src="https://github.com/tcrossland/github-curator/raw/main/docs/images/scorecard-finding.png">
  7. </picture>
  8. It holds five skills, each a set of instructions Claude follows when you run its command:
  9. - [`repo-review`](skills/repo-review/SKILL.md): recommends what to do with a repo and the work worth doing first, finds similar repos, checks the repo or a README draft against seven questions, and publishes a scorecard to a page in your claude.ai account (an artifact, private until you share it), with a fix prompt to paste into Claude Code. It runs in these modes:
  10. - `repo-review` with a repo URL, a local clone's folder, a file or pasted text: one full review.
  11. - `repo-review triage`: a quick first pass over all of an account's repos from the API, which settles the clear deletes and names the repos worth a full review. `triage org:NAME` does the same for an organisation's repos.
  12. - `repo-review overview`: reviews several repos and ranks them.
  13. - `no-publish`, in any mode: saves the page as a file rather than publishing it.
  14. The seven questions, most important first, each marked pass, fail or flagged:
  15. - **Hook**: would someone outside the niche understand what it is, why it's interesting and what it found?
  16. - **Findable**: is it public, with a description and topics in the words people search for?
  17. - **Facts**: does every result, status, version, command, link and tag match its source?
  18. - **Defensible**: does each strong claim point to the test, report or file that proves it?
  19. - **Context**: are the field's terms defined or linked where they first appear?
  20. - **Way in**: can a visitor run it, reuse part of it or join in, under a licence that lets them?
  21. - **Tone**: does it read as finished work that shows the author's judgement, rather than internal notes?
  22. - [`stargazers`](skills/stargazers/SKILL.md): lists who starred a repo and when, and picks out the stargazers whose own work is in the same field. With no repo given it covers every public repo of yours that has stars; `since:YYYY-MM-DD` keeps only recent stars, and `all` reads every stargazer, not only the 30 most recent. GitHub lists stargazers only to a repo's owner, so it works on your own repos. The repo review runs its Steps 1 to 3 for the scorecard's Outcomes panel.
  23. - [`forks`](skills/forks/SKILL.md): lists the forks of a repo that hold commits of their own, on any branch, what those commits change and who made them, and picks out the ones worth a look, such as a fork that fixes something the repo still gets wrong. With no repo given it covers every public repo of yours that has forks; `all` reads every fork pushed to since it was made, not only the 30 most recent. The repo review runs its Steps 1 to 3 for the scorecard's Outcomes panel.
  24. - [`contributions`](skills/contributions/SKILL.md): lists your merged pull requests to repos you don't own, in three groups: your own organisations' (counted), your employers' (listed apart, once you name them with `employers:OWNER`) and other people's projects, one row per repo with its stars, the dates and what you did. Pull requests to private repos are counted, never named.
  25. - [`traffic`](skills/traffic/SKILL.md): saves the views, clones, stars and top referrers of every public repo you own to a page titled "Traffic history", which charts them. GitHub keeps traffic for 14 days only, so run it once a week; `schedule` sets up a weekly task that does. On claude.ai the repos must be attached to the chat with push access first, which it asks for, and a scheduled run reads only those attached in the chat that created it.
  26. All five read GitHub through `gh api`, and `forks` reads the forks' commits with git. Before publishing a private repo, the review also scans its full history for keys and tokens with [betterleaks](https://github.com/betterleaks/betterleaks), if it's installed (`brew install betterleaks`), or on claude.ai fetched into the session's own VM and checked against its release's checksums; it only detects, and never sends a secret anywhere. The skills' instructions rule out following, starring, commenting on or messaging anyone, opening an issue or pull request, and archiving, deleting or changing the visibility of a repo: the review only recommends. Where a step needs one of those, such as deleting the repos a triage marks clear, the page gives you the commands to run yourself.
  27. In a claude.ai chat, GitHub answers only for the repos attached to the chat, so the skills ask you once to attach the ones they need and read public repos with git. An organisation's triage runs only in Claude Code, on your own computer, and the first triage of an account that would need more than 10 approvals to attach repos is better run there too. On claude.ai the review reads the profile's pinned repos from the profile page, which may miss some, and `contributions` can't read your organisations, so its count of private pull requests can be short.
  28. ## Try it
  29. It runs in a claude.ai chat or in Claude Code. In Claude Code it reads GitHub with your own `gh`, so sign in first with `gh auth login`. In a claude.ai chat it uses the chat's own access to GitHub, and asks before attaching the repos it needs.
  30. 1. Download the zip from the [latest release](https://github.com/tcrossland/github-curator/releases/latest) and upload it to claude.ai: Plugins in the left sidebar > Add > Upload plugin.
  31. 2. In a new chat, or a new Claude Code session in the Claude desktop app, which picks up plugins uploaded to claude.ai, review one of your repos:
  32. ```
  33. /github-curator:repo-review https://github.com/OWNER/REPO
  34. ```
  35. It publishes the scorecard to a page in your claude.ai account and replies in three lines: what to do with the repo, the most important fix, and how many of the seven questions pass, fail or are flagged. On an account with many repos, start with `/github-curator:repo-review triage`.
  36. ## Install and update
  37. To update, upload the new release's zip the same way; claude.ai asks you to confirm before it replaces the version you have. A Claude Code session that was already open keeps the version it started with, even after the new one reaches its disk: a skill invoked again returns the text it loaded first. Start a new session to use the new version.
  38. The skills run as `/github-curator:repo-review`, `/github-curator:stargazers`, `/github-curator:forks`, `/github-curator:contributions` and `/github-curator:traffic`.
  39. ## Working on it
  40. It doesn't take outside contributions yet: `CONTRIBUTING.md` in its repository says how to report a problem and how changes are made. Notes for changing the plugin, and how to run its tests, are in `docs/README.md` in its repository. They don't ship in the zip.
  41. ## Licence
  42. Apache License 2.0: see [LICENSE](LICENSE) and [NOTICE](NOTICE).

Version history

  • v0.5.011/22/2026

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.