Agent skill

Interview Prep

by jamditis in jamditis/claude-skills-journalism

Interview preparation and recording-consent law. An agent skill from jamditis/claude-skills-journalism.

MITAuto-check passedBusiness, Finance & HR

Install Interview Prep

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

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jamditis/claude-skills-journalism interview-prep --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jamditis/claude-skills-journalism.git skills-src && mkdir -p .claude/skills && cp -r skills-src/journalism-core/skills/interview-prep .claude/skills/interview-prep && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
interview-prep
GitHub stars
416
Token cost
~2.8k tokens
SKILL.md length
853 words
Files
2
Skills in repo
53
Repo updated
First seen
Licence
MIT

At a glance

Interview preparation and recording-consent law. An agent skill from jamditis/claude-skills-journalism.

  • Works in 5 steps: What happened? (Facts) → Why did it happen? (Causes) → What did you do/decide/see? (Actions) → …
  • Question frameworks
  • SKILL.md covers When to use, Pre-interview research checklist, Question framework and Recording and consent, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Interview Prep is an agent skill from jamditis/claude-skills-journalism. Interview preparation and recording-consent law. Use for research, question frameworks, one-party or all-party consent rules.

Its SKILL.md is about 2.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).

It sits in Business, Finance & HR, covering Interview preparation and Hypothesis generation. The repository describes itself as: Claude Code skills for journalism, media, and academia - verification, FOIA, data journalism, academic writing, and more. The licence is MIT.

When your agent uses it

  • Question frameworks
  • All-party consent rules

Example prompts

  • “/interview-prep”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  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)

What it can do on your machine

Read from SKILL.md and the folder at commit e3e2172. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Interview Prep loads about 2.8k tokens when it runs. Until then it costs about 35 tokens; SKILL.md has 853 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~35
When it runs · the whole SKILL.md, loaded when a task matches
~2.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from jamditis/claude-skills-journalism at commit e3e2172, republished under its MIT licence (© jamditis). 853 words, ~2,820 tokens.

Download SKILL.mdSave it as .claude/skills/interview-prep/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
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
TypePurposeExample
Open-endedGet the full story"Walk me through what happened that day."
ClarifyingPin down details"When you say 'soon after,' do you mean minutes or hours?"
ProbingGo deeper"Why do you think that happened?"
Follow-upCatch inconsistencies"Earlier you said X, but now you mentioned Y. Help me understand."
ConfrontationalChallenge statements"Documents show [fact]. How do you respond?"
ClosingEnsure 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 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.

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
Show full SKILL.md (348 more words)Show less
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. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in journalism-core/skills/interview-prep of jamditis/claude-skills-journalism.

  • SKILL.md
  • agents/openai.yaml

Open the folder on GitHubat commit e3e2172

Compare with similar skills

Interview Prep next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Interview Prep compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Interview Prep this skilljamditis/claude-skills-journalism416—~2.8kAutomated safety check: PassMIT
Career-Ops Job Search Centercareer-ops-hq/career-ops74k—~3.3kAutomated safety check: PassMIT
Internship Project Preparation ToolLiuMengxuan04/shushu-internship-tool2.1k—~2.3kAutomated safety check: PassCustom licence
Interview Coachnoamseg/interview-coach-skill2.3k—~3.7kAutomated safety check: PassMIT
Job Application AssistantMadsLorentzen/ai-job-search45k—~1.2kAutomated safety check: NotesMIT
Algo Senseikaranb192/algo-sensei284—~1.7kAutomated safety check: PassMIT

Similar skills

  • Career-Ops Job Search Center

    career-ops-hq/career-ops

    Routes job-search requests to modes for evaluating offers, scanning portals, generating tailored CVs, tracking applications and drafting outreach, starting from a pasted job URL or description.

    74k GitHub stars~3.3k tokensUpdated yesterday
    Business, Finance & HRAuto-check passed
  • Internship Project Preparation Tool

    LiuMengxuan04/shushu-internship-tool

    Turns a target internship job description into a resume-ready, interview-ready project by finding and auditing GitHub projects and drafting resume bullets and interview Q&A.

    2.1k GitHub stars~2.3k tokensUpdated 3 mo ago
    Business, Finance & HRAuto-check passed
  • Interview Coach

    noamseg/interview-coach-skill

    High-rigor interview coaching skill for job seekers. An agent skill from noamseg/interview-coach-skill.

    2.3k GitHub stars~3.7k tokensUpdated 4 mo ago
    Business, Finance & HRAuto-check passed
  • Job Application Assistant

    MadsLorentzen/ai-job-search

    Evaluates job postings against your profile, then tailors a LaTeX CV and cover letter and prepares interview answers for the roles you pursue.

    45k GitHub stars~1.2k tokensUpdated 2 days ago
    Business, Finance & HRAuto-check: notes
  • Algo Sensei

    karanb192/algo-sensei

    Your personal DSA & LeetCode mentor. An agent skill from karanb192/algo-sensei.

    284 GitHub stars~1.7k tokensUpdated 5 days ago
    Business, Finance & HRAuto-check passed
  • Backend and Agent Project Selector

    lishuangqiang/backend-agent-resume-scout

    Finds backend or AI agent projects on GitHub that are worth putting on a resume, checks them against local source and writes a Markdown resume package.

    347 GitHub stars~1.4k tokensUpdated 3 mo ago
    Business, Finance & HRAuto-check passed

More from jamditis/claude-skills-journalism

All 53 skills in this repo
  • Web Design Picker

    jamditis/claude-skills-journalism

    A skill your agent uses when creating distinct website directions, a client review picker, asset catalog, previews, and Cloudflare-ready handoffs.

    416 GitHub stars~3.1k tokensUpdated 3 days ago
    Auto-check passed
  • Okf Wiki

    jamditis/claude-skills-journalism

    Builds an Open Knowledge Format (OKF) knowledge base from existing docs, notes, or a repo.

    416 GitHub stars~4.7k tokensUpdated 3 days ago
    Auto-check passed
  • Private Secret Scanning

    jamditis/claude-skills-journalism

    Local Gitleaks scans for staged changes, push ranges, and full history in private repos, with redacted reports.

    416 GitHub stars~1.8k tokensUpdated 3 days ago
    Auto-check passed
  • Data Journalism

    jamditis/claude-skills-journalism

    Acquire, clean, analyze, verify, visualize, and explain data for journalism.

    416 GitHub stars~1.6k tokensUpdated 3 days ago
    Auto-check passed
  • Document Design

    jamditis/claude-skills-journalism

    Creates print-ready HTML that exports to PDF. An agent skill from jamditis/claude-skills-journalism.

    416 GitHub stars~1.9k tokensUpdated 3 days ago
    Auto-check passed
  • Using Superjawn

    jamditis/claude-skills-journalism

    Establishes how to find and use skills, requiring Skill tool invocation before any response.

    416 GitHub stars~1.5k tokensUpdated 3 days ago
    Auto-check passed

Questions about Interview Prep

What does Interview Prep do?

Interview preparation and recording-consent law. An agent skill from jamditis/claude-skills-journalism. Interview Prep is an agent skill from jamditis/claude-skills-journalism. Interview preparation and recording-consent law.

When should I use Interview Prep?

Interview Prep fits situations like: question frameworks; all-party consent rules.

How do I install Interview Prep in Claude Code?

Run `npx skills add jamditis/claude-skills-journalism --skill interview-prep -a claude-code`. Or copy the skill folder (journalism-core/skills/interview-prep in jamditis/claude-skills-journalism) into .claude/skills/interview-prep in your project. Claude Code loads it when a task matches its description.

How do I install Interview Prep in Codex?

Run `npx skills add jamditis/claude-skills-journalism --skill interview-prep -a codex`. Or copy the skill folder (journalism-core/skills/interview-prep in jamditis/claude-skills-journalism) into .agents/skills/interview-prep in your project. Codex loads it when a task matches its description.

Can I use Interview Prep in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jamditis/claude-skills-journalism --skill interview-prep -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/interview-prep, .gemini/skills/interview-prep, .github/skills/interview-prep and .opencode/skills/interview-prep in your project.

What does Interview Prep need to run?

SKILL.md names no scripts, command-line tools or credentials: Interview Prep is instructions for the agent only.

Does Interview Prep access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Interview Prep safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Interview Prep use?

Interview Prep is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Interview Prep use?

About 2.8k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Interview Prep?

Skills that share tags, products or a category with Interview Prep: Career-Ops Job Search Center (career-ops-hq/career-ops, 74k stars), Internship Project Preparation Tool (LiuMengxuan04/shushu-internship-tool, 2.1k stars), Interview Coach (noamseg/interview-coach-skill, 2.3k stars) and Job Application Assistant (MadsLorentzen/ai-job-search, 45k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Interview Prep?

jamditis (a GitHub user) maintains it in jamditis/claude-skills-journalism, which has 416 GitHub stars. The repository holds 53 skills in this directory. The repository was last updated on October 4, 2026.

Source: jamditis/claude-skills-journalism on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.