github-checkup
Skill2 starsChanged 43 days agoMITView on GitHub
Read-only GitHub account checkup. Use when the user asks to check their GitHub, "how's my GitHub", review their profile/repos presentation, or run a GitHub checkup. Produces friendly, evidence-backed findings without changing anything on GitHub.
- Installs packages
In this repository5 other files it gives its agents.
- github-cleanupSkill
- github-fixSkill
- github-polishSkill
- github-recapSkill
- github-todaySkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 5 are distinctive, and 1 is 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.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 64
READ ONLY. Never mutate GitHub.
- Distinctive: line 65
Never invent accomplishments, technologies, or metrics.
- Distinctive: line 66
Never rate the person as a developer.
- Distinctive: line 67
Prefer plain language. Add technical detail only after the plain explanation.
- Distinctive: line 68
Every recommendation must cite evidence from the CLI/JSON output.
- Very specific: line 69
Do not clone every repository.
≈ “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.
Files
github-checkup
Help the user understand how their GitHub account is doing — presentation, clarity, and a few attention items — without judging them as a developer.
Preconditions
gitandghare installed.gh auth statussucceeds.github-agentis installed (pip install -e .from this repo, or via./install.sh).
Workflow
- Confirm authentication:
github-agent auth-check --json - Collect + analyze (read-only):
For machine-readable output:github-agent checkupgithub-agent checkup --json - Optionally reuse a snapshot:
github-agent snapshot --out /tmp/gh-snapshot.json github-agent checkup --snapshot /tmp/gh-snapshot.json
Output style
Lead with a friendly summary like:
GitHub Checkup
I looked through your profile and 12 repositories.
I found 7 things worth looking at:
- 3 quick fixes
- 2 projects that could be easier to understand
- 1 older project worth reviewing
- 1 failed automated buildThen explain the most useful findings with evidence.
Adapt to account size:
- Few repos → keep it short and concrete.
- Many repos → prioritize; do not dump enterprise metric walls.
Rules
- READ ONLY. Never mutate GitHub.
- Never invent accomplishments, technologies, or metrics.
- Never rate the person as a developer. Talk about account health and presentation.
- Prefer plain language. Add technical detail only after the plain explanation.
- Every recommendation must cite evidence from the CLI/JSON output.
- Do not clone every repository. Rely on
github-agentprogressive inspection.
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
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.

