agentleFS
eklavyagoyaleklavyagoyal/wingman/skills/interview-prep/SKILL.md

interview-prep

Skill0 starsChanged 2 months agoMITView on GitHub

Prepare for a German Vorstellungsgespräch - in the language the interview will actually be in

56 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use application-tracker, interview-debrief and 8 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • xiding-codeSkill

    application-tracker

    Automatically log and track all job applications submitted. Use this skill after every application submission to record the details in a tracking spreadsheet and save relevant documents. Also trigger when the user asks "application status", "what have I applied to", "tracking", or wants to review their application history. Maintains a single source of truth for all job search activity.

    Also in 4 projects that use this

  • jackhendonSkill

    interview-debrief

    Structure notes from a user research session into a clean debrief with insights, quotes, and implications. Paste your raw notes in and get a formatted summary ready for Notion.

    Also in 3 projects that use this

  • claude-office-skillsSkill

    cover-letter

    >

    Also in 7 projects that use this

  • xiding-codeSkill

    cover-letter-writer

    Write and iteratively refine cover letters using a 3-agent debate team (2 Opus critics + 1 Sonnet judge). Use this skill whenever a job application allows cover letter upload, whenever the user asks to write or improve a cover letter, or whenever the job-screener skill returns APPLY for a position. The must-write rule (if enabled in config) applies: if the application system has a cover letter upload field, a cover letter MUST be written. Trigger on: "write cover letter", "cover letter", any application form with a cover letter upload option, or after a job-screener APPLY decision.

    Also in 3 projects that use this

  • claude-office-skillsSkill

    company-research

    Conduct comprehensive company research and due diligence. Analyze business model, competitive landscape, management, and market position.

    Also in 5 projects that use this

  • aslavchevSkill

    mock-interview

    Simulate a real job interview for any role. Use when user says "mock interview", "interview me", "interview prep", "practice interview", or wants to rehearse for a specific company or position. Adapts rounds and questions to the role — technical, managerial, creative, or any other.

    Also in 4 projects that use this

  • +1 more from claude-office-skills

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 3 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 48 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read language.md. This is the first thing to establish, and the answer changes the whole session.

    line 13
  2. Distinctive:

    Every story must be sourced from the profile.

    line 43
  3. Distinctive:

    If the interview is in German, draft the stories in German.

    line 45
  4. Distinctive:

    Run it turn by turn in the interview's language.

    line 57
  5. Very specific:

    Write DATA_DIR/jobs/[folder]/interview-prep.md.

    line 61
  6. Very specific:

    Update the tracker status to Gespräch.

    line 63

“Common” is measured: kept by at least 6 in 10 of the 48 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Interview Prep

Language: shared/references/language-decision.md · Market terms: shared/references/de-market.md

Step 0: Which language will the interview be in?

Read language.md. This is the first thing to establish, and the answer changes the whole session.

If the application went out in German, expect at least part of the interview in German — and if a level gap was flagged during the application, say so now, directly: the phone screen is where an overstated CEFR level surfaces. Better to rehearse in German and be ready than to be surprised.

Offer to run the practice in German, in English, or mixed — recommending whichever matches language.md.

Step 1: Load context

posting.md, evaluation.md, profile.md, the tailored CV and letter. Block H of the evaluation already contains the strategy if the score was 4.0+.

Step 2: What a German interview actually contains

Different from a US loop in ways worth preparing for:

ElementNotes
SelbstpräsentationAlmost always opens with „Erzählen Sie etwas über sich" — expect to talk for 2–3 minutes, structured, chronological. Germans expect a career narrative, not a highlight reel. Rehearse this one properly; it sets the tone.
Formal registerSie unless the company clearly runs on du. Titles used (Herr Dr.).
PunctualityBeing 5–10 minutes early is expected, not optional. Late is close to disqualifying.
Lückenlose ChronologieExpect direct questions about every gap. Use the wording stored in profile.md, so it matches the CV exactly.
GehaltsvorstellungAsked directly and early, often in the first call. Jahresbrutto. Have the number and the justification ready.
Kündigungsfrist / EintrittsterminAsked in the first call. Know the real date.
RückfragenYou are expected to have questions. Having none reads as disinterest.
Assessment Center / ProbearbeitstagCommon at corporates and in some trades. Ask the recruiter which format to expect.
FachfragenTechnical depth, often more detailed and less puzzle-oriented than US interviews.

Step 3: STAR stories

Build 5–8 stories from profile.md covering conflict, failure, leadership, a technical decision, delivery under pressure, and cross-team work. Each: Situation, Task, Action, Result, plus Reflection — what they would do differently. German interviewers respond well to the reflection; it reads as self-awareness rather than polish.

Every story must be sourced from the profile. Never invent one, and never inflate a result beyond what the CV supports — this is the moment those get checked.

If the interview is in German, draft the stories in German. A story rehearsed in English and delivered in German comes out as translation.

Step 4: Questions to expect, and to ask

Predict 8–12 likely questions from the posting and the candidate's gaps. For each: the answer's spine, not a script. Include the awkward ones — the gap, the short tenure, the missing requirement, the language level.

Then draft Rückfragen worth asking: team structure, why the position is open, what success looks like at six months, Betriebsrat, Überstundenkultur, remote policy in practice rather than on paper.

Step 5: Practice (interactive)

Offer a practice run with AskUserQuestion: full mock, Selbstpräsentation only, salary negotiation only, or just review the notes.

Run it turn by turn in the interview's language. Give feedback after each answer — specific and usable, not encouragement. Flag anything that overstates what the CV supports, immediately.

Step 6: Save

Write DATA_DIR/jobs/[folder]/interview-prep.md. Append reusable STAR stories to a story bank in profile.md so they compound across applications instead of being rewritten each time.

Update the tracker status to Gespräch.


Response Format

  1. Format — language, expected structure, what to prepare
  2. Your Stories — the STAR+R set, mapped to likely questions
  3. Expect to be Asked — with answer spines, including the awkward ones
  4. Ask Them — your Rückfragen
  5. Practice — offer the mock

Permissions

{ "permissions": { "allow": [
  "Read(~/.wingman/**)", "Write(~/.wingman/**)", "Edit(~/.wingman/**)",
  "mcp__claude-in-chrome__*"
] } }

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.