resume-blueprint — Claude Code skill: resume plans and setup
resume-blueprint is a Claude Code skill that builds a company-specific resume plan. It activates when someone wants to tailor a resume or get a template for a particular employer.
MIT ★ 345 updated 2026-11-14
/plugin marketplace add nishant-Tiwari24/cracked
/plugin install cracked@crackedWhat resume-blueprint does
The skill maps a candidate’s experience to a company, role, and level. It suggests a section order, picks projects and experience to feature first, identifies role keywords, and drafts bullet templates from the candidate’s real background. It also flags material to cut and writes a Markdown resume skeleton to $CRACKED_DIR/resume/<company>-blueprint.md.
It needs profile details from cracked-profile and company research from company-intel. If the agent has no Skill tool, open the relevant SKILL.md files in the cracked skills folder and follow them instead. A current resume improves the blueprint but is optional. Company claims must come from company-intel; fabricated experience or metrics are prohibited. For a general resume review, the skill points to /roast-my-resume.
What it helps with
- adapt resume sections to a target company and role
- choose which projects and experience to feature first
- identify role keywords missing from a resume
- create a Markdown resume skeleton from real experience
Example prompts for the agent
- Build a resume plan for a software engineer role at Google using my profile.
- Create an Amazon resume template from my experience and current resume.
- For Microsoft, compare my background with the role and choose which projects to lead with.
How to install resume-blueprint
1Plugin marketplace
/plugin marketplace add nishant-Tiwari24/cracked/plugin install cracked@crackedThis installs the whole cracked plugin with all its skills
2Skills CLI (Vercel)
npx skills add nishant-Tiwari24/cracked --skill resume-blueprint -a claude-code3Manually: put the files in place
~/.claude/skills/resume-blueprint/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/resume-blueprint/
1Skills CLI (Vercel)
npx skills add nishant-Tiwari24/cracked --skill resume-blueprint -a codex2Manually: put the files in place
.agents/skills/resume-blueprint/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add nishant-Tiwari24/cracked --skill resume-blueprint -a cursor2Manually: put the files in place
.cursor/skills/resume-blueprint/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install nishant-Tiwari24/cracked skills/profile/resume-blueprint2Manually: put the files in place
.github/skills/resume-blueprint/SKILL.md1Skills CLI (Vercel)
npx skills add nishant-Tiwari24/cracked --skill resume-blueprint -a gemini-cli2Platform CLI
gemini skills install https://github.com/nishant-Tiwari24/cracked --path skills/profile/resume-blueprintManually: put the files in place
.devin/skills/resume-blueprint/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about resume-blueprint
How do I install resume-blueprint in Claude Code?
Add the marketplace with /plugin marketplace add nishant-Tiwari24/cracked, then install the plugin with /plugin install cracked@cracked.
What does resume-blueprint do?
It creates a resume plan for a target company and role, with a suggested section order, keywords, bullet templates, and a fill-in Markdown skeleton based on the candidate’s real experience.
What does resume-blueprint need to work?
It uses profile details from cracked-profile and company research from company-intel. Without a Skill tool, open those skills’ SKILL.md files in the cracked folder; a current resume is optional.
Source text
SKILL.md · MIT
--- name: resume-blueprint description: Given a target company (and optionally a role), produce a company-specific resume blueprint covering what that company's screen looks for, the sections and order to use, which of the candidate's projects and experiences to lead with, must-have keywords, bullet templates tuned to the company's values, what to cut, and a fill-in-the-blanks resume skeleton built only from the candidate's real experience. Use when the user asks "what should my resume have for Google/Amazon/Microsoft/…", wants to tailor their resume to a company, or asks for a resume reference or template for a specific company. --- # Resume blueprint "What should my resume look like for <Company>?" deserves a better answer than a generic template. This skill combines what the company's screen rewards with the candidate's **real** material, and produces a resume plan they can fill in today. ## 0. Inputs 1. Call the Skill tool with "cracked-profile" (level, roles, resume path). 2. Company: from the request. If none is given, ask for it in one line. This skill only exists for company targeting; for a general review, point them to `/roast-my-resume`. 3. Role: from the request or profile. Default to the profile's first target role. 4. Call the Skill tool with "company-intel" for the company. You need the **Resume screen**, **Values** and **DSA focus** sections. 5. Read their current resume if there is one (same reading rules as `roast-my-resume`). The blueprint is far better with it, but it still works without one. ## 1. What this company's screen rewards Write 5–8 bullets, each tied to a source in the brief (the company's careers page, published values, or reported experiences), or to its archetype, labelled as such. For example: - "Impact at scale, quantified: bullets with users, latency or throughput numbers (big-tech archetype; consistent with reported screens)." - "Ownership and bias for action map to the published Leadership Principles, so frame bullets as *you* deciding and delivering." - "For new-grad SDE roles, DSA proof is a strong signal, given that their OA is reported as 2 medium–hard problems." Then list **what it doesn't care about** (cut these): e.g. a long skills dump, an objective statement, non-technical hobbies, certificates without projects. ## 2. The blueprint 1. **Section order** for this company, role and level, with a one-line reason each. 2. **Lead with**: which of their projects and experiences go first, and why, mapped to what the company values. Flag any project that hurts more than it helps here. 3. **Must-have keywords** for this role at this company, drawn from its JD language and stack. Mark each `✅ you have it` / `🟡 true but missing from resume` / `❌ gap`. Only `✅` and `🟡` go on the resume; `❌` goes to the prep list. 4. **Bullet templates in this company's language**: 4–6 templates showing how to frame *their* real experiences, e.g. `Led <project> end-to-end, choosing <tech> over <alt> to <reason>; shipped to [N] users, cutting <metric> by [X]%` (ownership and impact). 5. **Proof to add before applying**: the 1–3 highest-leverage things they could add in under 2 weeks (a contest rating, deploying an existing project, one metric they can actually measure), each tied to a cracked skill (`/make-it-hireable`, `/github-glowup`). ## 3. Resume skeleton Write `$CRACKED_DIR/resume/<company>-blueprint.md`: a full one-page resume skeleton in Markdown, in the recommended order, **pre-filled only with facts from their resume or profile**, with `[placeholders]` everywhere else, plus a `<!-- why -->` comment on each section explaining the choice. Mention that it converts cleanly to a single-column PDF (e.g. `pandoc`, or paste it into a plain single-column template). ## 4. Close - 3-line summary: the bar, their biggest gap against it, and the first fix. - Offer: `/roast-my-resume` (after they fill it in), `/jd-match` (once they have a specific JD), `/oa-sim <company>`. ## Rules - **Never fabricate.** No invented experience, metrics, or "what <Company> secretly wants". Everything is sourced, archetype-labelled, or comes from the candidate. - Company facts come only from the `company-intel` brief. If the brief says `unverified`, say the same here. --- *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