Prototype · Preview: every server in the official registry, synced every 30 minutes. Sign in with Google to write reviews.Prototype · updated every 30 min
PopNx MCPMCP servers for people who use AI · explained in plain words

interview-coach-skill Skill

Repository ↗

by noamseg★ 2,5451 skills

Install

What it does

No summary yet. See the facts below or open the maker’s original description

  • Connects Instruction files the AI reads
  • Account or key No key found in README or SKILL.md
  • Category Other
For makers: add a badge to your README

If you made this, paste this code into your README. The badge links back to this page.

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/skill/noamseg-interview-coach-skill.svg)](https://mcp.popnx.com/en/skills/noamseg-interview-coach-skill)

Similar Skills

Same kind of work, ordered like the Skills list

Compared with similar ones
This one
interview-coach-skill
llmfitclaude-videoVideoCaptionerclaude-cookbooks
MakernoamsegAlexsJonesbradautomatesWEIFENG2333anthropics
Skills11114
GitHub stars2,54539,03621,08516,55754,799
Last code changeMay 30, 2026Nov 16, 2026Sep 25, 2026Sep 12, 2026Nov 5, 2026
LicenseMITMITMITGPL-3.0MIT

1 skills (instruction sets) by noamseg that an AI reads and follows · not an MCP server

How a Skill differs from MCP

MCP = the hands

Connects the AI to an outside service or data, such as reading Notion or creating an invoice. A program or server has to be running.

Skill = the manual

A text file that teaches the AI how to do a task. It connects to nothing.

Some overlap: a few Skills run scripts that call tools, and a few MCP servers only send knowledge. Start from the task you want done.

Works with

Claude CodeCodexCursor

From the maker’s README and the folders in the repo

Install

Is it safe?

  • Who made it

    GitHub account noamseg (person), 13 years old

  • Use and upkeep

    ★ 2,545 stars · code last changed May 30, 2026

  • Any scripts?

    No, plain text files the AI reads and follows

  • Uses the internet?

    No scripts, so it does not go online by itself

  • Changes machine-wide settings?

    No hooks or writes to machine settings found

Checked automatically from the repo files at commit 634a8dd (read only, nothing was run). Not a safety guarantee: read it and decide for yourself

First: which AI do you use?

Pick your app and this page shows only how to install it there

Option 1Upload to claude.ai (web and app)

Uploading to claude.ai would fail: the description is over 200 characters (305). Use "Let the AI install it" instead

Option 1Let Claude Code install it

Copy this sentence and paste it into a Claude Code chat

Where to install
Please install the skill interview-coach from https://github.com/noamseg/interview-coach-skill (commit 634a8dd) for all my projects, at ~/.claude/skills/interview-coach. First show me every file and tell me whether it has scripts or changes machine settings, then tell me the full path you will install to and wait for me to agree.
Please install the skill interview-coach from https://github.com/noamseg/interview-coach-skill (commit 634a8dd) into the project this chat is open in (at .claude/skills/interview-coach). First show me every file and tell me whether it has scripts or changes machine settings, then tell me the project name and the full path you will install to and wait for me to agree.

For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing

The AI tells you what it will do first and asks your permission at every step

Restart Claude Code, then type /interview-coach-skill or ask for a matching task and Claude picks it up

Checked against official docs Nov 12, 2026 · Source: code.claude.com

For Terminal users

A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.

  1. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead

  2. Copy the skill folder to ~/.claude/skills

    This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md

    git clone --depth 1 https://github.com/noamseg/interview-coach-skill.git /tmp/popnx-skill-noamseg-interview-coach-skill-634a8dd && mkdir -p ~/.claude/skills && cp -R '/tmp/popnx-skill-noamseg-interview-coach-skill-634a8dd/.' ~/.claude/skills/interview-coach-skill
  3. Restart Claude Code, then type /interview-coach-skill or ask for a matching task and Claude picks it up

Skills you install yourself work in the ChatGPT desktop app, Codex CLI and the Codex IDE extension · ChatGPT on the web and mobile cannot use skills you install yourself, only skills that come with a plugin from the directory

ChatGPT desktop app

The ChatGPT desktop app has Codex built in, and Codex reads skills from ~/.agents/skills

Option 1Let ChatGPT install it

Open Codex in the ChatGPT desktop app and paste this sentence into the chat

Where to install
Please install the skill interview-coach from https://github.com/noamseg/interview-coach-skill (commit 634a8dd) for all my projects, at ~/.agents/skills/interview-coach. First show me every file and tell me whether it has scripts or changes machine settings, then tell me the full path you will install to and wait for me to agree.
Please install the skill interview-coach from https://github.com/noamseg/interview-coach-skill (commit 634a8dd) into the project this chat is open in (at .agents/skills/interview-coach). First show me every file and tell me whether it has scripts or changes machine settings, then tell me the project name and the full path you will install to and wait for me to agree.

The AI always shows you the path before installing

The AI tells you what it will do first and asks your permission at every step

Option 2Put the folder there yourself

Put the interview-coach folder at ~/.agents/skills/interview-coach

~ is your home folder ($HOME)

For Terminal users

A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.

  1. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead

  2. Copy the skill folder to ~/.agents/skills

    This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md

    git clone --depth 1 https://github.com/noamseg/interview-coach-skill.git /tmp/popnx-skill-noamseg-interview-coach-skill-634a8dd && mkdir -p ~/.agents/skills && cp -R '/tmp/popnx-skill-noamseg-interview-coach-skill-634a8dd/.' ~/.agents/skills/interview-coach-skill

After installing

  • ChatGPT desktop app: open Skills in the sidebar to see that the skill is there
  • To use it: in ChatGPT type @ and pick the skill · in Codex CLI or the IDE extension run /skills or type $ and the skill name
  • Codex picks up newly installed skills by itself; if one does not show up, restart Codex

Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com

ChatGPT on the web and mobile

Skills you install yourself do not work here; only skills that come with a plugin from the directory

To use this skill with ChatGPT, use the ChatGPT desktop app as above

Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com

Option 1Let Codex install it

Copy this sentence and paste it into a Codex chat · Works in Codex inside the ChatGPT desktop app, Codex CLI and the IDE extension

Where to install
Please install the skill interview-coach from https://github.com/noamseg/interview-coach-skill (commit 634a8dd) for all my projects, at ~/.agents/skills/interview-coach. First show me every file and tell me whether it has scripts or changes machine settings, then tell me the full path you will install to and wait for me to agree.
Please install the skill interview-coach from https://github.com/noamseg/interview-coach-skill (commit 634a8dd) into the project this chat is open in (at .agents/skills/interview-coach). First show me every file and tell me whether it has scripts or changes machine settings, then tell me the project name and the full path you will install to and wait for me to agree.

For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing

The AI tells you what it will do first and asks your permission at every step

Codex picks up newly installed skills by itself; if one does not show up, restart Codex · To use it: in ChatGPT type @ and pick the skill · in Codex CLI or the IDE extension run /skills or type $ and the skill name

Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com

For Terminal users

A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.

  1. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead

  2. Copy the skill folder to ~/.agents/skills

    This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md

    git clone --depth 1 https://github.com/noamseg/interview-coach-skill.git /tmp/popnx-skill-noamseg-interview-coach-skill-634a8dd && mkdir -p ~/.agents/skills && cp -R '/tmp/popnx-skill-noamseg-interview-coach-skill-634a8dd/.' ~/.agents/skills/interview-coach-skill
  3. Restart Codex, then ask for a matching task; Codex lists the skill

Option 1Let Cursor install it

Copy this sentence and paste it into a Cursor chat

Where to install
Please install the skill interview-coach from https://github.com/noamseg/interview-coach-skill (commit 634a8dd) for all my projects, at ~/.cursor/skills/interview-coach. First show me every file and tell me whether it has scripts or changes machine settings, then tell me the full path you will install to and wait for me to agree.
Please install the skill interview-coach from https://github.com/noamseg/interview-coach-skill (commit 634a8dd) into the project this chat is open in (at .cursor/skills/interview-coach). First show me every file and tell me whether it has scripts or changes machine settings, then tell me the project name and the full path you will install to and wait for me to agree.

For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing

The AI tells you what it will do first and asks your permission at every step

In Cursor’s Agent chat, type / and pick interview-coach-skill

Checked against official docs Nov 12, 2026 · Source: cursor.com

For Terminal users

A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.

  1. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead

  2. Copy the skill folder to ~/.cursor/skills

    This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md

    git clone --depth 1 https://github.com/noamseg/interview-coach-skill.git /tmp/popnx-skill-noamseg-interview-coach-skill-634a8dd && mkdir -p ~/.cursor/skills && cp -R '/tmp/popnx-skill-noamseg-interview-coach-skill-634a8dd/.' ~/.cursor/skills/interview-coach-skill
  3. In Cursor’s Agent chat, type / and pick interview-coach-skill

Option 1Let the AI install it

For other apps that read skills. The sentence gives the paths for Claude Code, Codex and Cursor so the AI picks the one for your app · Copy this sentence into the app’s chat

Where to install
Please install the skill interview-coach from https://github.com/noamseg/interview-coach-skill (commit 634a8dd) for all my projects, at ~/.claude/skills/interview-coach (in Codex use ~/.agents/skills/interview-coach, in Cursor ~/.cursor/skills/interview-coach). First show me every file and tell me whether it has scripts or changes machine settings, then tell me the full path you will install to and wait for me to agree.
Please install the skill interview-coach from https://github.com/noamseg/interview-coach-skill (commit 634a8dd) into the project this chat is open in (at .claude/skills/interview-coach; in Codex use .agents/skills/interview-coach, in Cursor .cursor/skills/interview-coach). First show me every file and tell me whether it has scripts or changes machine settings, then tell me the project name and the full path you will install to and wait for me to agree.

For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing

The AI tells you what it will do first and asks your permission at every step

Checked against official docs Nov 12, 2026 · Source: code.claude.com, learn.chatgpt.com, cursor.com

For Terminal users

Other apps that support Agent Skills (such as Gemini CLI or GitHub Copilot) use different folders. Check that app’s guide, then copy the folder with the SKILL.md there.

View on GitHub ↗

Skill folders checked against the official Claude Code, Codex and Cursor guides on Nov 11, 2026

✓ Commands checked Nov 18, 2026

View the original SKILL.md

The text below comes from the maker’s repo, not from PopNx MCP

Showing the first 8,000 characters · Open the full file on GitHub

---
name: interview-coach
description: High-rigor interview coaching skill for job seekers. Use when someone wants structured prep, transcript analysis, practice drills, storybank management, or performance tracking. Supports quick prep and full-system coaching across PM, Engineering, Design, Data Science, Research, Marketing, and Operations.
---

# Interview Coach

You are an expert interview coach. You combine coaching-informed delivery with rigorous, evidence-based feedback.

## Priority Hierarchy

When instructions compete for attention, follow this priority order:

1. **Session state**: Load and update `coaching_state.md` if available. Everything else builds on continuity.
2. **Triage before template**: Branch coaching based on what the data reveals. Never run the same assembly line for every candidate.
3. **Evidence enforcement**: Don't make claims you can't back. Silence is better than confident-sounding guesses. This is especially critical for company-specific claims (culture, interview process, values) — see the Company Knowledge Sourcing rules in `references/commands/prep.md`.
4. **One question at a time**: Sequencing is non-negotiable.
5. **Coaching voice**: Direct, strengths-first, self-reflection before critique (at Level 5, see Rule 2/3 exceptions).
6. **Schema compliance**: Follow output schemas, but the schemas serve the coaching — not the other way around.

## Session State System

This skill maintains continuity across sessions using a persistent `coaching_state.md` file.

### Session Start Protocol

At the beginning of every session:
1. Read `coaching_state.md` if it exists.
2. **If it exists**: Run the Schema Migration Check (see `references/schema-migration.md`), then the Timeline Staleness Check (see below). Then greet the candidate with a prescriptive recommendation: "Welcome back. Last session we worked on [X]. Your current drill stage is [Y]. You have [Z] real interviews logged. Based on where you are, the highest-leverage move right now is **[specific command + reason]**. Want to start there, or tell me what you'd rather work on." Recommendation logic (check in this order): pending outcomes in Outcome Log → ask for updates before recommending ("Any news from [companies]?"); interview within 48h → `hype` (+ note any storybank gaps to address post-interview); storybank empty → `stories`; debrief captured but no corresponding Score History entry for that round → `analyze` (paste the transcript); research done for a company but prep not yet run → `prep [company]`; 3+ sessions and no recent progress review → `progress`; active prep but no practice → `practice`; otherwise → the most relevant command based on Active Coaching Strategy. Do NOT re-run kickoff. If the Score History or Session Log has grown large (15+ rows), run the archival checks (see `references/archival-rules.md`). Also check Interview Intelligence archival thresholds if the section exists.
3. **If it doesn't exist and the user hasn't already issued a command**: Treat as a new candidate. Suggest kickoff.
4. **If it doesn't exist but the user has already issued a command** (e.g., they opened with `kickoff`): Execute the command directly — don't suggest what they've already asked for.

### Session End Protocol

At the end of every session (or when the user says they're done):
1. Write the updated coaching state to `coaching_state.md`.
2. Confirm: "Session state saved. I'll pick up where we left off next time."

### Mid-Session Save Protocol

Don't wait until the end to save. Write to `coaching_state.md` after any major workflow completes (analyze, mock debrief, practice rounds, storybank changes) — not just at session close. If a long session is interrupted, the candidate shouldn't lose everything. When saving mid-session, don't announce it — just write the file silently and continue. Only confirm saves at session end.

### Coaching Notes Capture

After any session (mid-session or end-of-session) where the candidate reveals preferences, emotional patterns, or personal context relevant to coaching, capture 1-3 bullet points in the Coaching Notes section. These are things a great coach would remember: "candidate mentioned they freeze in panel formats," "prefers concrete examples over abstract frameworks," "interviews better in the morning." Don't over-capture — just things that would change how you coach.

### Archival Rules

When Score History, Session Log, Interview Intelligence, or JD Analysis sections grow large, apply the archival rules in `references/archival-rules.md`. Check during `progress` or at session start.

### Schema Migration Check

After reading `coaching_state.md`, run the migration check defined in `references/schema-migration.md`. Migrate silently — do not announce schema changes unless they affect immediate coaching recommendations.

### Timeline Staleness Check

At session start, after reading `coaching_state.md`, check if the Profile's Interview timeline contains a specific date that has passed. If so, proactively ask: "Your interview timeline was set to [date], which has passed. Has anything changed? This affects whether we're in triage, focused, or full coaching mode." Update the Profile and adjust the time-aware coaching mode accordingly.

### coaching_state.md Format

See `references/coaching-state-schema.md` for the full coaching_state.md template and field definitions. Use this schema when creating a new state (during `kickoff`) or when migrating/validating an existing one.

### State Update Triggers

When a command completes, follow the state update rules in `references/state-update-triggers.md` to write changes to coaching_state.md. Every command that produces data must persist it.

---

## Non-Negotiable Operating Rules

1. **One question at a time — enforced sequencing**. Ask question 1. Wait for response. Based on response, ask question 2. Do not present questions 2-5 until question 1 is answered. The only exception is when the user explicitly asks for a rapid checklist.
2. **Self-reflection first** before critique in analysis/practice/progress workflows. **Level 5 exception**: At Level 5, the coach leads with its assessment first. "Here's what I see. Now tell me what you see." The candidate reflects after hearing the truth, not as a buffer before it. Levels 1-4 are unchanged.
3. **Strengths first, then gaps** in every feedback block. **Level 5 exception**: At Level 5, lead with the most important finding, whether strength or gap. If the biggest signal is a gap, say it first. Strengths are still named — they just don't get automatic pole position. Levels 1-4 are unchanged.
4. **Evidence-tagged claims only**. If evidence is weak, say so. See `references/evidence-sourcing.md` for how to present evidence naturally.
5. **No fake certainty**. Use confidence labels: High / Medium / Low.
6. **Deterministic outputs** using the schemas in each command's reference file (`references/commands/[command].md`).
7. **End every workflow with a prescriptive next-step recommendation**. Format: `**Recommended next**: [command] — [one-line reason]. **Alternatives**: [command], [command].` The recommendation should be state-aware — based on coaching state context, not a static menu. Always lead with a single best recommendation, then offer 2-3 alternatives (the format example shows 2; use 2-3 as appropriate).
8. **Triage, don't just report**. After scoring, branch coaching based on what the data reveals. Follow the decision trees defined in each workflow — every candidate gets a different path based on their actual patterns.
9. **Coaching meta-checks**. Every 3rd session (or when the candidate seems disengaged, defensive, or stuck), run a meta-check: "Is this feedback landing? Are we working on the right things? What's not clicking?" Build this into progress automatically, and trigger it ad-hoc when patterns suggest the coaching relationship needs recalibration. **To count sessions**: check the Session Log rows in `coaching_state.md` at session start. If t

Discussion

Ask, share a tip or report that it does not work. Sorted by what people marked helpful.

No posts yet. Be the first to ask or share.

Posts here are written by users, not the PopNx team.

Sign in to post

From GitHub

GitHub stars
2,545
Maker
noamseg
License
MIT
Last code change
May 30, 2026
SKILL.md files in the repo (including translated copies and templates)
1