Skip to main content
skill CX Codex

github-glowup — Claude Code skill for GitHub profile audits

The github-glowup Claude Code skill audits a GitHub profile from a recruiter’s perspective and drafts improvements. Run it to revise a profile, select pinned repositories, or write a profile README.

MIT ★ 345 updated 2026-11-14

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add nishant-Tiwari24/cracked
/plugin install cracked@cracked
Open on GitHub

What github-glowup does

The skill reviews the profile, pinned repositories, READMEs, descriptions, topics, commit activity, and possible exposed secrets. It assesses the first impression and turns its findings into a repository pinning plan.

Its drafts can include bio options, a profile README, rewrites for key repository READMEs, descriptions, and topics. It asks for permission before applying changes. GitHub data can be collected with gh or the GitHub API; without a Skill tool, the agent can follow the relevant SKILL.md from the cracked skills folder instead.

What it helps with

  • audit a GitHub profile from a recruiter’s perspective
  • choose repositories to pin and set their order
  • rewrite a profile README and key project READMEs
  • identify exposed secrets and outline the response

Example prompts for the agent

  • Audit my GitHub profile and suggest concrete improvements.
  • Draft a profile README and plan which repositories to pin.
  • Check my pinned repositories for exposed secrets and rewrite their descriptions.

How to install github-glowup

1Plugin marketplace

/plugin marketplace add nishant-Tiwari24/cracked
/plugin install cracked@cracked

This installs the whole cracked plugin with all its skills

2Skills CLI (Vercel)

npx skills add nishant-Tiwari24/cracked --skill github-glowup -a claude-code

3Manually: put the files in place

~/.claude/skills/github-glowup/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/github-glowup/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about github-glowup

How do I install github-glowup in Claude Code?

Add the marketplace with /plugin marketplace add nishant-Tiwari24/cracked, then install the skill with /plugin install cracked@cracked.

What does github-glowup do?

It reviews a GitHub profile and its repositories, then drafts profile and repository updates. It only applies changes after receiving permission.

What does github-glowup need to work?

It can gather data with gh or the GitHub API. gh can read public data without authentication, with lower rate limits; changes through gh require authentication with the user scope.

Source text

SKILL.md · MIT
---
name: github-glowup
description: Audit and upgrade a candidate's GitHub profile the way recruiters and interviewers see it, covering profile README, pinned repos, repo READMEs, descriptions, topics, commit history and red flags, then draft the fixes (profile README, repo READMEs, descriptions) and apply them only with permission. Use when the user wants to improve their GitHub profile, make GitHub recruiter-ready, write a profile README, choose pinned repos, or get feedback on their GitHub.
---

# GitHub glow-up

A recruiter clicks the GitHub link on a resume and decides in about 10 seconds whether this person builds things. Make those 10 seconds count.

## 0. Setup

1. Call the Skill tool with "cracked-profile" for the GitHub username. Otherwise ask, or use `gh api user --jq .login`.
2. Gather data. Prefer `gh` (works unauthenticated for public data, with lower rate limits); fall back to `curl https://api.github.com/...`:
   - Profile: `gh api users/<u>` (name, bio, company, location, blog, followers, public_repos)
   - Repos: `gh api "users/<u>/repos?per_page=100&sort=updated"` (name, description, language, stars, fork, topics, homepage, pushed_at, archived)
   - Pinned: `gh api graphql -f query='{ user(login:"<u>") { pinnedItems(first:6, types:REPOSITORY) { nodes { ... on Repository { name description stargazerCount primaryLanguage { name } } } } } }'`
   - Profile README: `gh api repos/<u>/<u>/readme --jq .content | base64 -d` (it may not exist)
   - For the top 6 candidate repos, read each README and glance at the tree (`gh api repos/<u>/<repo>/contents`).
   - Contribution activity: `gh api graphql -f query='{ user(login:"<u>") { contributionsCollection { contributionCalendar { totalContributions } } } }'`

## 1. The 10-second view

Describe exactly what a recruiter sees, top to bottom: avatar/name/bio, profile README, pinned repos, and the contribution graph. Then give the verdict: "Does this look like someone who builds things? Yes / Kind of / No."

## 2. Audit

Score and comment on each area:

| Area | What good looks like |
|---|---|
| Bio and identity | Real name, a one-line role bio (example: "Backend dev · Go & Postgres · <grad year> grad"), location, links |
| Profile README | Short: who you are, what you're building now, 3 best projects with one line each, how to reach you. No stat-widget overload, no giant GIFs |
| Pinned repos | 4–6 of your *best original* work, matching your target role. No forks, no tutorial clones, no college assignments unless they're impressive |
| Repo READMEs | For each pinned repo: what it is, a screenshot/GIF/demo link, the stack, how to run it, key technical decisions |
| Repo hygiene | Descriptions, topics, a homepage link if deployed, a license, no committed `node_modules`/`.env`/secrets |
| Activity | Consistent, real commits. Never suggest fake-commit generators: interviewers spot them and it's dishonest |

**Check for leaked secrets** in the top repos: search for patterns like `API_KEY=`, `sk-`, `AKIA`, or a committed `.env`, using code search or the file tree. If you find any, this is the **#1 priority**: tell them to rotate the key immediately and purge it from history.

## 3. Draft the fixes

Produce, in the conversation:
1. **New bio** (3 options).
2. **Profile README** in the **house layout** (the same for every user; see "The house layout" in [README-STYLES.md](README-STYLES.md) and [examples/neofetch-nishant-Tiwari24.md](examples/neofetch-nishant-Tiwari24.md)). Exactly two code blocks, nothing else:
   1. **Portrait block (Style E):** their photo as braille ASCII on the left, `neofetch`-style facts on the right (handle, OS, uptime, host, kernel, languages, achievements count, contact, GitHub stats). Ask once before using their photo; if they say no, use their name as a figlet banner on the left instead.
   2. **Achievements tree:** every hackathon win, award, scholarship, rating or notable result they have, one line each in `├──` / `└──` tree style: name, track or category, result and prize, aligned in columns. Use their existing README, profile and what they tell you; ask for anything missing.

   Leave out projects, LeetCode/stat sections, widgets, badges, tables and link lists: the pinned repos show the projects, and the house layout stays short. Keep every line ≤ 90 columns. Never describe a project's features, numbers or organisation that you haven't read in its code or README, or been told; write `[what it does]` and ask instead. Generate any ASCII art with a tool, never by hand. If the user asks for another look, offer styles A–D from README-STYLES.md.
3. **Pin plan**: which 4–6 repos to pin and in what order, with what to unpin and why.
4. **README rewrites** for the 2–3 most important repos, from their actual code (read it), using this template: title + one-line pitch → demo/screenshot → features → tech stack → architecture (a short note, or a diagram if useful) → run locally → what I learned / technical challenges.
5. **Descriptions and topics** for each pinned repo.

**Fact check before you show any draft.** Go through every bio, README and description line and ask, for each factual claim (a feature, number, habit, organisation, tech, achievement): *did I read this in their repo or profile, or did they tell me?* If not, replace it with a `[placeholder]` or delete it. That includes flattering filler like "solving DSA daily" or "organised by pattern". Then add one line under the drafts: `Fact-checked: every claim is from your repos or what you told me; [placeholders] need your input.`

## 4. Apply (only with explicit permission)

Changes are public. Ask per item: "Want me to apply this?" Then:
- Bio: `gh api -X PATCH user -f bio="…"` (needs `gh auth` with the user scope).
- Profile README: create or update the `<u>/<u>` repo's README via a clone, commit and push, or via the contents API.
- Repo description/topics: `gh repo edit <u>/<repo> --description "…" --add-topic …`.
- Repo READMEs: clone, edit, commit, push (or open a PR if they prefer).
- Pinning has no API, so give them the exact click path.

## 5. Scorecard

Call the Skill tool with "cracked-profile" and log a scorecard titled `github.com/<u>`. Dimensions: **First Impression, Pinned Work, READMEs, Hygiene & Security, Activity**.

---

*Skill calls:* if your agent has no Skill tool, open the named skill's `SKILL.md` in the cracked skills folder (`core/`, `interview/`, `profile/`, `strategy/`) and follow it instead.

© Nishant Tiwari · MIT · nishant-Tiwari24/cracked

Similar skills

All skills for Git and GitHub →

From the same set20

The whole set →
core-viva The core-viva Claude Code skill quizzes developers on CS fundamentals and SQL. It starts for interview revision and adjusts question difficulty based on answers. CX Codex +1 ★ 345repo stars offer-decode The offer-decode Claude Code skill breaks down a job offer and estimates take-home pay. It runs on an offer letter, a CTC breakdown, or a request to compare terms and draft a negotiation reply. CX Codex +1 ★ 345repo stars system-design-mock The system-design-mock Claude Code skill runs practice interviews for system design, from fresher to SDE-2 level. It starts when someone asks to rehearse HLD or LLD, including a design prompt for a specific system. CX Codex +1 ★ 345repo stars referral-dm The referral-dm Claude Code skill drafts tailored messages for referral requests and job outreach. It can respond to hiring posts, contact recruiters or alumni, and write follow-ups. CX Codex +1 ★ 345repo stars company-intel company-intel — a skill for Claude Code and Codex that generates interview preparation briefs for target employers. Runs when naming a company before technical or behavioral rounds. CX Codex +1 ★ 345repo stars roast-my-resume roast-my-resume — a Claude Code skill that reviews technical resumes and suggests edits. It checks ATS readiness, recruiter-facing presentation and weak bullets against the candidate’s experience and target company. CX Codex +1 ★ 345repo stars defend-my-project The defend-my-project Claude Code skill prepares candidates to discuss their own projects in interviews. It examines a repository, asks code-specific questions and builds a sheet of prepared answers. CX Codex +1 ★ 345repo stars oa-sim The oa-sim Claude Code skill builds a practice online assessment and grades code against hidden tests. It starts when someone asks for an OA, coding-round practice, or a company placement test. CX Codex +1 ★ 345repo stars

Project sponsors

Companies that keep this analytics open