agentleFS
Sign inStart free
aprameyakaprameyak/github-agent-skills/skills/github-cleanup/SKILL.md

github-cleanup

Skill2 starsChanged 43 days agoMITView on GitHub

Conservative GitHub cleanup review. Use when the user asks to clean up GitHub, find clutter, empty/stale repos, old forks, duplicate-looking projects, or abandoned experiments. Suggests review candidates with evidence. Never deletes repositories.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. aadityad12/claude-skills★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository5 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Distinctive:

    Do not say: "Delete this."

    line 30
  2. Distinctive:

    Never decide a repository is useless.

    line 32
  3. Distinctive:

    READ ONLY for this skill.

    line 45
  4. Distinctive:

    No force-push, archive-without-asking, or visibility changes.

    line 47
  5. Distinctive:

    Always show evidence (size, last push date, fork parent, name group).

    line 48

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

github-cleanup

Help the user spot repositories and clutter worth reviewing. Be conservative.

Preconditions

  1. gh auth status succeeds.
  2. github-agent is on PATH.

Workflow

github-agent cleanup
# or
github-agent cleanup --json

Language rules (critical)

Say: "Consider reviewing…"

Do not say: "Delete this."

Never decide a repository is useless. People keep experiments, classwork, forks, and memories on purpose.

What to surface

  • Empty or near-empty repositories
  • Stale projects (no pushes for a long time)
  • Old forks
  • Versioned groups (app, app-v2, app-final)
  • Similar-looking duplicate names
  • Archived repos that may still dominate the profile story

Safety

  • READ ONLY for this skill.
  • Repository deletion is out of scope and must be refused.
  • No force-push, archive-without-asking, or visibility changes.
  • Always show evidence (size, last push date, fork parent, name group).

Output style

Friendly, non-judgmental, actionable. Offer to help organize next steps (pins, READMEs, archival discussion) only with explicit approval for any mutation.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free