Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Interview Script

ASecurity

Create a structured user interview script with warm-up, core exploration, and wrap-up sections. Use when preparing for user research interviews to ensure consistent, insightful conversations.

158 stars
0 votes
0 copies
0 views
Added 10/6/2026
developmentrustgorails

Security Analysis

A100/100

Scanned 10/6/2026

$npx -y skills add NVlabs/Skill2Env --skill interview-script --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Interview Script?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Interview Script
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/nvlabs-interview-script-skill2env/badge)](https://www.skillsdirectory.com/skills/nvlabs-interview-script-skill2env)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: interview-script
description: Create a structured user interview script with warm-up, core exploration, and wrap-up sections. Use when preparing for user research interviews to ensure consistent, insightful conversations.
---

# Interview Script

Create a structured user interview script for qualitative research.

## Context

You are a senior UX researcher preparing an interview script for $ARGUMENTS. If the user provides files (personas, research goals, product context), read them first.

## Domain Context

- User Interviews (Steve Portigal, Interviewing Users): Open-ended questions that reveal motivations, behaviors, and mental models.
- Follow the funnel approach: broad context questions before specific feature questions.
- Use JTBD probing: When did you last...? What were you trying to accomplish? What happened next?
- Avoid leading questions, hypotheticals, and yes/no questions.

## Instructions

1. **Clarify objectives**: Confirm the research goals, target participants, and interview duration.
2. **Create the script** with these sections:
   - **Introduction** (2-3 min): Welcome, explain purpose, set expectations, get consent
   - **Warm-up** (3-5 min): Easy context-setting questions about their background and role
   - **Core exploration** (20-30 min): Deep-dive questions organized by research theme, with follow-up probes
   - **Specific scenarios** (10-15 min): Walk-through of specific tasks or experiences
   - **Wrap-up** (3-5 min): Summary, anything we missed, next steps, thank you
3. **Include probing techniques**: "Tell me more about that", "Why was that important?", "What happened next?"
4. **Add facilitator notes**: Tips for staying neutral, handling tangents, and managing time.
5. Think step by step. Present the script in a ready-to-use format.

## Question Quality Guardrails

**Ensure all questions are non-leading.** A leading question contains the answer or implies a preferred response. Replace any question that assumes sentiment, behaviour, or outcome.

| Leading (avoid) | Non-leading (use) |
|---|---|
| "Was that frustrating?" | "How did you feel about that?" |
| "Did you find it easy?" | "How easy or difficult was that for you?" |
| "Did you like the feature?" | "What did you notice about that feature, if anything?" |
| "Would you use this?" | "How would you use this in your work, if at all?" |

**Test each question before including it:** If the question contains its own implied answer, rewrite it as an open invitation. If the question can be answered with yes or no, extend it ("...and why?").

## Further Reading

- Interviewing Users — Steve Portigal
- Just Enough Research — Erika Hall

Attribution

NVlabsNVlabs
View sourceSee grades on GitHubMore from NVlabs →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Clean Code

Pragmatic coding standards - concise, direct, no over-engineering, no unnecessary comments

304955 votes

Browser Extension Developer

Use this skill when developing or maintaining browser extension code in the `browser/` directory, including Chrome/Firefox/Edge compatibility, content scripts, background scripts, or i18n updates.

286712 votes

Seo Optimizer

SEO optimization with keyword analysis, readability assessment, technical validation, content quality. Use for search rankings, blog posts, content audits, or encountering keyword density, readability scores, meta tags, schema markup errors.

2222 votes

Google Official Seo Guide

Official Google SEO guide covering search optimization, best practices, Search Console, crawling, indexing, and improving website search visibility based on official Google documentation

1862 votes

Writing Plans

Use when you have a spec or requirements for a multi-step task, before touching code

2927051 votes
View all in development →