interview-prep
Prepare for journalism interviews with research checklists, question frameworks, and attribution guidelines. Use when preparing to interview sources, planning follow-up questions, or managing interview logistics. Covers consent, recording laws, and professional protocols.
What this skill does
# 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 [pub
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.