github-glowup
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.
How do I install this agent skill?
npx skills add https://github.com/nishant-tiwari24/cracked --skill github-glowupIs this agent skill safe to install?
- Gen Agent Trust Hubpass
This skill audits GitHub profiles and proposes improvements, including secret scanning and ASCII art generation. It carries low risk from external package execution (npx) and the potential for indirect prompt injection from the repository READMEs it processes.
- Socketpass
No alerts
- Snykfail
Risk: CRITICAL · 1 issue
What does this agent skill do?
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
- Call the Skill tool with "cracked-profile" for the GitHub username. Otherwise ask, or use
gh api user --jq .login. - Gather data. Prefer
gh(works unauthenticated for public data, with lower rate limits); fall back tocurl 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 } } } }'
- Profile:
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:
-
New bio (3 options).
-
Profile README in the house layout (the same for every user; see "The house layout" in README-STYLES.md and examples/neofetch-nishant-Tiwari24.md). Exactly two code blocks, nothing else:
- 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. - 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. - Portrait block (Style E): their photo as braille ASCII on the left,
-
Pin plan: which 4–6 repos to pin and in what order, with what to unpin and why.
-
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.
-
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="…"(needsgh authwith 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.
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/nishant-tiwari24/cracked/github-glowup">View github-glowup on skillZs</a>