PlugWiki

github-profile-optimization Skill (samber): Fix Profile

Makes Claude audit and rebuild a GitHub personal or organization profile: README, pins, bio and contribution signals.

Installs
12.4K
on skills.sh
Stars
7
on GitHub
Files
6
besides SKILL.md
Updated
Nov 2026
last repo commit

github-profile-optimization scores a GitHub profile against a scorecard of four blocking checks and eight scored checks worth two points each, then orders fixes by return per hour. It drafts three positioning sentences, rebuilds the profile README from a skeleton, sets the six pins, handles the contribution graph honestly and re-scores. The ship bar is 13 of 16, which SKILL.md calls its own baseline, not a published one.

Claude can run scripts/profile-audit.py, which calls GitHub's API for a public account. Setting GITHUB_TOKEN is optional and adds pinned items. SKILL.md says it is not for a single repository README and names readme-optimization for that.

Good for

  • Engineers whose GitHub profile gets read during hiring
  • DevRel practitioners preparing a talk or launch
  • Companies with an empty GitHub organization page

Install github-profile-optimization

Claude Code

  1. 1

    Copy this prompt.

    Install the github-profile-optimization skill in Claude Code. Run this command:
    
    /plugin marketplace add samber/developer-relations-skills
    /plugin install developer-relations-skills@developer-relations-skills
    
    Then check that it loaded and tell me how to use it.
  2. 2

    Paste it into Claude Code. It shows the change and asks before running it.

Install the whole set, not one skill: the README says the skills reference each other, so picking one leaves those pointers going nowhere. The repo tree holds 93 skill folders. Fourteen of them bundle .py or .sh files; github-profile-optimization bundles one, scripts/profile-audit.py. The tree holds no hooks, agents or MCP config files.

From the project README. Source.

What's in the skill

When it loads

Audits and rebuilds a personal or organization profile on GitHub as a developer-relations surface - the profile README, the six pinned items, bio and social fields, the organization profile repository, and the contribution signals visitors read as evidence. Use whenever someone says "optimize my GitHub profile", "profile README", "our GitHub org page is empty", "what should I pin", "nobody knows what our company builds on GitHub", or is preparing a launch, a talk or a job search - even if they only mention their GitHub page. Covers solo maintainers, company organizations, and engineers whose profile gets read during hiring. GitHub-scoped: the audit script and pin/contribution-graph mechanics are GitHub-specific, though the checklist reasoning transfers by hand to another forge. Not a single repository's README - use samber/developer-relations-skills@readme-optimization.

Sections in SKILL.md

  1. Calibrate what you promise
  2. Interview
  3. Step 1 - Collect the facts
  4. Step 2 - Score the page
  5. Order the fixes
  6. Step 3 - Fix what is false before improving what is weak
  7. Step 4 - Brainstorm the positioning before writing it
  8. Step 5 - Rebuild the page
  9. Step 6 - Set the pins deliberately
  10. Step 7 - Handle contribution signals honestly
  11. Step 8 - Verify, then keep it alive
  12. What to track afterwards
  13. Common failure modes
  14. Reference

Key facts

Installs on skills.sh
12,397 (Nov 2, 2026)
Last repo commit
Nov 1, 2026

What it includes

  • Reads published findings before quoting any figure

    Read · Calibrate what you promise

  • Questions 1-4 gate the rewrite

    Read · Interview

  • Runs the audit script, or you paste the README and pins

    The script reports profile fields, README facts, third-party widgets and unpinned repo candidates.

    Runs code · Step 1: collect the facts

  • Four blocking checks and eight two-point checks, then a fix order

    Write · Step 2: score the page

  • Removes false claims before improving weak ones

    Write · Step 3: fix what is false

  • Three candidate positioning sentences with trade-offs

    Write · Step 4: positioning

  • Picks a skeleton and drafts one section at a time

    Skeletons cover maintainer, DevRel practitioner, engineer and organization.

    Write · Step 5: rebuild the page

  • Chooses the six pins against your goal, not star count

    Write · Step 6: set the pins

  • Handles the graph and achievements honestly

    Read · Step 7: contribution signals

  • Re-scores; ships at 13 of 16 with all blocking checks passed

    Write · Step 8: verify and keep alive

  • Calls GitHub REST and GraphQL APIs for a public account

    Optional GITHUB_TOKEN raises the rate limit and adds pinned items.

    Runs code · profile-audit.py

From the official docs

Permissions

Low risk

github-profile-optimization is planning instructions plus one script, and it may save notes to devrel-context.md. Our advice: check that file before you commit it.

What it can do

  • Read your data
  • Create and change things
  • Delete things
  • Read-only mode

Watch out for

  • It may save notes to devrel-context.md

    SKILL.md tells Claude to keep task and project context in devrel-context.md when memory lives in a file, or in the memory system your tool already uses. Check the file before you commit it. github.com

  • The audit script calls GitHub and can use your token

    profile-audit.py requests api.github.com and, for the profile README, the download URL the API returns. If GITHUB_TOKEN is set, it sends the token in an Authorization header to GitHub. Leave it unset if you do not want that. github.com

  • The whole-set install adds 93 skills, 14 with scripts

    The README says to install every skill. The git tree has 93 skill folders and 14 of them hold .py or .sh files. The tree holds no hooks, agents or MCP config files. github.com

Technical details
Turning on read-onlySKILL.md describes no read-only mode.
Talks toapi.github.com
Sign-in and keysOptional GITHUB_TOKEN environment variable read by the bundled profile-audit.py script.
Scopes
  • Claude writes the plan or report in the conversation

  • May save notes to devrel-context.md when memory lives in a file

  • Can run python3 scripts/profile-audit.py <account>

  • Optional GITHUB_TOKEN environment variable read by that script

Questions

What does github-profile-optimization do?

It makes Claude audit your GitHub profile or organization page and rebuild it as a developer-relations surface. It scores the page, sets pins and drafts the profile README.

How do I install it?

Use the install box at the top. The README says to install every skill in the repo because the skills point to each other, so the box shows whole-set routes.

Does it need a GitHub token?

No token is required. The script reads GitHub's public API. Setting GITHUB_TOKEN raises the hourly rate limit and includes pinned items, which only the authenticated GraphQL API exposes.

Does it work on GitLab or Codeberg?

The script does not. SKILL.md says it has no equivalent for GitLab, Codeberg or a self-hosted forge, and says to apply the checklist by hand there.

Can I use it to improve a repository README?

No. SKILL.md names readme-optimization for a single repository README.

Is it safe to install?

Claude can run one Python script that makes requests to GitHub's API for the account you name. If you set GITHUB_TOKEN, the script sends it to api.github.com as a bearer token. Claude may also save notes to a devrel-context.md file.

Information

updated Nov 2, 2026

Folder
skills/github-profile-optimization

samber/developer-relations-skillsskills.sh

Sources

Docs, issue trackers and discussions this page is built from.

Show all 7
  1. README · github.com
  2. marketplace.json · github.com
  3. plugin.json · github.com
  4. github-profile-optimization SKILL.md · github.com
  5. LICENSE · github.com
  6. skills.sh listing · skills.sh
  7. github-profile-optimization scripts/profile-audit.py · github.com

Updated Nov 2, 2026.