investigate

Plan and conduct user research studies and synthesize findings into actionable insights.

Updated May 5, 2026
One-click install
npx skills add https://github.com/TheGeekosaurus/blogging-platform-2 --skill investigate-thegeekosaurus
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: investigate
Source: https://github.com/TheGeekosaurus/blogging-platform-2/tree/main/.agents/skills/investigate
Command: npx skills add https://github.com/TheGeekosaurus/blogging-platform-2 --skill investigate-thegeekosaurus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often make design decisions based on assumptions rather than evidence, or choose research methods before defining what they need to learn. This Skill guides the full user research lifecycle — planning, execution, synthesis, and communication — so findings are rigorous and decision-ready. ## Core Features & Use Cases - Research Planning & Method Selection: Choose the right method (interviews, usability tests, surveys, diary studies, contextual inquiry, card sorts, tree tests) based on the question, constraints, and required fidelity. - Instrument Design: Build interview guides with probing techniques, usability test plans with severity ratings, and bias-free surveys with proper question types and flow. - Synthesis & Communication: Apply affinity mapping, Braun & Clarke thematic analysis, and structured insight statements (observation + inference + implication) with evidence strength grading. - Use Case: A product team unsure why onboarding completion is low uses this Skill to plan five moderated usability tests, write the task scenarios, synthesize findings via affinity mapping, and deliver a findings report with prioritized recommendations. ## Quick Start Ask the AI to write an interview guide for understanding how new users experience your product's onboarding flow.

Frequently Asked Questions about investigate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I choose the right user research method?▼

Start with what you need to learn, then match the method to the question. Use interviews or contextual inquiry for generative exploration, usability tests or surveys for validation, diary studies for behavior over time, and card sorts or tree tests for information architecture questions.

How do I write a user interview guide?▼

Structure it as a conversation outline: a 5-10 minute opening with consent and rapport, 30-40 minutes of open-ended behavior-focused core questions with probes, and a closing summary. Avoid leading questions, hypotheticals, and asking participants to design solutions.

How many participants do I need for usability testing?▼

Five participants per round typically catch about 85% of usability issues. For surveys, aim for 100+ responses for descriptive statistics and 30+ per group for comparisons. Always report your sample size alongside findings.

How do I synthesize qualitative research findings?▼

Use affinity mapping by clustering individual observations bottom-up without preset categories, or apply the Braun & Clarke thematic analysis framework: familiarize, code, search for themes, review, define, and report. Tag every finding with an evidence strength rating.

What are common survey design mistakes to avoid?▼

Avoid double-barreled questions, leading wording, and unrandomized answer order. Watch for social desirability and acquiescence bias by asking about specific behaviors and mixing positively and negatively worded items. Pilot test with 5-10 people before launch.

When should I not use surveys for user research?▼

Do not survey before you know what to ask — generative questions need interviews or contextual inquiry first. Surveys reveal prevalence, not motivations, and small qualitative samples are better for understanding why users behave as they do.