Reactive Resume Builder
reactive-resume/reactive-resume
Builds resumes as valid JSON for the open-source Reactive Resume app by interviewing you, and can track job applications through its MCP tools.
Prepares for hiring manager rounds at Staff+ (L6+) level — scope of impact, influence without authority, ambiguity navigation, mentorship, strategic thinking.
$ npx skills add curiositech/some_claude_skills --skill hiring-manager-deep-dive -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install curiositech/some_claude_skills hiring-manager-deep-dive --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/curiositech/some_claude_skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/hiring-manager-deep-dive .claude/skills/hiring-manager-deep-dive && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "hiring-manager-deep-dive" agent skill from https://github.com/curiositech/some_claude_skills/tree/main/.claude/skills/hiring-manager-deep-dive into .claude/skills/hiring-manager-deep-dive/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hiring-manager-deep-dive", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/curiositech/some_claude_skills/tree/main/.claude/skills/hiring-manager-deep-diveType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add curiositech/some_claude_skills --skill hiring-manager-deep-dive -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install curiositech/some_claude_skills hiring-manager-deep-dive --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/curiositech/some_claude_skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/hiring-manager-deep-dive .agents/skills/hiring-manager-deep-dive && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "hiring-manager-deep-dive" agent skill from https://github.com/curiositech/some_claude_skills/tree/main/.claude/skills/hiring-manager-deep-dive into .agents/skills/hiring-manager-deep-dive/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hiring-manager-deep-dive", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add curiositech/some_claude_skills --skill hiring-manager-deep-dive -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install curiositech/some_claude_skills hiring-manager-deep-dive --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/curiositech/some_claude_skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/hiring-manager-deep-dive .cursor/skills/hiring-manager-deep-dive && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "hiring-manager-deep-dive" agent skill from https://github.com/curiositech/some_claude_skills/tree/main/.claude/skills/hiring-manager-deep-dive into .cursor/skills/hiring-manager-deep-dive/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hiring-manager-deep-dive", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/curiositech/some_claude_skills.git --path .claude/skills/hiring-manager-deep-dive--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add curiositech/some_claude_skills --skill hiring-manager-deep-dive -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install curiositech/some_claude_skills hiring-manager-deep-dive --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/curiositech/some_claude_skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/hiring-manager-deep-dive .gemini/skills/hiring-manager-deep-dive && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "hiring-manager-deep-dive" agent skill from https://github.com/curiositech/some_claude_skills/tree/main/.claude/skills/hiring-manager-deep-dive into .gemini/skills/hiring-manager-deep-dive/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hiring-manager-deep-dive", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install curiositech/some_claude_skills hiring-manager-deep-diveInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add curiositech/some_claude_skills --skill hiring-manager-deep-dive -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/curiositech/some_claude_skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/hiring-manager-deep-dive .github/skills/hiring-manager-deep-dive && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "hiring-manager-deep-dive" agent skill from https://github.com/curiositech/some_claude_skills/tree/main/.claude/skills/hiring-manager-deep-dive into .github/skills/hiring-manager-deep-dive/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hiring-manager-deep-dive", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add curiositech/some_claude_skills --skill hiring-manager-deep-dive -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install curiositech/some_claude_skills hiring-manager-deep-dive --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/curiositech/some_claude_skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/hiring-manager-deep-dive .opencode/skills/hiring-manager-deep-dive && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "hiring-manager-deep-dive" agent skill from https://github.com/curiositech/some_claude_skills/tree/main/.claude/skills/hiring-manager-deep-dive into .opencode/skills/hiring-manager-deep-dive/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hiring-manager-deep-dive", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
hiring-manager-deep-divePrepares for hiring manager rounds at Staff+ (L6+) level — scope of impact, influence without authority, ambiguity navigation, mentorship, strategic thinking.
Hiring Manager Deep Dive is an agent skill from curiositech/some_claude_skills. Prepares for hiring manager rounds at Staff+ (L6+) level — scope of impact, influence without authority, ambiguity navigation, mentorship, strategic thinking. Use when practicing HM rounds or calibrating story depth for target level. Activate on "hiring manager round", "HM screen", "staff level", "scope of impact". NOT for coding interviews, system design, behavioral/values rounds, or resume writing.
Its SKILL.md is about 3.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `.claude-plugin/plugin.json`, `references/project-impact-calculator.md` and `references/staff-level-signals.md`).
It sits in Business, Finance & HR, covering Resume and CV writing. The repository describes itself as: Claude skills that make my life easier. The licence is MIT.
3 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 6713fc7. It shows what the files ask for, not the result of running them.
Pre-approves these tools, so the agent can use them without asking each time:
ReadWriteEditFrom allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md (its code samples are mermaid).
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Hiring Manager Deep Dive loads about 3.5k tokens when it runs, and up to ~12k if it reads all its reference files. Until then it costs about 107 tokens; SKILL.md has 1,755 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from curiositech/some_claude_skills at commit 6713fc7, republished under its MIT licence (© curiositech). 1,755 words, ~3,510 tokens.
.claude/skills/hiring-manager-deep-dive/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.The hiring manager round is the highest-signal evaluation of whether a candidate operates at the target level. It is less about technical depth and more about scope of impact, ability to navigate ambiguity, influence without direct authority, and strategic thinking. The HM is answering one question: "Would I trust this person to own a critical workstream independently?"
Use this skill for:
NOT for:
senior-coding-interview)ml-system-design-interview)values-behavioral-interview)cv-creator)career-biographer)Hiring managers evaluate candidates across six dimensions. Every answer you give should register on at least 2-3 of these.
| Dimension | L5 (Senior) Signal | L6+ (Staff) Signal | Weight |
|---|---|---|---|
| Technical Depth | Solves hard problems in their domain | Sets technical direction for a domain; others follow their lead | 15% |
| Scope of Impact | Delivers features for their team | Drives outcomes across teams or the org | 25% |
| Ambiguity Navigation | Executes well on defined problems | Finds the right problem to solve; creates clarity from chaos | 20% |
| Influence Without Authority | Convinces teammates | Aligns engineers, PMs, and leadership across orgs without reporting lines | 20% |
| Mentorship & Team Growth | Helps teammates with code reviews | Develops engineers' careers; shapes team culture and hiring bar | 10% |
| Strategic Thinking | Understands their team's roadmap | Connects technical decisions to business outcomes and multi-year strategy | 10% |
radar
title Staff+ Signal Radar — Target Profile
"Technical Depth" : 7
"Scope of Impact" : 9
"Ambiguity Navigation" : 8
"Influence w/o Authority" : 9
"Mentorship & Growth" : 7
"Strategic Thinking" : 8Key insight: At L5, technical depth carries you. At L6+, scope and influence carry you. Many candidates fail HM rounds by over-indexing on technical heroics and under-indexing on organizational impact.
The same question produces fundamentally different answers at different levels. Study these contrasts.
| Question | L5 Answer (Senior) | L6+ Answer (Staff) |
|---|---|---|
| "Tell me about your biggest project" | "I implemented the feature using X technology" | "I identified that our team was solving the wrong problem, proposed an alternative approach, and led the design review across 3 teams" |
| "Tell me about a performance win" | "I fixed the performance bug" | "I recognized a systemic performance issue, built a profiling framework, trained 4 engineers to use it, and reduced p99 latency by 40% across the org" |
| "How do you handle disagreements?" | "I presented data and my tech lead agreed" | "I wrote an RFC comparing 3 approaches, facilitated a design review with stakeholders from 2 orgs, incorporated feedback, and built consensus on an approach none of us had originally proposed" |
| "Tell me about mentoring" | "I helped a junior engineer debug their PR" | "I designed an onboarding curriculum, paired with 3 new hires through their first quarter, and two of them are now leading their own projects" |
| "How do you prioritize?" | "I work on what my manager says is highest priority" | "I maintain a priority framework based on business impact, technical risk, and team capacity. When our OKRs conflicted with a VP's request, I presented the tradeoff analysis and we agreed to defer one initiative" |
The pattern: L6+ answers show ownership of problem selection, cross-team coordination, multiplier effects (making others more effective), and connection to business outcomes.
The HM is evaluating: Scope + Impact + Decision Quality
Structure your answer using SCOPE-IMPACT-DECISION (SID):
references/project-impact-calculator.md)Follow-up survival guide:
The HM is evaluating: Influence + Diplomacy + Judgment
Structure using SITUATION-STAKES-STRATEGY-SYNTHESIS (4S):
Critical rule: Never position yourself as the hero who was right all along. The best answers show you changed your own mind partway through, or the final solution was better than anyone's original proposal.
The HM is evaluating: Cross-team Influence + Technical Leadership
Structure using CHALLENGE-COALITION-OUTCOME (CCO):
Signal amplifiers:
The HM is evaluating: Team Growth + Culture Building
Structure using PHILOSOPHY-PRACTICE-PROOF (3P):
Level calibration: L5 mentoring is helping with tasks. L6+ mentoring is shaping careers and building team culture.
The HM is evaluating: Strategic Thinking + Business Judgment
Structure using FRAMEWORK-FRICTION-FOLLOWTHROUGH (3F):
The HM reveals their expectations through their questions. Read these signals:
| HM Signal | What It Means | How to Adjust |
|---|---|---|
| Asks about team size and reports | Evaluating management scope | Emphasize leadership of people, not just projects |
| Asks "what did YOU specifically do?" | Testing for scope inflation | Be precise about your role vs team's role |
| Asks about failures | Testing self-awareness and growth | Own the failure fully, show systemic learning |
| Asks about 2-3 year vision | Evaluating strategic thinking | Connect your technical perspective to business trajectory |
| Asks about tradeoffs repeatedly | Testing decision-making maturity | Show you think in tradeoffs, not right/wrong |
| Keeps asking "why?" | Probing for depth vs surface knowledge | Go deeper each time; if you bottom out, say so honestly |
Novice signal: Only describes individual contributions -- "I wrote the code", "I designed the model", "I shipped the feature" -- with no mention of team, organizational, or strategic impact. Every story is about personal technical heroics.
Expert signal: Naturally weaves in scope -- "I identified the need, proposed it to leadership, assembled a cross-functional team of 6 engineers across 2 orgs, owned the technical design, coached two junior engineers through implementation, and presented results to the VP." The technical work is there but embedded in organizational context.
Detection: When asked "how did this affect the broader org?", gives vague answers like "people liked it" or pivots back to technical details. Cannot articulate the counterfactual (what would have happened without their work).
Recovery: For each story, explicitly prepare the "zoom out" layer. Ask yourself: Who besides your immediate team was affected? What organizational capability did this create? What would the next 12 months have looked like without this work?
Novice signal: Claims to have driven a project that was clearly team-driven. Uses "I" for everything. Under follow-up, cannot explain specific decisions they made vs decisions others made. The story changes or becomes vague under 2-3 levels of probing.
Expert signal: Is precise about their role -- "I was the tech lead for the ML pipeline; my peer led the serving infrastructure; our EM coordinated with the product team. My specific contributions were the architecture decision to use X over Y, the data pipeline design, and mentoring two engineers on the team." Credits others naturally without diminishing their own contribution.
Detection: Ask "who else was involved and what did they own?" -- a scope inflator either cannot answer or gives generic responses. Ask the same question from a different angle later; the story should be consistent.
Recovery: Map every story to a RACI-like structure before the interview. Know exactly what you were Responsible for, what you were Accountable for, and what you Consulted or Informed on. Precision builds trust.
Novice signal: Can describe what they built in exhaustive technical detail but not WHY it mattered to the business. Cannot answer "what would have happened if you hadn't done this?" or "what's the 2-year vision for this area?" Treats strategy questions as irrelevant to their engineering role.
Expert signal: Connects technical decisions to business outcomes, competitive landscape, and long-term platform strategy. "We chose to build the inference pipeline in-house rather than using a vendor because our model iteration speed is a competitive advantage, and vendor lock-in would have cost us 2-3 weeks per model update cycle. The 2-year vision is a self-serve platform where researchers can deploy models without infra involvement."
Detection: Ask "why did this project matter more than other things you could have worked on?" A strategy vacuum gives answers like "my manager asked me to" or "it was the next thing on the roadmap."
Recovery: For every project story, prepare answers to: (1) Why this project over alternatives? (2) What was the business case? (3) What would the world look like in 2 years if this succeeds? (4) What are the risks if it fails?
references/staff-level-signals.md -- Detailed breakdown of L6/Staff+ expectations by dimension, with level calibration examples and company-specific patterns for Anthropic, Google, Meta, and OpenAIreferences/project-impact-calculator.md -- Framework for quantifying and articulating project impact, with worked examples for 4 ML project types and audience-specific framing techniques© curiositech, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 3 other files (references) in .claude/skills/hiring-manager-deep-dive of curiositech/some_claude_skills.
Open the folder on GitHubat commit 6713fc7
Hiring Manager Deep Dive next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Hiring Manager Deep Dive this skillcuriositech/some_claude_skills | 243 | — | ~3.5k | Automated safety check: Pass | MIT | |
| Reactive Resume Builderreactive-resume/reactive-resume | 44k | — | ~1.5k | Automated safety check: Pass | MIT | |
| Career-Ops Job Search Centercareer-ops-hq/career-ops | 74k | — | ~3.6k | Automated safety check: Pass | MIT | |
| Internship Project Preparation ToolLiuMengxuan04/shushu-internship-tool | 2.1k | — | ~2.3k | Automated safety check: Pass | Custom licence | |
| Resume Tailoringvarunr89/resume-tailoring-skill | 768 | 1 repos | ~8.9k | Automated safety check: Pass | MIT | |
| Good StoryRimagination/good-story | 134 | 1 repos | ~2.9k | Automated safety check: Pass | MIT |
reactive-resume/reactive-resume
Builds resumes as valid JSON for the open-source Reactive Resume app by interviewing you, and can track job applications through its MCP tools.
career-ops-hq/career-ops
Routes job-search requests to modes for evaluating offers, scanning portals, generating tailored CVs, tracking applications and drafting outreach, starting from a pasted job URL or description.
LiuMengxuan04/shushu-internship-tool
Turns a target internship job description into a resume-ready, interview-ready project by finding and auditing GitHub projects and drafting resume bullets and interview Q&A.
varunr89/resume-tailoring-skill
A skill your agent uses when creating tailored resumes for job applications - researches company/role, creates optimized templates, conducts branching experience discovery to surface undocumented…
Rimagination/good-story
A skill your agent uses when the user asks to find, sharpen, evaluate, rewrite, or explain the story in scientific or scholarly materials across disciplines, including manuscripts, grants, paper…
MadsLorentzen/ai-job-search
Evaluates job postings against your profile, then tailors a LaTeX CV and cover letter and prepares interview answers for the roles you pursue.
curiositech/some_claude_skills
Detect crisis signals in user content using NLP, mental health sentiment analysis, and safe intervention protocols.
curiositech/some_claude_skills
End-to-end form handling with react-hook-form, Zod schemas, validation patterns, error messaging, field arrays, and multi-step wizards.
curiositech/some_claude_skills
Build production CI/CD pipelines with GitHub Actions. An agent skill from curiositech/some_claude_skills.
curiositech/some_claude_skills
Expert in background job processing with Bull/BullMQ (Redis), Celery, and cloud queues.
curiositech/some_claude_skills
Strategic analyst that maps competitive landscapes, identifies white space opportunities, and provides positioning recommendations.
curiositech/some_claude_skills
Build production computer vision pipelines for object detection, tracking, and video analysis.
Categories
Prepares for hiring manager rounds at Staff+ (L6+) level — scope of impact, influence without authority, ambiguity navigation, mentorship, strategic thinking. Hiring Manager Deep Dive is an agent skill from curiositech/some_claude_skills. Prepares for hiring manager rounds at Staff+ (L6+) level — scope of impact, influence without authority, ambiguity navigation, mentorship, strategic thinking.
Hiring Manager Deep Dive fits situations like: practicing HM rounds; calibrating story depth for target level.
Run `npx skills add curiositech/some_claude_skills --skill hiring-manager-deep-dive -a claude-code`. Or copy the skill folder (.claude/skills/hiring-manager-deep-dive in curiositech/some_claude_skills) into .claude/skills/hiring-manager-deep-dive in your project. Claude Code loads it when a task matches its description.
Run `npx skills add curiositech/some_claude_skills --skill hiring-manager-deep-dive -a codex`. Or copy the skill folder (.claude/skills/hiring-manager-deep-dive in curiositech/some_claude_skills) into .agents/skills/hiring-manager-deep-dive in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add curiositech/some_claude_skills --skill hiring-manager-deep-dive -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/hiring-manager-deep-dive, .gemini/skills/hiring-manager-deep-dive, .github/skills/hiring-manager-deep-dive and .opencode/skills/hiring-manager-deep-dive in your project.
SKILL.md names no scripts, command-line tools or credentials: Hiring Manager Deep Dive is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Write, Edit.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Hiring Manager Deep Dive is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 3.5k tokens (SKILL.md is roughly 14k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 8k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Hiring Manager Deep Dive: Reactive Resume Builder (reactive-resume/reactive-resume, 44k stars), Career-Ops Job Search Center (career-ops-hq/career-ops, 74k stars), Internship Project Preparation Tool (LiuMengxuan04/shushu-internship-tool, 2.1k stars) and Resume Tailoring (varunr89/resume-tailoring-skill, 768 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
curiositech (a GitHub organization) maintains it in curiositech/some_claude_skills, which has 243 GitHub stars. The repository holds 95 skills in this directory. The repository was last updated on September 6, 2026.
Source: curiositech/some_claude_skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.