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

github-polish

Skill2 starsChanged 43 days agoMITView on GitHub

Improve GitHub presentation: profile, profile README, descriptions, topics, homepage URLs, README intros, and consistency. Use when the user asks to make GitHub look better, look put together, or polish their profile/repos.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

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

    Do not silently edit the default branch for content changes.

    line 47
  2. Distinctive:

    Do not invent project capabilities.

    line 48
  3. Distinctive:

    Prefer small, accurate descriptions over marketing fluff.

    line 49
  4. Distinctive:

    Keep language approachable.

    line 51

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

Make the user's GitHub look put together using evidence from their actual repositories.

Preconditions

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

Workflow

  1. Analyze presentation gaps:
    github-agent polish
github-agent polish --json
  2. For each improvement:
    • Infer suggestions only from repository evidence (README preview, language, topics, homepage, code signals).
    • Never fabricate features, stack, or impact.
  3. Apply changes with the correct safety lane:

Metadata (description / topics / homepage)

  1. Propose exact new values.
  2. Preview (github-agent apply-metadata ... without --execute).
  3. Get explicit user approval.
  4. Apply with --execute.

Content (README / profile README)

  1. Create a branch.
  2. Modify locally.
  3. Show the diff.
  4. Get approval.
  5. Push and open a pull request with gh.

Rules

  • Do not silently edit the default branch for content changes.
  • Do not invent project capabilities.
  • Prefer small, accurate descriptions over marketing fluff.
  • Topics should be real, conventional, and grounded in evidence.
  • Keep language approachable; offer technical detail on request.

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