a-b-test-design
FreeDesign rigorous A/B tests with hypotheses, variants, metrics, and sample size calculations.
The English summary is being prepared. Showing the original description.
Infrasity-Labs/dev-gtm-claude-skills141Updated Jun 29, 2026
FreePublished on GitHub
interview-script
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.
The English summary is being prepared. Showing the original description.
See how to installFiles included (1)
- SKILL.md2.6 KB
SKILL.md (original)
Review the instructions the agent will receive before you install.
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
- Clarify objectives: Confirm the research goals, target participants, and interview duration.
- 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
- Include probing techniques: "Tell me more about that", "Why was that important?", "What happened next?"
- Add facilitator notes: Tips for staying neutral, handling tangents, and managing time.
- 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
Reviews
No reviews yet. Tell others what you thought.
Comments
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
More skills from this repository
ab-testing
FreeWhen the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program," or "experiment playbook." Use this whenever someone is comparing two approaches and wants to measure which performs better, or when they want to build a systematic experimentation practice. For tracking implementation, see analytics. For page-level conversion optimization, see cro.
The English summary is being prepared. Showing the original description.
Infrasity-Labs/dev-gtm-claude-skills141Updated Jun 29, 2026
Format CVs for academic positions with publications, grants, and teaching
The English summary is being prepared. Showing the original description.
Infrasity-Labs/dev-gtm-claude-skills141Updated Jun 29, 2026
Conduct a comprehensive accessibility audit against WCAG guidelines with severity ratings and remediation steps.
The English summary is being prepared. Showing the original description.
Infrasity-Labs/dev-gtm-claude-skills141Updated Jun 29, 2026
Create accessibility testing plans covering assistive technologies and WCAG criteria.
The English summary is being prepared. Showing the original description.
Infrasity-Labs/dev-gtm-claude-skills141Updated Jun 29, 2026
ad-creative
FreeWhen the user wants to generate, iterate, or scale ad creative — headlines, descriptions, primary text, or full ad variations — for any paid advertising platform. Also use when the user mentions 'ad copy variations,' 'ad creative,' 'generate headlines,' 'RSA headlines,' 'bulk ad copy,' 'ad iterations,' 'creative testing,' 'ad performance optimization,' 'write me some ads,' 'Facebook ad copy,' 'Google ad headlines,' 'LinkedIn ad text,' or 'I need more ad variations.' Use this whenever someone needs to produce ad copy at scale or iterate on existing ads. For campaign strategy and targeting, see ads. For landing page copy, see copywriting.
The English summary is being prepared. Showing the original description.
Infrasity-Labs/dev-gtm-claude-skills141Updated Jun 29, 2026