Run any Skill in Manus with one click

craft-discovery-synthesis

Stars128

Forks15

UpdatedApril 6, 2026 at 04:28

Take raw user interview notes or feedback and extract themes and insights. Use when synthesizing qualitative data from interviews, surveys, support tickets, or feedback.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

amplitude

amplitude/builder-skills

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Project Management SpecialistsBusiness and Financial Operations Occupations·SOC 13-1082

SKILL.md

readonly

name	craft-discovery-synthesis
description	Take raw user interview notes or feedback and extract themes and insights. Use when synthesizing qualitative data from interviews, surveys, support tickets, or feedback.
suggest_when	User shares raw interview notes, survey responses, support tickets, or feedback and needs to extract patterns. Says "synthesize this", "what are the themes", "summarize this research".

Discovery Synthesis

Take raw user interview notes or feedback and extract themes and insights.

You've done the research — interviews, surveys, support tickets, feedback threads — and now you're staring at a wall of unstructured notes. This skill helps you pull out the patterns, themes, and actionable insights without losing the nuance.

Prompt Template

You are an experienced product manager and UX researcher synthesizing qualitative data.

Here are the raw notes from user research:

<context>
$ARGUMENTS
</context>

> If the above is blank, ask the user: "{{PASTE YOUR INTERVIEW NOTES, SURVEY RESPONSES, SUPPORT TICKETS, OR FEEDBACK HERE}}"

Synthesize this into a research summary that includes:

1. **Key Themes** — The 3-5 most prominent patterns across the data. For each theme, include supporting quotes or examples.
2. **Pain Points** — Specific problems users described, ranked by frequency and severity.
3. **Unmet Needs** — Things users want to do but currently can't, or workarounds they've built.
4. **Surprises** — Anything unexpected that challenges our assumptions.
5. **Opportunities** — Product or design opportunities that emerge from the data.
6. **Confidence Level** — How confident should we be in these findings? Flag where more research is needed.

Preserve the user's voice — use direct quotes where they're powerful. Distinguish between what users said vs. what you're inferring. Be honest about thin data.

Tips

Don't worry about cleaning up your notes before pasting them in. Messy is fine — the skill is designed for raw input.
If you have notes from multiple sources (interviews + support tickets + survey), label them so the synthesis can distinguish between them.
Run this after each batch of interviews to build up a living insights library over time.

More from this repository

same repository

instrument-pr

amplitude/builder-skills

Instruments a pull request with Amplitude analytics that conform to the project's existing taxonomy. Reads the tracking plan via the Amplitude MCP server (events, properties, naming conventions), analyzes the PR diff to find the few user actions genuinely worth tracking, detects the codebase's SDK and tracking patterns, and adds instrumentation that matches both. Optionally (opt-in) stages new events and properties on an Amplitude tracking-plan branch for data-governance review. Use when asked to "instrument this PR", "add analytics to this change", "add tracking", "add Amplitude events", "instrument this feature", or "what should I track here".

2026-07-09128

product-diagnosis

amplitude/builder-skills

Diagnoses product health by cross-referencing Amplitude analytics (dashboards, charts, funnels, feedback, AI agent analytics), optionally Datadog (errors, latency, stack traces), and optionally Slack (qualitative feedback, bug reports, feature requests). Identifies what's broken, what's working, and what to do about it — with root causes, not just symptoms. Use when asked to "diagnose my product", "what's going on", "product health check", "what's broken", "where are users struggling", "give me a product diagnosis", or "what should I focus on".

2026-07-09128

citation-recovery-optimizer

amplitude/builder-skills

Use this skill whenever a user wants to improve existing pages on their website to get cited more by AI models — whether they say "our pages aren't getting cited", "improve this page for AI visibility", "which of our pages should we update", "make this article more cite-worthy", "our competitors are getting cited instead of us", "update our content for AI search", or any variation where the goal is improving an existing asset rather than creating something new. This skill pulls owned pages from AI Visibility, identifies which ones have citation potential but are underperforming, compares them against the external pages that are winning citations on the same topics, and produces section-level rewrites or a full-page update — then pushes the revision to the CMS as a draft. Trigger even if the user just says "help me get cited more" or "why is [competitor] getting cited instead of us".

2026-04-23128

competitor-prompt-hijacker

amplitude/builder-skills

Use this skill whenever a user wants to win AI citations on prompts that competitors currently dominate — whether they say "competitors are getting cited instead of us", "we're losing on these prompts", "how do I outrank [competitor] in AI answers", "find prompts where we should be winning", "create content to beat [competitor]", or any variation where the goal is capturing AI share on prompts a competitor currently owns. This skill pulls competitor visibility data from AI Visibility, identifies the specific prompts where competitors win and Amplitude is absent, clusters them by intent, and produces targeted comparison pages, alternatives content, or rebuttal assets — then pushes drafts to CMS. Trigger on any mention of competitor, prompt hijack, outrank, or "why is [competitor] getting cited instead of us".

2026-04-23128

prompt-gap-to-publish

amplitude/builder-skills

Use this skill whenever a user wants to turn AI Visibility data into published content — whether they say "find content gaps", "what should we write about", "which topics have low visibility", "help me get cited by AI models", "create a blog post from our AI Visibility gaps", "we're losing to competitors on these prompts", or any variation where they want to go from AI visibility weakness to a draft article, landing page, or FAQ. This skill connects directly to Amplitude AI Visibility data (topics, prompts, visibility scores, citations, competitor data, full LLM responses and sources) and produces a publish-ready content brief plus full article draft. If the user mentions CMS (WordPress, Webflow, Contentful, Sanity, HubSpot, Ghost, Shopify), also trigger this skill to push the draft directly. Trigger even if they just say something vague like "what content should we create?" in an AI Visibility context.

2026-04-23128

simulation-backed-publisher

amplitude/builder-skills

Use this skill whenever a user wants to test content variants before publishing to find which one will get cited most by AI models — whether they say "which version of this content will perform better", "test this article before we publish", "simulate how AI will respond to this content", "which angle should we use", "generate content variants and pick the winner", "run a simulation before publishing", or any variation where the goal is data-driven content selection rather than gut-feel publishing. This skill takes an identified content opportunity, generates 2–3 distinct variants with different angles or structures, scores them against actual AI model responses from AI Visibility, references the Simulate Changes feature for pre-publish validation, and produces a clear recommendation on which variant to publish — then pushes the winner to CMS. Trigger on any mention of "simulate", "test variants", "which performs better", "A/B content", or "before we publish".

2026-04-23128

name	craft-discovery-synthesis
description	Take raw user interview notes or feedback and extract themes and insights. Use when synthesizing qualitative data from interviews, surveys, support tickets, or feedback.
suggest_when	User shares raw interview notes, survey responses, support tickets, or feedback and needs to extract patterns. Says "synthesize this", "what are the themes", "summarize this research".

Discovery Synthesis

Take raw user interview notes or feedback and extract themes and insights.

Prompt Template

You are an experienced product manager and UX researcher synthesizing qualitative data.

Here are the raw notes from user research:

<context>
$ARGUMENTS
</context>

> If the above is blank, ask the user: "{{PASTE YOUR INTERVIEW NOTES, SURVEY RESPONSES, SUPPORT TICKETS, OR FEEDBACK HERE}}"

Synthesize this into a research summary that includes:

1. **Key Themes** — The 3-5 most prominent patterns across the data. For each theme, include supporting quotes or examples.
2. **Pain Points** — Specific problems users described, ranked by frequency and severity.
3. **Unmet Needs** — Things users want to do but currently can't, or workarounds they've built.
4. **Surprises** — Anything unexpected that challenges our assumptions.
5. **Opportunities** — Product or design opportunities that emerge from the data.
6. **Confidence Level** — How confident should we be in these findings? Flag where more research is needed.

Preserve the user's voice — use direct quotes where they're powerful. Distinguish between what users said vs. what you're inferring. Be honest about thin data.

Tips

Don't worry about cleaning up your notes before pasting them in. Messy is fine — the skill is designed for raw input.
If you have notes from multiple sources (interviews + support tickets + survey), label them so the synthesis can distinguish between them.
Run this after each batch of interviews to build up a living insights library over time.