agentleFS
UwayxtUwayxt/agent-skills/.agents/skills/user-research-synthesis/SKILL.md

user-research-synthesis

Skill4 starsChanged 3 months agoMITView on GitHub

Turn raw user data into ranked design insights. Use when synthesize interviews, user feedback, what did users say, research findings, analyze survey, or interview notes.

14 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use competitive-analysis and launch-strategy.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • AnthropicSkill

    competitive-analysis

    Framework for building competitive landscape decks — market positioning, competitor deep-dives, comparative analysis, strategic synthesis. Use when the user asks for a competitive landscape, competitor analysis, peer comparison, market positioning assessment, strategic review, or investment memo deck. Also triggers on "who are the competitors to X", "benchmark X against peers", "build a market map", or any request to systematically evaluate competitive dynamics across an industry.

    Also in 4 projects that use this

  • silvainfmSkill

    launch-strategy

    When the user wants to plan a product launch, feature announcement, or release strategy. Also use when the user mentions 'launch,' 'Product Hunt,' 'feature release,' 'announcement,' 'go-to-market,' 'beta launch,' 'early access,' 'waitlist,' or 'product update.' This skill covers phased launches, channel strategy, and ongoing launch momentum.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 14 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Never analyze qualitative complaints in a vacuum.

    line 14

“Common” is measured: kept by at least 6 in 10 of the 14 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Synthesis is the translation of raw user noise into ranked, actionable product decisions. Summarizing repeats what people said; synthesis uncovers the underlying behavioral patterns that dictate what you must build.

1. Collect & classify data by type

Separate input signals into two complementary streams:

  • Qualitative Data: User interview transcripts, open-ended support tickets, usability test session notes, observational recordings.
  • Quantitative Telemetry: Funnel drop-off percentages, feature click rates, search query logs, NPS scores, time-on-task metrics.

2. Triangulate qualitative insights with quantitative baselines

Never analyze qualitative complaints in a vacuum. Pair the "What" with the "Why":

  • Example: "Users abandon at Checkout Step 2" (Quantitative: 42% drop-off) + "I didn't trust that my credit card info was secure without a lock badge" (Qualitative: 7/10 users) = Single High-Confidence Insight.

3. Extract atomic observations

Break transcripts and notes into atomic observations (1 observation = 1 discrete action, quote, or blocker).

  • Valid atomic observation: "User #4 clicked the disabled 'Next' button 5 times because the required checkbox was scrolled out of view."
  • Invalid vague summary: "User was confused by the form."

4. Affinity clustering & thematic grouping

Group atomic observations into emerging behavioral themes (e.g. Mental Model Mismatch, Discoverability Gap, Trust Deficit, Operational Friction).

5. Weigh by Frequency × Severity Matrix

Plot themes on a 2×2 grid:

  • Frequency: Isolated (1 user) ↔ Pervasive (≥ 70% of sample).
  • Severity: Annoyance (cosmetic) ↔ Task Blocker (churn risk / fatal drop-off). Themes in Pervasive + Task Blocker are critical release-blocking priorities.

6. Derive actionable Insight Statements

Formulate structured insight statements: "[Target Segment] experiences [struggle/behavior] because [underlying root cause], which means we should [specific design/architectural remediation]."

Completion Criteria

  • Raw input parsed into discrete atomic observations (not premature conclusions)
  • Qualitative feedback triangulated with quantitative telemetry where available
  • Frequency × Severity matrix calculated for all identified clusters
  • Insight statements follow the [Segment] + [Behavior] + [Root Cause] + [Remediation] formula
  • Prioritized design recommendations ranked by impact and implementation effort

Output Format

A research_synthesis_report.md artifact containing the raw observation catalog, thematic clusters, Frequency × Severity matrix, and ranked actionable design recommendations.

Anti-patterns

  • Treating one vocal enterprise customer's feature demand as a universal product pattern.
  • Reporting raw transcript quotes without extracting the underlying root need.
  • Confusing feature requests ("they asked for an Excel export") with user needs ("reporting is fragmented across tools").
  • Ignoring quantitative baseline data when qualitative feedback contradicts real telemetry behavior.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.