Career-Ops Job Search Center
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.
Walk into an exit interview knowing what it's for, what to say, and what to keep — honest-but-strategic answers that protect references and leave the door open.
Install Exit Interview Strategy
$ npx skills add mohitagw15856/pm-claude-skills --skill exit-interview-strategy -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mohitagw15856/pm-claude-skills exit-interview-strategy --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/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/exit-interview-strategy .claude/skills/exit-interview-strategy && 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 "exit-interview-strategy" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/exit-interview-strategy into .claude/skills/exit-interview-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "exit-interview-strategy", 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/mohitagw15856/pm-claude-skills/tree/main/skills/exit-interview-strategyType 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 mohitagw15856/pm-claude-skills --skill exit-interview-strategy -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mohitagw15856/pm-claude-skills exit-interview-strategy --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/exit-interview-strategy .agents/skills/exit-interview-strategy && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "exit-interview-strategy" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/exit-interview-strategy into .agents/skills/exit-interview-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "exit-interview-strategy", 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 mohitagw15856/pm-claude-skills --skill exit-interview-strategy -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mohitagw15856/pm-claude-skills exit-interview-strategy --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/exit-interview-strategy .cursor/skills/exit-interview-strategy && 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 "exit-interview-strategy" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/exit-interview-strategy into .cursor/skills/exit-interview-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "exit-interview-strategy", 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/mohitagw15856/pm-claude-skills.git --path skills/exit-interview-strategy--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 mohitagw15856/pm-claude-skills --skill exit-interview-strategy -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mohitagw15856/pm-claude-skills exit-interview-strategy --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/exit-interview-strategy .gemini/skills/exit-interview-strategy && 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 "exit-interview-strategy" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/exit-interview-strategy into .gemini/skills/exit-interview-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "exit-interview-strategy", 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 mohitagw15856/pm-claude-skills exit-interview-strategyInstalls 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 mohitagw15856/pm-claude-skills --skill exit-interview-strategy -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/exit-interview-strategy .github/skills/exit-interview-strategy && 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 "exit-interview-strategy" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/exit-interview-strategy into .github/skills/exit-interview-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "exit-interview-strategy", 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 mohitagw15856/pm-claude-skills --skill exit-interview-strategy -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mohitagw15856/pm-claude-skills exit-interview-strategy --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/exit-interview-strategy .opencode/skills/exit-interview-strategy && 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 "exit-interview-strategy" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/exit-interview-strategy into .opencode/skills/exit-interview-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "exit-interview-strategy", 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.
Facts
- Skill name
exit-interview-strategy- GitHub stars
- 1.4k
- Token cost
- ~1.4k tokens
- SKILL.md length
- 711 words
- Files
- 1
- Skills in repo
- 1,348
- Repo updated
- First seen
- Licence
- MIT
At a glance
Walk into an exit interview knowing what it's for, what to say, and what to keep — honest-but-strategic answers that protect references and leave the door open.
- Works in 5 steps: Know what it's for (them, not you): exit… → Say — pattern-level, futureless… → Soften — true things with named humans… → …
- Asked what do I say in my exit interview
- SKILL.md covers What This Skill Produces, Required Inputs, Framework: The Sorting Rules and Output Format, plus 7 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Exit Interview Strategy is an agent skill from mohitagw15856/pm-claude-skills. Walk into an exit interview knowing what it's for, what to say, and what to keep — honest-but-strategic answers that protect references and leave the door open. Use when asked what do I say in my exit interview, should I be honest in my exit interview, prep me for my exit interview, or is the exit interview confidential. Produces the goals-and-risks brief, prepared answers for the standard questions, the say/soften/skip sorting of your real feedback, and the scripts for the questions that are traps.
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Business, Finance & HR, covering Interview preparation. The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.
When your agent uses it
- Asked what do I say in my exit interview
- Should I be honest in my exit interview
- Prep me for my exit interview
- Is the exit interview confidential
Example prompts
- “/exit-interview-strategy”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Know what it's for (them, not you): exit interviews exist to detect legal risk, spot patterns, and close the file. Change rarely follows…
- Say — pattern-level, futureless feedback: things that help the org, cost you nothing, and discuss systems not people ("the on-call load in…
- Soften — true things with named humans attached: convert person-feedback to process-feedback. "I'd suggest clearer promotion criteria"…
- Skip — anything venty, unverifiable, or already-decided: grievances that fix nothing and mark the file. The test: would I want this read…
- Legal-adjacent issues don't go here: harassment, discrimination, retaliation, wage issues — raising them casually in an exit interview is…
What it can do on your machine
Read from SKILL.md and the folder at commit 1cbf1f0. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Exit Interview Strategy loads about 1.4k tokens when it runs. Until then it costs about 132 tokens; SKILL.md has 711 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.
Safety
Auto-check passed
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.
SKILL.md
The full file from mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 711 words, ~1,387 tokens.
Download SKILL.mdSave it as
.claude/skills/exit-interview-strategy/SKILL.md (or your agent's skills folder).- name
- exit-interview-strategy
- description
- Walk into an exit interview knowing what it's for, what to say, and what to keep — honest-but-strategic answers that protect references and leave the door open. Use when asked what do I say in my exit interview, should I be honest in my exit interview, prep me for my exit interview, or is the exit interview confidential. Produces the goals-and-risks brief, prepared answers for the standard questions, the say/soften/skip sorting of your real feedback, and the scripts for the questions that are traps.
Exit Interview Strategy Skill
The exit interview is a meeting where you can win nothing and lose things you'll want later — references, rehire eligibility, relationships that follow you between companies. It is not therapy, not a performance review of your manager, and rarely as confidential as presented: notes get filed, summarized, and sometimes shared with the very people discussed. This skill preps it like the low-stakes-for-them, real-stakes-for-you meeting it is: decide the two things worth saying, sort the rest into soften or skip, and exit the exit gracefully.
What This Skill Produces
- The brief — what this interview can and can't do for you, and your 1–2 chosen messages
- Prepared answers — the standard questions (why leaving, what would you change, manager feedback) answered in advance, calm and final
- The say / soften / skip sort — their real feedback triaged by usefulness-to-them vs. risk-to-you
- Trap scripts — word-for-word responses for the destination question, the "is there anything that would keep you" re-recruit, and the name-names invitation
Required Inputs
Ask for these if not provided:
- The real feedback — everything they wish they could say, unfiltered; the sort works on the honest list
- The exit temperature — amicable, burned, or complicated; and whether anything legal-adjacent is in the mix (harassment, retaliation, unpaid wages — which changes the venue entirely, see framework)
- What they want to protect — references from whom, rehire eligibility, relationships with specific people
- Who's conducting it — HR, manager, skip-level; the same answer lands differently per audience
Framework: The Sorting Rules
- Know what it's for (them, not you): exit interviews exist to detect legal risk, spot patterns, and close the file. Change rarely follows one interview. Calibrate effort accordingly — your leverage for changing things ended when you resigned.
- Say — pattern-level, futureless feedback: things that help the org, cost you nothing, and discuss systems not people ("the on-call load in that team is a retention risk" not "my manager ignored burnout"). Two items maximum; more dilutes both.
- Soften — true things with named humans attached: convert person-feedback to process-feedback. "I'd suggest clearer promotion criteria" carries the content of "my manager promoted his friends" without the blast radius. The person-version travels; the process-version works.
- Skip — anything venty, unverifiable, or already-decided: grievances that fix nothing and mark the file. The test: would I want this read back to me by their lawyer, or repeated to the named person? Both happen.
- Legal-adjacent issues don't go here: harassment, discrimination, retaliation, wage issues — raising them casually in an exit interview is the worst of both worlds (on record enough to complicate, informal enough to dismiss). Those go through counsel or a formal complaint, chosen deliberately, not slipped into a goodbye chat.
Show full SKILL.md (270 more words)Show less
Output Format
Exit Interview Prep: [company, conducted by]
The Brief
[What this meeting can/can't do · your 1–2 chosen messages · what you're protecting]
Prepared Answers
"Why are you leaving?" → [forward-facing, pull-not-push: the opportunity, not the escape] "What would you change?" → [your say-list items, pattern-level] "How was your manager?" → [the softened version, rehearsed]
The Sort
| Real feedback | Say / Soften / Skip | The version that gets said (if any) |
|---|
Trap Scripts
"Where are you going?" → [share or deflect by choice — "I'd rather share once I've started" is complete] "What would it take to keep you?" → [gracious close, not a negotiation re-open — that ship sailed with the counteroffer decision] "You can be honest — who specifically?" → [the names-stay-out line]
Quality Checks
- Say-list is ≤2 items, both pattern-level and person-free
- Every softened item preserves the useful content minus the names
- Legal-adjacent issues are routed out of the interview, explicitly
- Answers are final-sounding — nothing that reopens negotiation or invites follow-up meetings
- The prep protects the named list (references, rehire flag, relationships)
Anti-Patterns
- Do not treat "this is confidential" as load-bearing — prep as if notes reach the people discussed, because sometimes they do
- Do not unload — the relief is real and expensive; venting buys nothing and marks the file
- Do not name names attached to negative feedback, even when invited to
- Do not litigate your performance reviews or comp history — closed chapters
- Do not skip the prep because "it's just a formality" — unprepared honesty is how references quietly die
Example Trigger Phrases
- "What do I say in my exit interview?"
- "Should I be honest in my exit interview?"
- "Prep me for my exit interview."
- "Is the exit interview confidential?"
© mohitagw15856, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/exit-interview-strategy of mohitagw15856/pm-claude-skills.
Open the folder on GitHubat commit 1cbf1f0
Compare with similar skills
Exit Interview Strategy 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 |
|---|---|---|---|---|---|---|
| Exit Interview Strategy this skillmohitagw15856/pm-claude-skills | 1.4k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Career-Ops Job Search Centercareer-ops-hq/career-ops | 74k | — | ~3.6k | Automated safety check: Pass | MIT | |
| Interview Prepreactive-resume/reactive-resume | 44k | — | ~10k | Automated safety check: Pass | MIT | |
| Internship Project Preparation ToolLiuMengxuan04/shushu-internship-tool | 2.1k | — | ~2.3k | Automated safety check: Pass | Custom licence | |
| Job Application Managerreactive-resume/reactive-resume | 44k | — | ~13k | Automated safety check: Pass | MIT | |
| Mock Interviewreactive-resume/reactive-resume | 44k | — | ~11k | Automated safety check: Pass | MIT |
Similar skills
Interview Prep
reactive-resume/reactive-resume
Prepares the user for a specific interview from their real experience.
Internship Project Preparation Tool
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.
Job Application Manager
reactive-resume/reactive-resume
Runs the job-search pipeline. An agent skill from reactive-resume/reactive-resume.
Mock Interview
reactive-resume/reactive-resume
Runs a mock interview for a specific job description. An agent skill from reactive-resume/reactive-resume.
Interview Coach
noamseg/interview-coach-skill
High-rigor interview coaching skill for job seekers. An agent skill from noamseg/interview-coach-skill.
More from mohitagw15856/pm-claude-skills
All 1,348 skills in this repoCar Tco
mohitagw15856/pm-claude-skills
Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly…
Cs Health Scorecard
mohitagw15856/pm-claude-skills
Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.
Exit Waterfall
mohitagw15856/pm-claude-skills
Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.
Feature Prioritisation
mohitagw15856/pm-claude-skills
Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.
Fire Number
mohitagw15856/pm-claude-skills
Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer.
Freelance Rate
mohitagw15856/pm-claude-skills
Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.
Related
Categories
Questions about Exit Interview Strategy
What does Exit Interview Strategy do?
Walk into an exit interview knowing what it's for, what to say, and what to keep — honest-but-strategic answers that protect references and leave the door open. Exit Interview Strategy is an agent skill from mohitagw15856/pm-claude-skills. Walk into an exit interview knowing what it's for, what to say, and what to keep — honest-but-strategic answers that protect references and leave the door open.
When should I use Exit Interview Strategy?
Exit Interview Strategy fits situations like: asked what do I say in my exit interview; should I be honest in my exit interview; prep me for my exit interview; is the exit interview confidential.
How do I install Exit Interview Strategy in Claude Code?
Run `npx skills add mohitagw15856/pm-claude-skills --skill exit-interview-strategy -a claude-code`. Or copy the skill folder (skills/exit-interview-strategy in mohitagw15856/pm-claude-skills) into .claude/skills/exit-interview-strategy in your project. Claude Code loads it when a task matches its description.
How do I install Exit Interview Strategy in Codex?
Run `npx skills add mohitagw15856/pm-claude-skills --skill exit-interview-strategy -a codex`. Or copy the skill folder (skills/exit-interview-strategy in mohitagw15856/pm-claude-skills) into .agents/skills/exit-interview-strategy in your project. Codex loads it when a task matches its description.
Can I use Exit Interview Strategy in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mohitagw15856/pm-claude-skills --skill exit-interview-strategy -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/exit-interview-strategy, .gemini/skills/exit-interview-strategy, .github/skills/exit-interview-strategy and .opencode/skills/exit-interview-strategy in your project.
What does Exit Interview Strategy need to run?
SKILL.md names no scripts, command-line tools or credentials: Exit Interview Strategy is instructions for the agent only.
Does Exit Interview Strategy access the network?
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.
Is Exit Interview Strategy safe to install?
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.
What licence does Exit Interview Strategy use?
Exit Interview Strategy is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Exit Interview Strategy use?
About 1.4k tokens (SKILL.md is roughly 5.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Exit Interview Strategy?
Skills that share tags, products or a category with Exit Interview Strategy: Career-Ops Job Search Center (career-ops-hq/career-ops, 74k stars), Interview Prep (reactive-resume/reactive-resume, 44k stars), Internship Project Preparation Tool (LiuMengxuan04/shushu-internship-tool, 2.1k stars) and Job Application Manager (reactive-resume/reactive-resume, 44k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Exit Interview Strategy?
mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,434 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 9, 2026.
Source: mohitagw15856/pm-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.