- name
SKILL.md
स्किल फ़ाइल पब्लिशर की रिपॉज़िटरी में ही रहती है।
कॉपी की गई कमांड टर्मिनल में पेस्ट करें। यह इस SKILL.md को उस एजेंट में इंस्टॉल करती है।
npx skills add nishant-Tiwari24/cracked --skill github-glowup -a cursor -yकॉपी की गई कमांड टर्मिनल में पेस्ट करें। यह इस SKILL.md को उस एजेंट में इंस्टॉल करती है।
npx skills add nishant-Tiwari24/cracked --skill github-glowup -a claude-code -yकॉपी की गई कमांड टर्मिनल में पेस्ट करें। यह इस SKILL.md को उस एजेंट में इंस्टॉल करती है।
npx skills add nishant-Tiwari24/cracked --skill github-glowup -a codex -yकॉपी की गई कमांड टर्मिनल में पेस्ट करें। यह इस SKILL.md को उस एजेंट में इंस्टॉल करती है।
npx skills add nishant-Tiwari24/cracked --skill github-glowup -a grok -yकॉपी किया गया संदेश Grok Bot चैट में भेजें। Bot यह SKILL.md GitHub से लाता है और उसे उन स्किल में जोड़ देता है जो आपके सभी Bot साझा करते हैं।
Install this skill: https://github.com/nishant-Tiwari24/cracked/tree/HEAD/skills/profile/github-glowupपब्लिशर से
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.
gh api user --jq .login.gh (works unauthenticated for public data, with lower rate limits); fall back to curl https://api.github.com/...:
gh api users/<u> (name, bio, company, location, blog, followers, public_repos)gh api "users/<u>/repos?per_page=100&sort=updated" (name, description, language, stars, fork, topics, homepage, pushed_at, archived)gh api graphql -f query='{ user(login:"<u>") { pinnedItems(first:6, types:REPOSITORY) { nodes { ... on Repository { name description stargazerCount primaryLanguage { name } } } } } }'gh api repos/<u>/<u>/readme --jq .content | base64 -d (it may not exist)gh api repos/<u>/<repo>/contents).gh api graphql -f query='{ user(login:"<u>") { contributionsCollection { contributionCalendar { totalContributions } } } }'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."
Score and comment on each area:
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.
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:
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.├── / └── 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.
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.
Changes are public. Ask per item: "Want me to apply this?" Then:
gh api -X PATCH user -f bio="…" (needs gh auth with the user scope).<u>/<u> repo's README via a clone, commit and push, or via the contents API.gh repo edit <u>/<repo> --description "…" --add-topic ….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.
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
---name: github-glowupdescription: Audit and upgrade a candidate's GitHub profile the way recruiters and interviewers see it, covering profile…---# skills/profile/github-glowup/SKILL.mdओवरव्यू
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.
FAQ
पब्लिशर से skills/profile/github-glowup/SKILL.md डाउनलोड करें, या पाथ कॉपी करके रिपॉज़िटरी खोलें। PlugMCP स्किल को सूचीबद्ध करता है, फ़ाइल होस्ट नहीं करता।
पब्लिशर इसे https://github.com/nishant-Tiwari24/cracked पर रखता है।
Claude, Cursor, Codex और Grok Build वह SKILL.md पढ़ सकते हैं जिसे आप पब्लिशर की रिपॉज़िटरी से जोड़ते हैं। जब आप चैट में स्किल के GitHub फ़ोल्डर का लिंक भेजते हैं, तो Grok Bot उसे इंस्टॉल कर देता है।