プロトタイプ · プレビュー版:公式レジストリのすべてのサーバーを掲載し、30分ごとに同期しています。Google でログインするとレビューを書けます。プロトタイプ · 30分ごとに更新
PopNx MCPAIを使う人のためのMCPサーバー · やさしい言葉で解説

interview-coach-skill Skill

リポジトリ ↗

作者:noamseg★ 2,5451 個の skill

インストール

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 その他
作者向け:README にバッジを付ける

作者の方は、このコードを README に貼れます。バッジはこのページにリンクします。

[![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)

似た Skill

同じ種類の作業。Skill 一覧と同じ並び

似たものと比べる
これ
interview-coach-skill
llmfitclaude-videoVideoCaptionerclaude-cookbooks
作者noamsegAlexsJonesbradautomatesWEIFENG2333anthropics
Skill 数11114
GitHub スター2,54539,03621,08516,55754,799
最終コード更新2026年5月30日2026年11月16日2026年9月25日2026年9月12日2026年11月5日
ライセンスMITMITMITGPL-3.0MIT

noamseg による 1 個の Skill(指示セット)。AI が読んでそのとおりに作業します · MCP server ではありません

Skill と MCP の違い

MCP = 手

AI を外部のサービスやデータにつなぎます(例:Notion を読む、請求書を作る)。プログラムやサーバーが動いている必要があります。

Skill = 手順書

作業のやり方を AI に教えるテキストファイル。どのサービスにもつながりません。

重なる部分もあります。ツールを呼ぶスクリプト付きの Skill や、知識だけを渡す MCP もあります。やりたい作業から選んでください。

使えるアプリ

Claude CodeCodexCursor

提供元の README と repo のフォルダから判断

インストール

Is it safe?

  • Who made it

    GitHub account noamseg (person), 13 years old

  • Use and upkeep

    ★ 2,545 stars · code last changed 2026年5月30日

  • 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

まず:どの AI を使っていますか

使っているアプリを選ぶと、そのアプリでのインストール方法だけが表示されます

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 1Claude Code にインストールしてもらう

この文をコピーして Claude Code のチャットに貼り付けます

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

Claude Code を開き直し、/interview-coach-skill と入力するか関連する作業を頼むと Claude が自動で使います

Checked against official docs 2026年11月12日 · Source: code.claude.com

For Terminal users

Skill は AI が従う指示です。入れる前にファイルを読み、信頼できる提供元のものだけを入れてください。

  1. ターミナルを開く

    Mac:Command+スペースで Terminal と入力 · Windows:下のコマンドは PowerShell では動きません。上の「AI にインストールしてもらう」を使ってください

  2. skill フォルダを ~/.claude/skills にコピー

    repo を一時フォルダにダウンロードし、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. Claude Code を開き直し、/interview-coach-skill と入力するか関連する作業を頼むと Claude が自動で使います

自分でインストールした Skill は ChatGPT デスクトップアプリ、Codex CLI、IDE の Codex 拡張機能で使えます · Web 版とモバイル版の ChatGPT では自分でインストールした Skill は使えず、ディレクトリのプラグインに含まれる Skill だけが使えます

ChatGPT デスクトップアプリ

ChatGPT デスクトップアプリには Codex が組み込まれていて、Codex は ~/.agents/skills フォルダから Skill を読み込みます

Option 1ChatGPT にインストールしてもらう

ChatGPT デスクトップアプリで Codex を開き、この文をチャットに貼り付けます

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 2自分でフォルダを置く

interview-coach フォルダを ~/.agents/skills/interview-coach に置きます

~ はホームフォルダ($HOME)です

For Terminal users

Skill は AI が従う指示です。入れる前にファイルを読み、信頼できる提供元のものだけを入れてください。

  1. ターミナルを開く

    Mac:Command+スペースで Terminal と入力 · Windows:下のコマンドは PowerShell では動きません。上の「AI にインストールしてもらう」を使ってください

  2. skill フォルダを ~/.agents/skills にコピー

    repo を一時フォルダにダウンロードし、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

インストールしたあと

  • ChatGPT デスクトップアプリ:サイドバーの Skills を開いて Skill があるか確認します
  • 使い方:ChatGPT では @ を入力して Skill を選びます · Codex CLI や IDE 拡張機能では /skills を実行するか、$ に続けて Skill 名を入力します
  • Codex は新しくインストールした Skill を自動で見つけます。表示されない場合は Codex を再起動してください

Checked against official docs 2026年11月15日 · Source: learn.chatgpt.com

Web 版とモバイル版の ChatGPT

自分でインストールした Skill は使えません。ディレクトリのプラグインに含まれる Skill だけが使えます

この Skill を ChatGPT で使うには、上の方法で ChatGPT デスクトップアプリを使ってください

Checked against official docs 2026年11月15日 · Source: learn.chatgpt.com

Option 1Codex にインストールしてもらう

この文をコピーして Codex のチャットに貼り付けます · ChatGPT デスクトップアプリ内の Codex、Codex CLI、IDE 拡張機能で使えます

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 は新しくインストールした Skill を自動で見つけます。表示されない場合は Codex を再起動してください · 使い方:ChatGPT では @ を入力して Skill を選びます · Codex CLI や IDE 拡張機能では /skills を実行するか、$ に続けて Skill 名を入力します

Checked against official docs 2026年11月15日 · Source: learn.chatgpt.com

For Terminal users

Skill は AI が従う指示です。入れる前にファイルを読み、信頼できる提供元のものだけを入れてください。

  1. ターミナルを開く

    Mac:Command+スペースで Terminal と入力 · Windows:下のコマンドは PowerShell では動きません。上の「AI にインストールしてもらう」を使ってください

  2. skill フォルダを ~/.agents/skills にコピー

    repo を一時フォルダにダウンロードし、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. Codex を開き直して関連する作業を頼むと、Codex が skill を一覧に出します

Option 1Cursor にインストールしてもらう

この文をコピーして Cursor のチャットに貼り付けます

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

Cursor の Agent チャットで / を入力し interview-coach-skill を選ぶ

Checked against official docs 2026年11月12日 · Source: cursor.com

For Terminal users

Skill は AI が従う指示です。入れる前にファイルを読み、信頼できる提供元のものだけを入れてください。

  1. ターミナルを開く

    Mac:Command+スペースで Terminal と入力 · Windows:下のコマンドは PowerShell では動きません。上の「AI にインストールしてもらう」を使ってください

  2. skill フォルダを ~/.cursor/skills にコピー

    repo を一時フォルダにダウンロードし、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. Cursor の Agent チャットで / を入力し interview-coach-skill を選ぶ

Option 1Let the AI install it

Skill を読めるほかのアプリ向けです。この文には Claude Code、Codex、Cursor のパスが入っていて、AI が使っているアプリに合わせて選びます · 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 2026年11月12日 · Source: code.claude.com, learn.chatgpt.com, cursor.com

For Terminal users

Gemini CLI や GitHub Copilot など Agent Skills 対応の他のアプリはフォルダが違います。そのアプリのガイドを見て、SKILL.md のあるフォルダをコピーしてください。

GitHub で見る ↗

2026年11月11日 に Claude Code、Codex、Cursor の公式ガイドで skill フォルダを確認

✓ コマンド確認済み 2026年11月18日

元の SKILL.md を見る

以下は提供元の repo の文章で、PopNx MCP の指示ではありません

最初の 8,000 文字を表示 · 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

話し合い

質問、コツの共有、使えないことの報告ができます。「役に立った」の多い順です。

まだ投稿はありません。最初の質問や共有をどうぞ。

ここの投稿は利用者によるもので、PopNx チームのものではありません。

ログインして投稿

GitHub の情報

GitHub スター
2,545
提供元
noamseg
ライセンス
MIT
最終コード更新
2026年5月30日
repo 内の SKILL.md(翻訳版とテンプレートを含む)
1