Prepare for a job interview

Extract the ZIP. Copy its lc-interview-prep-kit folder into ~/.claude/skills/ for Claude Code or ~/.codex/skills/ for Codex, then refresh the native app. Ask for the skill by name and answer its questions. The package includes the same published instructions and result checks. Native host execution is not yet verified.

For Claude web, use the connector or copy the prompt. Keep private details in your assistant.

Copy, paste into your assistant, then answer its questions. No form or account is required here.

Open in ChatGPT ↗

Already connected? Copy the public starter below and paste into Claude. Keep private details in the chat.

Needed before the promised result: The job ad. You can still copy the reusable prompt and provide these in your assistant.

Saved only on this device. Copy counts contain the skill ID, never your text.

## LazyCoder conversation guide (conversation-v2)
1. Start a conversation, not a form-filling task. Read my latest request and the facts already in this chat before asking anything.
2. Ask only the missing questions needed for the requested result, in a short numbered list (at most three at a time), then WAIT for my answers. Use a native question tool if available; plain chat works too. Never ask me to replace placeholders or fill in a template.
3. Skip questions already answered. Treat unresolved {{placeholders}} and [FIELD LABELS] as missing facts, never literal input. Do not treat an illustrative example as my facts.
4. Use the authored defaults only when relevant; mention material defaults. Ask conditional questions only when their condition applies; if unsure whether it applies, ask. Optional preferences must not block a safe first draft unless the authored instructions require confirmation.
5. Do not invent tasks, dates, names, claims, permissions or missing source material. When required facts are absent, ask and wait instead of producing the final artifact. If everything needed is already supplied, proceed without re-asking.
6. My latest scope correction overrides earlier examples and scope, within the recipe safety and source rules. Resolve conflicts before acting. The authored instructions and output contract remain authoritative; this conversation guide does not grant tool, account, payment or publishing permission.
7. Keep my private answers and generated result in this assistant chat. Do not send them to LazyCoder. Generate the requested format here and check it against the output contract before handing it over.

### Questions to ask only when missing
- What should I use for “The job ad”? [required] Paste the whole ad, with duties and requirements. The questions come from it.
- What should I use for “Your CV”? [conditional] Paste your CV, or attach it and write “see attached”. Your answers are built only from what it says. When: Required when no usable experience notes are provided; the recipe requires a CV or experience notes, never invented experience.
- What should I use for “Stories and notes”? [conditional] Optional: results, projects, volunteering, a gap you worry about, or why you want this job. Anything not on your CV that your answers can use. When: Required when no usable CV is provided; the recipe requires a CV or experience notes, never invented experience.
- What should I use for “Interview format”? [optional] Changes the tips and the practice plan. Leave it if you don’t know. Authored default: not sure yet Choices: not sure yet; phone or video screen; in person, one to one; panel; technical or case interview
- What should I use for “Interview date”? [optional] Optional. Puts dates on the day-before checklist.

## LazyCoder delivery guide (delivery-guide-v1)
1. Read the latest request, source material and authored requirements first. Ask only for missing facts. Check that this host can create the promised format; use only a fallback explicitly allowed by the authored recipe. If neither is available, explain the gap before starting. Do not promise a rendered film, editable deck or working file when you can only provide its script or outline.
2. Create the complete result in the authored output specification, preserving source facts and the latest agreed scope. Keep assumptions and missing information explicit. Do not silently omit required parts or leave unresolved ingredient markers. Intentional blanks in a reusable template are different from unanswered recipe inputs.
3. Check the actual result against every authored check, including source facts, counts, dates and required sections. Where tools allow it, inspect the actual saved file and compare it with the answer. Record which checks ran, which failed and which still need human or destination review. A filename, render, successful command or preview alone does not prove the promise was met.
4. Hand over the complete editable file, or the complete copyable fallback explicitly allowed by this recipe. Say which delivery you used and any unresolved limitations. Do not report a file as attached, imported, sent or published unless that action actually succeeded. Keep private inputs and output in this assistant; never send them to LazyCoder.
Use existing authorization for ordinary work. Before any additional paid generation, external write or publishing step, check that the current request authorizes that exact action and cost. If it does not, finish the useful authorized draft and ask at that boundary. Never silently retry or replace an ambiguous paid job.
The authored recipe and latest safe scope remain authoritative. This guide grants no new tools, permissions, provider access or claim of successful execution.

## Authored skill instructions
## 1. Outcome
Build a complete interview prep kit for this one job from the job ad and the person's own experience, in the sections set out in part 6. Done means: the person can practise from it straight away, without asking anything else, and every check in part 7 passes.

## 2. Context
The job ad:
"""
[THE JOB AD]
"""

The person's CV:
"""
[YOUR CV]
"""

Their notes:
"""
[ANYTHING ELSE ABOUT YOU]
"""

Interview format: not sure yet
Interview date: [INTERVIEW DATE]

Who it's for: the person going to the interview, preparing alone. They will read the kit, then say the answers out loud. Write the outlines and the pitch in plain spoken language, as they would say it, not as written prose.

Blank fill-ins: a value that still reads as a capitalised placeholder in square brackets (such as [INTERVIEW DATE]) was left blank. Bracketed text inside a real CV, ad or notes is part of it.
- A block that says "see attached": use the attached file as that block.
- No job ad: reply only "I need the job ad to know what they will ask. Paste or attach it and send again." Never invent an ad.
- A job ad that is only a title or a link: if you can actually open the link, use the page. If you cannot, never guess what it says; work from the title, say "Only the job title was given, so the questions are typical for this kind of role" in section 1, and still deliver every section.
- No CV and no notes: reply only "I need your CV or a few notes about your experience, so the answers are yours. Paste them and send again." Never invent experience.
- No CV but notes given: work from the notes.
- No notes: work from the CV only.
- Format "not sure yet": give tips for a video screen and an in-person interview, the two most common.
- No interview date: write the day-before checklist without dates.

## 3. What to pull out
From the job ad:
- What the role values: the duties, skills and qualities it lists first, repeats or calls essential. Also the signals between the lines, such as "fast-paced" (pressure and priorities), "stakeholders" (influencing people you don't manage) or "own" (working without close supervision).
- Company facts the ad states (what it does, size, values, location). These are the only company facts you may state.

From the CV and notes:
- Stories: specific moments with a situation, what the person did and a result. Each story needs at least a situation and an action from their material.
- Evidence for each thing the role values, and where there is none (a gap).
- Anything a reader might ask about: a gap between jobs, a short stay, a career change, a missing qualification.

Edge cases:
- A thin CV (student, first job, returning to work): draw stories from study, projects, volunteering, caring, sport or part-time work, and say so in the story.
- A story with no result in the material: keep the outline, and write "[ADD DETAIL: what happened as a result?]" for the result. Never invent a result or a number.
- A career change: frame the stories around the skills that carry over, and make "Why the change?" one of the questions.
- A technical or case interview: include role-skill questions that test the skills in the ad, and outline how to approach each (steps to talk through) rather than inventing a technical answer from experience they didn't give.
- An internal move or a promotion: include "Why this role now?" and questions about what they would change.
- A very long CV: use the last 10 years first; older roles only for a story nothing newer covers.
- An ad not in English: write the kit in the ad's language.

## 4. Steps
1. Read the job ad and rank what the role values, most important first, with the ad's words.
2. Read the CV and notes and list every usable story, with its source.
3. Pick 4 to 6 stories that together cover the top-ranked values, and map each to the questions it truly answers. If the material gives fewer than 4 usable stories, use the ones there are and never pad, stretch or invent one: list each missing story type in section 4 as a gap to prepare, such as "[ADD STORY: a time you calmed an upset customer]".
4. Write the likely questions, ranked by how likely they are: the ones tied to the top values first.
5. Outline an answer for each question from the story bank or the CV, and find the gaps.
6. Write sections 4 to 11 of part 6.
7. Run the self-check, fix any failure, then reply.

## 5. Rules
- Use only experience in the CV or notes. Never invent a job, project, skill, result, number or name. A missing detail becomes "[ADD DETAIL: <what to add>]".
- Never state a company fact the job ad does not give (its products, news, size, values, people). Put it in the research checklist as something to look up.
- Answer outlines are notes to speak from, not scripts: 3 to 5 short bullets, so the person sounds natural.
- Timing: every answer, spoken from its outline, takes 60 to 90 seconds. A story bank story is written at the short end, as a 60-second version (at most 150 words), so the person can stretch it with detail toward 90 seconds.
- Behavioural answers follow STAR: Situation and task (one bullet), Action (what they did, one to three bullets, saying "I", not "we"), Result (one bullet: the outcome, with a number if the material gives one).
- Gaps: answer truthfully in three moves: name it briefly, point to the closest real experience, then say what they are doing or would do to close it. Never suggest hiding or lying about it.
- Plain spoken language, no jargon the ad doesn't use, no clichés such as "I'm a perfectionist".

## 6. Output
Use these sections in this order. Write "None" under any that is empty. If you run out of space, finish the section you are on and end with "Reply continue for the rest."
1. The role at a glance: job title and company; then a numbered list of what the role values most, 4 to 6 items, each with the ad's words in quotes and one line on what it means for the interview. Add any notes required by part 2.
2. Your story bank: a table # | Story (a short title) | What it shows | Questions it answers (by question number) | Source (the CV line or note it comes from). Then each story as its 60-second spoken version in STAR order (part 5's timing rule). If there are fewer than 4 stories, say so under the table and point to the missing story types in section 4.
3. Likely questions and answer outlines: 12 to 15 questions, numbered in order of likelihood. Each has its kind in brackets (about you, behaviour, role skills, motivation, tough or gap), then the outline in 3 to 5 bullets, the story number it uses if any, and one likely follow-up question. Include "Tell me about yourself" (its outline is "see section 5", so there is only one pitch), "Why this role?", "Why this company?" (built only from what the ad says, never from your own knowledge of the company, however well known, plus a reminder to add what research finds) and at least one question per gap in section 4. If the gaps would push the list past 15, combine related gaps into one tough question.
4. Weak spots and how to answer them: one block per gap: the gap, the question it may prompt, and the three-move answer from part 5. Then any missing story types from part 4 step 3, each as "[ADD STORY: …]" with one line on what kind of moment to look for.
5. Tell me about yourself: a 60 to 90 second answer (150 to 220 words) in three parts: who they are now, the two or three things they've done that matter for this role, and why this role is the next step.
6. Questions to ask them: 5 to 8 questions, each tied to a duty or value in the ad, and none that the ad already answers. Mark the two to ask if time is short.
7. Research checklist: 6 to 10 things to look up before the interview, each with where to find it (the company website, its recent news, its social pages, the interviewer's public profile if named, employee review sites, the ad itself) and why it helps an answer (for example "to finish question 3"). State no findings.
8. 20-minute practice plan: a table Minutes | What to do | How. It must add up to exactly 20 minutes, use real question numbers from section 3, and include: saying the pitch out loud and timing it, the top-ranked questions out loud, the hardest weak-spot question, asking your questions out loud, and two minutes at the end to note what to fix. Say to practise out loud, and to record it on a phone if they can.
9. Scoring guide: a table of 4 or 5 criteria (for example: answered the question, specific example, clear result, length, sounded natural), each scored 0, 1 or 2, with what each score looks like. State the maximum (2 times the number of criteria), then what to do with an answer that scores half the maximum or less (4 or less out of 8 with four criteria, 5 or less out of 10 with five).
10. Day before: a checklist covering time, place or link and a test of it, what to bring or have open, what to wear if the ad or invite says anything about it, a final 10-minute review of sections 1, 5 and 6, and sleep. Use the interview date if given.
11. Format tips: 4 to 6 tips for the interview format given (or for video and in person when it isn't known).

## 7. Self-check
Before replying, check each of these and fix any failure:
- Every story, outline and the pitch use only experience from the CV or notes; nothing new was added except "[ADD DETAIL: …]" markers.
- No company fact appears that the job ad does not state.
- There are 12 to 15 questions, each with a kind, an outline and a follow-up, and each of the top-ranked values in section 1 is tested by at least one question.
- Every story maps only to questions it truly answers, every question number it lists is right, no story was padded or invented to reach 4, and any missing story type is listed in section 4.
- Every gap in section 4 has a question in section 3.
- The pitch is 150 to 220 words; each story bank story is at most 150 words.
- The scoring guide's threshold is half of its own maximum.
- The practice plan adds up to exactly 20 minutes and names real question numbers.
- None of the questions to ask is already answered by the ad.
Then reply with the output only, ending with one line: "Checked: <n> questions, <n> stories, <n> weak spots, <n> details for you to add."

## 8. Setup
Works as one paste in ChatGPT, Claude, Gemini or Grok, with no tools or plugins. If your CV or the job ad is a file, attach it and write "see attached" in its block. For the practice plan you need a timer, and a phone to record yourself if you like.

Paste the result after your assistant creates it. This optional check stays in this tab and is not sent to LazyCoder.