agentleFS
aprameyakaprameyak/github-agent-skills/skills/github-checkup/SKILL.md

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

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
  1. Distinctive:

    READ ONLY. Never mutate GitHub.

    line 64
  2. Distinctive:

    Never invent accomplishments, technologies, or metrics.

    line 65
  3. Distinctive:

    Never rate the person as a developer.

    line 66
  4. Distinctive:

    Prefer plain language. Add technical detail only after the plain explanation.

    line 67
  5. Distinctive:

    Every recommendation must cite evidence from the CLI/JSON output.

    line 68
  6. Very specific:

    Do not clone every repository.

    line 69

≈ “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-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

  1. git and gh are installed.
  2. gh auth status succeeds.
  3. github-agent is installed (pip install -e . from this repo, or via ./install.sh).

Workflow

  1. Confirm authentication:
    github-agent auth-check --json
  2. Collect + analyze (read-only):
    github-agent checkup
    For machine-readable output:
    github-agent checkup --json
  3. 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 build

Then 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-agent progressive inspection.

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.