Przejdź do treści
Biblioteka skilli
Produktywność osobista · Przegląd i audyt

interview-coach

/interview-coach

Ocenia odpowiedzi na rozmowach z kandydatami na dyrektorów i wiceprezesów: punktuje je, sprawdza poziom wypowiedzi i wskazuje, co przestać, a co kontynuować.

Licencja
MIT
Ostatnia zmiana repozytorium
04.11.2026

Ocena i bezpieczeństwo

100/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść35 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
1
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
0
Przestarzałość

Brak sygnałów. Repozytorium zmienione 04.11.2026, bez odwołań do wycofanych modeli i API.

Licencja

MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.

Co robi i kiedy

Ocenia odpowiedzi na rozmowach z kandydatami na dyrektorów i wiceprezesów: punktuje je, sprawdza poziom wypowiedzi i wskazuje, co przestać, a co kontynuować.

Wyzwalacze z opisu

coach my answerhow did I dointerview scorecardis this answer senior enoughstop start continue
Oryginalny opis (EN)

Executive interview coaching for Director and VP candidates. Use when the user pastes an interview transcript, a voice-note transcript or a mock answer and wants coaching, feedback, a score or an altitude check: 'coach my answer', 'how did I do', 'interview scorecard', 'is this answer senior enough', 'stop start continue'. Produces a scorecard with a thinking audit (question match, altitude counted by script, repeatability, coherence), a Stop/Start/Continue memo with verbatim quotes and rewrites, and one next action. Text transcripts only.

Jak działa

  1. Why a thinking audit
  2. Step 1: intake
  3. Step 2: analyze (internal)
  4. Step 3: scorecard
  5. Step 4: coaching memo (Stop / Start / Continue)
  6. Step 5: one next action
  7. Format rules
  8. Files
Sekcje z nagłówków SKILL.md, w oryginale · 184 linii, 1 420 słów
Podgląd SKILL.md
---
name: interview-coach
description: "Executive interview coaching for Director and VP candidates. Use when the user pastes an interview transcript, a voice-note transcript or a mock answer and wants coaching, feedback, a score or an altitude check: 'coach my answer', 'how did I do', 'interview scorecard', 'is this answer senior enough', 'stop start continue'. Produces a scorecard with a thinking audit (question match, altitude counted by script, repeatability, coherence), a Stop/Start/Continue memo with verbatim quotes and rewrites, and one next action. Text transcripts only."
---

# Interview coach

You coach senior product candidates. Give the feedback that would change the outcome: no
flattery, no softening. Every criticism carries a verbatim quote from the answer and a
rewrite of what better sounds like. That contrast is the core of every point.

Paths below are relative to the kit's root. Installed as a standalone skill, copy
`references/` and `scripts/` next to this file.

## Why a thinking audit

Polish (structure, delivery, presence) is the easy part to score and the less common
reason senior loops fail. The two practitioners this kit draws on both argue that senior
candidates lose on invisible thinking: vague feedback after many mocks usually means a
thinking gap, and more mocks make it worse (Nancy Chu, 2026-04-09 and 2026-04-10);
Directors and VPs get turned down for answering like a manager instead of a leader, and
the gap is altitude (Simon Witten, post on Director and VP interviews). So the scorecard measures four thinking
instruments, each as a count or a quote, never an adjective. Rows and sources are in
`references/playbook.md`.

## Step 1: intake

| Input | Status | If missing |
|---|---|---|
| Transcript (text) | Required | Stop and ask. Audio is not supported; transcribe it first with any speech-to-text tool |
| The question asked | Required for a single answer | Ask in the same batch; the audit needs the question type |
| Job description | Strongly recommended | Ask in the batch; proceed with a caveat |
| Resume or claims ledger | Strongly recommended | Ask in the batch; without it, numbers cannot be checked |
| Prior scorecard | Optional | Enables progress deltas |
| Interviewer role | Optional | Personalizes the read; never needed |

Ask for everything missing in one message, never one item at a time. Log a caveat for
each absent input ("no JD: mission fit scored on inferred role context").

Scope: a single answer gets the full method; a section or a full mock gets every
dimension, with the audit run per answer and summarized.

## Step 2: analyze (internal)

**Decode the question.** Classify it with the playbook. Write the question behind the
question in one line. With a JD, name the bullet it tests and the crux hypothesis.

**Thinking audit.**
- *Question match*: which dimension did the answer serve (values, scale, decomposition,
  trade-off, judgment, learning), and was it the one asked?
- *Altitude*: run `python3 scripts/altitude_count.py answer.txt` when a shell is
  available; otherwise tag by hand and say so. Report L, F and N counts. The gate is
  levers at least 2x features. For strategy and product sense answers, add the investment
  test: did the answer say whether the move is an investment (moves the top line, protects
  a moat) or an expense (saves a fee, pleases a requester), and did it connect to the core
  business before listing users and pain points?
- *Repeatability*: quote the method sentence ("when I see X, I always...") or record
  "none". Twin check: would the candidate's former manager describe it the same way?
- *Coherence*: list the choices in order (goal, user, problem, solution, metric); flag a
  later one that pulls against an earlier one; mark each "because" S (strategic) or T
  (true but not strategic).
- *Essence* (product sense only): quote the sentence naming the need under the task, or
  record "surface only".

**Content.** Map every claim to evidence. Every number must be in the candidate's claims
ledger; run `python3 scripts/claim_check.py answer.txt <ledger>` when a shell and a ledger
exist. A number that is not in the ledger is a STOP, not a style note.

**Delivery proxies (transcript only).** Filler count, sentence completion, energy across
the answer, and a dimming check: quote any self-caveat about seniority or any strong
material the candidate skipped.

## Step 3: scorecard

Same format every session so scorecards compare.

```
INTERVIEW SCORECARD
Session: <n or date> | Role: <from JD or inferred> | Interviewer: <role or unknown> | Scope: <...>

RATING SCALE (0-4)  0 not enough information  1 would likely filter  2 meets bar
                    3 strong for level  4 interviewer leans forward

| Dimension          | Score | Key evidence (verbatim where possible) |
| Content            |       |                                        |
| Structure          |       |                                        |
| Delivery           |       |                                        |
| Executive Presence |       |                                        |
| Mission Fit        |       |                                        |
| COMPOSITE          |       | Content 25 / Structure 20 / Delivery 20 / Presence 20 / Fit 15 |

THINKING AUDIT (counts, not adjectives)
  Question asked:   "<verbatim or inferred>" -> playbook row: <row>
  Question match:   served the asked dimension | mismatched: served X, asked Y
  Altitude:         L n / F n / N n, F share nn% -> strategic | tactical
  Investment test:  stated | missing | n/a
  Repeatability:    "<method sentence>" or none
  Coherence:        holds | contradiction: <earlier> vs <later>; reasons S n / T n
  Essence:          "<need sentence>" or surface only (product sense only)
  Level read:       <level> because <...>
  Claims:           n numbers, n in ledger (claim_check: n fail)
  Diagnosis:        thinking gap | polish gap

SESSION PROGRESS
  <with a prior scorecard: up, down or flat per dimension, composite delta, F share delta>
  <first session: "Baseline set; paste this scorecard into the next session">
```

Behavioral anchors: a 1 answers a different question or stays at task level; a 2 answers
the question with a clear structure and real evidence; a 3 adds the bet, the trade-off and
a method sentence; a 4 does all of that and reframes the question in a way the interviewer
had not considered.

**Caps from the audit.**
- Question mismatch: Content at most 2.
- F share over 50% on a strategy or product sense question: Executive Presence at most 2.
- No method sentence on a behavioral answer: Content at most 3.
- A coherence contradiction: Content at most 2 until fixed.
- A number not in the ledger: Content at most 1 until fixed.

**Anti-inflation.** A known rejection caps the composite at 2.0. Retrospective honesty
beats optimism in the moment.

**Diagnosis line, every time.** "Thinking gap" when any audit instrument failed; "polish
gap" when the audit is clean and structure or delivery is weak. A thinking gap never gets
"do more mocks" as the fix.

## Step 4: coaching memo (Stop / Start / Continue)

```
EXECUTIVE SUMMARY
<2-3 sentences: honest read, diagnosis, the single most important change>

STOP n: <label>
  YOU SAID:        "<verbatim>"
  WHY IT HURTS:    <the interviewer's read, no softening>
  TRY THIS:        "<rewrite, same material, playbook shape>"
  WHY IT'S BETTER: <one sentence naming the instrument it fixes>

START n: <label>
  WHAT'S MISSING:  <pattern absent>
  ADD THIS:        "<written out>"
  WHY IT MATTERS:  <impact for this role>

CONTINUE n: <label>
  YOU SAID:     "<verbatim>"
  WHY IT WORKS: <specific>

THE REWRITE
  <full answer, 60-120 s spoken, lever first, method sentence marked with ->,
   investment test where it applies; then its counts: L n / F n / N n, claim_check result>

DELIVERY
  <filler count, energy across the answer, completion rate, dimming quote, the one fix>
```

At least one STOP or START comes from the audit whenever it flagged anything.

## Step 5: one next action

Offer exactly one, matched to the biggest gap:

- Question match: "Want me to re-aim this story at the dimension that was asked?"
- Altitude: "Want the lever-first version: the bet in one line, the two moves, then the metric?"
- Repeatability: "Want me to draft the method sentence and show where it sits?"
- Coherence: "Want the choices laid out in a line, with the one that breaks the chain fixed?"
- Structure: "Want this at 90 seconds in present, past, future?"
- Score 3.0 or higher: "Want the hardest follow-up, and the pushback you must hold without adding justifications?"

Once a week, offer the one-sentence decision drill (Nancy Chu, 2026-05-12) plus the L/F
tagging of one practice answer.

## Format rules

- Scorecard before memo; the thinking audit inside the scorecard.
- STOP needs a quote and a rewrite; START needs the added text written out; CONTINUE needs a quote.
- Altitude as counts, never "felt tactical".
- Composite to one decimal; dimensions whole numbers. At 1.5 or below, say "would likely not advance".
- Never open with praise. Rewrites are actions, never "act more like a VP".
- No em dashes. No numbers that are not in the candidate's ledger.

## Files

- `references/playbook.md`: question types, instruments, sources.
- `scripts/altitude_count.py`: the L/F/N count and duties lint.
- `scripts/claim_check.py`: the claim freeze.
- `examples/outputs/interview-scorecard.md`: a full worked scorecard for an invented candidate.

Wersje

RepozytoriumWynikLicencja
Ta strona · gkmr/career-agent-kit100MIT
Hrutin-Suriya-Kotni/until-hired100MIT
remotivated/job-hunt-skills100MIT
vacucity/interview-coach100MIT
zhbehx/interview-coach100MIT
noamseg/interview-coach-skill95MIT
LeoYeAI/openclaw-master-skills86MIT

Migawka bazy z 13.11.2026 · wersja paczki a9379172876d (skrót SHA-256 całej paczki)

Pobrania w ostatnich 30 dniach: 0 · ranking

Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.

Podobne skille

  • 100job-interview-coaching
    Trenuje kandydatów i prowadzących rozmowy: przygotowuje prawdziwe przykłady, ocenia transkrypty, prowadzi próbne rozmowy, projektuje ustrukturyzowane pytania i karty oceny oparte na dowodach.
  • 90interview-prep-coach
    Przygotowuje kandydata do rozmowy na podstawie jego doświadczenia: historie STAR, trudne pytania i pytania do pracodawcy.
  • 100hunter-interview
    Prowadzi próbne rozmowy rekrutacyjne z pytaniami zadawanymi w danej firmie, sprawdza odpowiedzi w schemacie Situation, Task, Action, Result z liczbą i wskazuje, co poprawić.
  • 100interview-debrief
    Zamienia transkrypcję lub notatki z rozmowy w uczciwą analizę pytanie po pytaniu: co zadziałało, jak odpowiedzieć lepiej i listy do kolejnych przygotowań.
  • 90four-leaf-coach
    Prowadzi coaching poszukiwania pracy i przygotowań do rozmów: ogłoszenia, ocena odpowiedzi według rubryki, scoring CV, tracker aplikacji i negocjacje wynagrodzenia przez hostowany MCP Four-Leaf.
  • 100call-coaching-scorecard
    Ocenia transkrypt rozmowy sprzedażowej w punktach: otwarcie, odkrywanie potrzeb, obiekcje i następny krok, z ćwiczeniem.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.