Skip to main content
skill CX Codex

interview-prep · jamditis — Claude Code skill: interview research, questions

interview-prep — a skill for journalists and researchers to prepare for interviews: research a source's background, design effective questions, and understand recording-consent laws across U.S. states.

MIT 228 installs ★ 458 updated 2026-10-24

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add jamditis/claude-skills-journalism --skill interview-prep -a claude-code
Open on GitHub

What interview-prep does

The skill includes checklists for source research—public records, professional history, social media, prior statements—and question templates tailored to interview type: profile, investigative, expert explainer, and sensitive-topic conversations. Each template walks you through the right sequence and tone.

A core section covers U.S. recording laws. Most states allow one-party consent (you can record if you're part of the call), but about a dozen require all-party consent; rules sometimes differ between phone and in-person. The skill points to the Reporters Committee for Freedom of the Press recording guide for current, state-by-state details. The baseline across all jurisdictions: announce you're recording at the start and get affirmative consent on the recording itself.

Also included: attribution terms (on the record, on background, off the record), ethical guidance, and tactics for catching inconsistencies and building rapport.

What it helps with

  • Research a source's background before an interview
  • Design a coherent question sequence for different interview types
  • Determine if you need recording consent in a specific U.S. state
  • Set clear ground rules for attribution and confidentiality upfront
  • Spot contradictions and follow up effectively

Example prompts for the agent

  • Generate a source-research checklist for an interview with a government official
  • Create a question framework for a profile interview about someone's career
  • Check the recording-consent rules for California

How to install interview-prep

1Skills CLI (Vercel)

npx skills add jamditis/claude-skills-journalism --skill interview-prep -a claude-code

2Manually: put the files in place

~/.claude/skills/interview-prep/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/interview-prep/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about interview-prep

How do I install interview-prep in Claude Code?

Run npx skills add jamditis/claude-skills-journalism --skill interview-prep -a claude-code in your terminal, then open ~/.claude/skills/interview-prep/SKILL.md.

What does interview-prep do?

It provides pre-interview research checklists, question templates for different interview types (profile, investigative, expert, sensitive), and a guide to U.S. state recording-consent laws so you know whether you need permission to record.

When do I need to ask permission to record?

Most U.S. states use one-party consent—you can record if you're a party to the conversation. But roughly a dozen states (California, Florida, Illinois, Maryland, and others) require all-party consent. If you're calling someone in a different state, the stricter law applies. Either way, announce the recording and get consent on tape.

Source text

SKILL.md · MIT
---
name: interview-prep
description: Interview preparation and recording-consent law. Use for research, question frameworks, one-party or all-party consent rules.
---

# Interview preparation

Interviews fail in the preparation, not the conversation. This skill covers pre-interview research, question design, logistics, and follow-up.

## When to use

- Preparing to interview a source
- Developing question frameworks for recurring interview types
- Managing interview logistics and consent
- Planning follow-up after initial interviews
- Training new reporters on interview technique

## Pre-interview research checklist

### Background research

```markdown
## Source background check

### Public records
- [ ] Professional licenses verified
- [ ] Court records checked (civil/criminal)
- [ ] Business registrations confirmed
- [ ] Property records (if relevant)
- [ ] Campaign finance (if political figure)
- [ ] SEC filings (if corporate)

### Professional background
- [ ] LinkedIn profile reviewed
- [ ] Current employer confirmed
- [ ] Previous employers noted
- [ ] Published work reviewed
- [ ] Conference appearances checked
- [ ] Professional associations

### Social media audit
- [ ] All platforms identified (X, Bluesky, Threads, Mastodon, Instagram, Facebook, LinkedIn, TikTok, YouTube, Substack, etc.)
- [ ] Post history reviewed
- [ ] Connections/followers analyzed
- [ ] Previous statements on topic found
- [ ] Any deleted content recovered? (See **web-archiving** skill for Wayback / Archive.today retrieval)

### Media appearances
- [ ] Previous interviews found
- [ ] Statements consistent with current position?
- [ ] Other journalists' assessments
- [ ] Any retractions or corrections involving them?
```

### Context research

```markdown
## Topic preparation

### Essential knowledge
- [ ] Key facts about the topic confirmed
- [ ] Timeline of events established
- [ ] Other stakeholders identified
- [ ] Conflicting accounts noted
- [ ] Documents/data reviewed

### What to know before you dial
- [ ] How do they fit into the story?
- [ ] What do I NEED from this interview?
- [ ] What might they be reluctant to discuss?
- [ ] What have they said publicly before?
```

## Question framework

### The essential questions

Every interview should be built to answer:
1. **What happened?** (Facts)
2. **Why did it happen?** (Causes)
3. **What did you do/decide/see?** (Actions)
4. **What does it mean?** (Significance)
5. **What's next?** (Implications)

### Question types

| Type | Purpose | Example |
|------|---------|---------|
| **Open-ended** | Get the full story | "Walk me through what happened that day." |
| **Clarifying** | Pin down details | "When you say 'soon after,' do you mean minutes or hours?" |
| **Probing** | Go deeper | "Why do you think that happened?" |
| **Follow-up** | Catch inconsistencies | "Earlier you said X, but now you mentioned Y. Help me understand." |
| **Confrontational** | Challenge statements | "Documents show [fact]. How do you respond?" |
| **Closing** | Ensure completeness | "Is there anything I didn't ask that you think I should know?" |

### Question templates by interview type

**Profile interview:**
```markdown
1. Background: "Tell me about where you grew up / how you got started."
2. Turning point: "When did you realize [X] was your path?"
3. Challenge: "What was the hardest moment in [period]?"
4. Values: "What principle guides your work?"
5. Future: "What are you working on next?"
```

**Investigative interview:**
```markdown
1. Establish rapport: Non-threatening background questions first
2. Timeline: "Walk me through [event] from the beginning."
3. Details: "Who else was there? What did you see/hear?"
4. Documentation: "Do you have any records of this?"
5. Corroboration: "Who else can confirm this?"
6. Response: "What did [other party] say when you raised this?"
```

**Expert/explainer interview:**
```markdown
1. Credentials: "What's your expertise in this area?"
2. Plain language: "Explain [concept] as if I'm not a specialist."
3. Context: "How common/unusual is [situation]?"
4. Significance: "Why does this matter?"
5. Sources: "Where can I learn more? Who else should I talk to?"
```

**Victim/sensitive interview:**
```markdown
1. Control: "Take your time. You can stop at any point."
2. Open: "Tell me what you're comfortable sharing."
3. Specific: "Can you describe [specific detail]?"
4. Impact: "How has this affected you?"
5. Agency: "What do you want people to understand?"
6. Check-in: "Are you okay to continue?"
```

## Recording and consent

### Recording laws by state

State recording-consent law is jurisdiction-specific and shifts. Some states distinguish telephone from in-person recording; others treat electronic communications under a separate statute; case law in several states (e.g., Massachusetts, Michigan, Connecticut) has narrowed or expanded the original statutory rule.

**The single most reliable reference is the Reporters Committee for Freedom of the Press *Reporter's Recording Guide*** at `rcfp.org/reporters-recording-guide`. It is maintained continuously and provides per-state breakdowns covering one-party vs. all-party consent, phone-vs-in-person distinctions, hidden-recording rules, and federal preemption.

**General categories:**

- **One-party consent (federal default).** You can record without telling the other person if you are a party to the conversation. You *should* tell them anyway for ethical reasons.
- **All-party (two-party) consent.** All participants must consent. As of 2025-2026 this category includes (non-exhaustive, verify against RCFP before relying): California, Florida, Illinois, Maryland, Massachusetts, Montana, Nevada, New Hampshire, Pennsylvania, Washington. Several other states (Connecticut, Michigan, Oregon, Delaware, Vermont, Hawaii) apply two-party rules in some contexts but not all, RCFP has the per-context details.
- **Cross-state calls.** When the parties are in different states, the stricter state's law generally controls. If you are in a one-party state interviewing someone in a two-party state, get consent.

**Always do, regardless of jurisdiction:**

- State clearly at the start: "I'm recording this interview. Is that okay?"
- Get affirmative consent on the recording itself.
- Note the consent in your notes.

This protects you legally everywhere and is the ethical baseline.

### Consent template

```markdown
## Recording consent

Date: [date]
Interviewer: [your name]
Subject: [their name]
Medium: [phone/video/in-person]

[At start of recording:]
"This is [your name] with [publication], interviewing [their name] on [date].
I'm recording this conversation. Do I have your permission to record?"

[Their response: yes/no]

"And you understand this may be used for publication?"

[Their response: yes/no]
```

## Attribution guidelines

### On the record (default)
- Everything can be published with full name and title
- This is the standard expectation unless otherwise agreed

### On background
- Information can be used, but source not identified by name
- Agree on description: "a senior official," "someone familiar with the matter"
- Confirm exact wording before interview ends

### Deep background
- Information can guide reporting but cannot be attributed at all
- Verify independently before publishing
- Rarely appropriate, push for at least background

### Off the record
- Information is for your knowledge only
- Cannot be published or used to seek confirmation elsewhere
- Agree to this BEFORE they share information, not after
- If they say something on the record then try to take it off, you can refuse

### Clarifying attribution

```markdown
Before starting:
"Just to be clear on attribution, are we on the record?"

If they request otherwise:
"I'd prefer on the record. What concerns you about that?"

If they insist:
"Okay, we'll go on background. What description can I use?"

Document it:
"So I can refer to you as [agreed description], is that right?"
```

## Interview logistics

### Scheduling template

```markdown
## Interview request

To: [source name]
Subject: Interview request - [topic] - [publication]

[Name],

I'm a [title] at [publication] working on a story about [brief, honest description].

I'd like to speak with you because [why they're relevant]. The interview would take approximately [realistic time estimate].

Are you available [specific days/times]? I can do phone, video, or in-person, whatever works best for you.

Please let me know if you have questions about the story.

[Your name]
[Contact info]
```

### Pre-interview checklist

```markdown
## Day-of checklist

### Equipment
- [ ] Primary recorder charged/working
- [ ] Backup recorder ready
- [ ] Notebook and pens
- [ ] Printed questions/documents
- [ ] Business cards

### Logistics
- [ ] Location confirmed
- [ ] Contact's phone number for day-of
- [ ] Tested video/phone connection
- [ ] Quiet space secured

### Preparation
- [ ] Questions reviewed and prioritized
- [ ] Documents to reference ready
- [ ] Timeline of facts clear in mind
- [ ] Backup questions if interview goes short
```

## During the interview

### Opening
- Small talk to build rapport (brief)
- Confirm time available
- State recording and get consent
- Start with easy, open questions

### Active listening
- Let them finish sentences
- Use silence, don't fill every pause
- Take notes even if recording
- Note non-verbal cues separately

### Real-time verification
- Ask for specifics: dates, names, locations
- Request documentation during interview
- Ask "How do you know that?"
- Note inconsistencies for follow-up

### Closing
- "Is there anything I didn't ask that I should have?"
- "Who else should I talk to?"
- "Can I follow up if I have more questions?"
- Thank them for their time

## Follow-up protocols

For recording backup, transcription tooling, and quote verification mechanics, use the **interview-transcription** skill. The notes here cover only the post-interview *editorial* steps that aren't covered there.

### Immediate (same day)
- [ ] Back up recording (see interview-transcription for storage and naming)
- [ ] Note observations not on recording (body language, environment, off-mic remarks)
- [ ] Send thank-you if appropriate

### Within 48 hours
- [ ] Fact-check claims against available records
- [ ] Identify gaps requiring follow-up
- [ ] Add source to contacts database

### Before publication
- [ ] Verify quotes are accurate
- [ ] Confirm attribution terms
- [ ] Offer to read back quotes if promised
- [ ] Give chance to respond to characterizations (if newsworthy)

## Difficult situations

### They want to go off the record mid-interview
"Before I agree to that, let me hear what you want to tell me, and then we can discuss how to handle it."

### They refuse to answer
"I understand you can't discuss that. Can you point me to someone who can?"

### They're hostile
Stay calm. Keep questions factual. "I'm just trying to understand what happened."

### They're crying/emotional
Pause. "Take your time. We can stop whenever you need."

### They lie
Don't accuse. Present contradicting evidence: "Documents show [X]. Can you help me understand the discrepancy?"

---

*Good interviews require good preparation. The conversation is the easy part.*

© jamditis · MIT · jamditis/claude-skills-journalism

Similar skills

All skills for Writing and docs →

interview-prep by other authors comes first.

interview-prep official anthropics interview-prep is a Claude Code skill that builds interview plans with competency-based questions and scorecards. It activates for interview preparation and requests for interview questions or plans. CX Codex +1 3,900installs interview-prep rohitg00 The interview-prep Claude Code skill runs mock interviews for AI engineering roles. It asks a question or incident scenario, waits for an answer, then reviews it. CX Codex +1 532installs interview-prep tatat interview-prep turns a role and a company into a prep sheet: likely questions, STAR breakdowns and a few questions to ask back. CX Codex +1 104installs tech-podcast-interview-prep Samuel Berthe tech-podcast-interview-prep prepares a guest for someone else's technical podcast, YouTube interview or panel: show reconnaissance, a message spine, sound bites and a post-release promotion plan. CX Codex +1 13,500installs interview-prep-generator davila7 interview-prep-generator is a Claude Code skill that turns a resume into STAR stories, role-specific questions, and talking points. It activates for upcoming interviews or behavioral-question practice. CX Codex +1 61installs summarize-interview phuryn The summarize-interview skill transforms an interview transcript into a structured report with Jobs to Be Done, satisfaction signals, and action items. Saves time parsing recordings and helps organize insights for product discovery. CX Codex +1 3,000installs interview-me pedrohcgs interview-me runs a multi-turn interview and turns a half-formed research idea into a structured spec: question, hypotheses, identification, data, empirical strategy. CX Codex +1 ★ 1,729repo stars discovery-interview-prep deanpeters discovery-interview-prep guides product teams through planning customer discovery conversations. It sets up target segments, frames research goals, and filters out bias before you speak with users. CX Codex +1 3,200installs core-interview pwguler core-interview — a skill for Claude Code that runs an interview loop through decision trees until every branch is settled. CX Codex +1 1,000installs

From the same set35

The whole set →
newsroom-style newsroom-style applies AP Style and newsroom standards when drafting news stories, editing press releases, or sharpening headlines. CX Codex +1 279installs document-design document-design builds print-ready HTML for PDF export with brand styling. Use it for reports, proposals, one-pagers, newsletters, slides, or flyers. CX Codex +1 255installs editorial-workflow editorial-workflow organizes newsroom production with story status taxonomies, assignment cards, deadline schedules, and edit handoff checklists. CX Codex +1 252installs crisis-communications crisis-communications guides rapid fact-checking workflows and provides crisis communication templates under tight deadlines. CX Codex +1 232installs foia-requests foia-requests is a Claude Code skill with references and templates for drafting U.S. federal and state public records requests under FOIA and state laws. CX Codex +1 228installs interview-transcription The interview-transcription skill turns interview recordings into timestamped transcripts and helps extract quotes. Use it when audio or video must be checked before publication. CX Codex +1 226installs story-pitch This skill shapes story pitches for editors, query letters, and opinion pieces. Use it when an idea needs a clear angle, evidence plan, and outlet fit. CX Codex +1 215installs web-archiving web-archiving teaches the agent to pull archived copies of pages from Wayback Machine and Archive.today, and to save fresh snapshots before content changes. CX Codex +1 215installs

Project sponsors

Companies that keep this analytics open