[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M751JVTN5JM74AM3ND85M3BJ":3,"skill-same:01M751JVTN5JM74AM3ND85M3BJ":49},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":31,"ownerHtmlUrl":32,"ownerBlogUrl":31,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M751JVTN5JM74AM3ND85M3BJ","research-synthesis",null,"Turns many sources into a decision-ready synthesis - atomic claims clustered into named themes, surfaced tensions between sources, gaps no source answers, and explicit so-what\u002Fnow-what implications with confidence ratings. Use when someone says \"synthesize this research\", \"what do all these reports agree on\", \"pull the themes out of these articles\", or has a pile of sources and needs conclusions rather than source-by-source summaries. Do NOT use for synthesizing user interview transcripts - use interview-synthesis instead; for a formal academic literature review, use literature-review.","SkillMedev\u002Fskills","SkillMedev","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F298078254?v=4","01M74ZSGTQ918CB0VXW4EG3RMX","SkillMe","01M74ZSGVBT497NA95CBT8JTY4",25,"MIT","https:\u002F\u002Fgithub.com\u002FSkillMedev\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch-synthesis\u002FSKILL.md",[],[],"2026-11-11 18:21:06",false,"---\nname: research-synthesis\ndescription: Turns many sources into a decision-ready synthesis - atomic claims clustered into named themes, surfaced tensions between sources, gaps no source answers, and explicit so-what\u002Fnow-what implications with confidence ratings. Use when someone says \"synthesize this research\", \"what do all these reports agree on\", \"pull the themes out of these articles\", or has a pile of sources and needs conclusions rather than source-by-source summaries. Do NOT use for synthesizing user interview transcripts - use interview-synthesis instead; for a formal academic literature review, use literature-review.\nmetadata:\n  title: \"Research Synthesis\"\n---\n\n# Research Synthesis\n\nSynthesis is not summary. A summary repeats what each source said; a synthesis finds\nthe patterns *across* sources and says what it means. This skill turns 20+ sources into\na decision-ready document.\n\n## Step 1: Capture, don't just read\n\nAs you go through each source, extract atomic notes (one idea per note):\n\n```\nSource: \u003Cauthor, title, date>\nClaim: \u003Ca single finding or argument, in your own words>\nEvidence: \u003Cwhat backs it - data, study, anecdote>\nConfidence: \u003Cstrong \u002F moderate \u002F weak>\n```\n\nKeep claims atomic so you can later regroup them across sources. Tag each with a topic.\n\n## Step 2: Cluster into themes\n\nLay all the claims out and group them by what they're *about*, regardless of source.\nPatterns emerge when ideas from different authors sit together. Name each cluster with\na **theme** - a sentence that captures the shared insight, not just a topic word.\n\n```\nTheme: \"Remote teams ship faster but report weaker belonging.\"\n  - [Source A] productivity up 12% remote\n  - [Source C] async cuts cycle time\n  - [Source B] belonging scores down in fully-remote orgs\n```\n\n## Step 3: Find tensions and disagreements\n\nThe most valuable output is where sources **conflict**. For each tension:\n- State both positions and who holds them.\n- Hypothesize *why* they differ (different populations? definitions? time periods? incentives?).\n- Note what evidence would resolve it.\n\nDon't paper over disagreement - surfacing it is the point.\n\n## Step 4: Identify gaps\n\nWhat's **missing**? Note:\n- Questions no source answers.\n- Weakly-supported claims everyone repeats (an echo, not evidence).\n- Populations \u002F contexts not studied.\n\nGaps tell the reader where to be cautious and where new research\u002Fwork is needed.\n\n## Step 5: Write the \"so what\"\n\nEnd every theme and the document overall with implications:\n\n- **So what?** - why does this matter for the decision at hand?\n- **Now what?** - what should we do given this? Concrete recommendations.\n\nA synthesis that doesn't reach \"so what\" is just organized note-taking.\n\n## Output structure\n\n```\n# Synthesis: \u003Cquestion>\n\n## Executive summary (the so-what, up front)\n## Themes\n  ### Theme 1 - \u003Cinsight sentence>\n    Evidence: [sources]. So what: \u003C...>\n## Tensions & disagreements\n## Gaps & open questions\n## Implications & recommendations\n## Source list with confidence ratings\n```\n\n## Tips\n\n- **Synthesize across, not down** - organize by theme, never source-by-source.\n- **Weight by quality** - three weak blog posts don't outweigh one rigorous study.\n- **Quote sparingly**; paraphrase into your shared framework.\n- **Show your confidence** so readers can calibrate.\n\n## Anti-patterns\n\n- A list of source summaries with a conclusion bolted on - that's not synthesis.\n- Ignoring disagreement to present a tidy narrative.\n- Treating volume of mentions as truth - popularity isn't evidence.\n- Stopping at \"what\" without \"so what \u002F now what\".\n","# Research Synthesis\n\nSynthesis is not summary. A summary repeats what each source said; a synthesis finds\nthe patterns *across* sources and says what it means. This skill turns 20+ sources into\na decision-ready document.\n\n## Step 1: Capture, don't just read\n\nAs you go through each source, extract atomic notes (one idea per note):\n\n```\nSource: \u003Cauthor, title, date>\nClaim: \u003Ca single finding or argument, in your own words>\nEvidence: \u003Cwhat backs it - data, study, anecdote>\nConfidence: \u003Cstrong \u002F moderate \u002F weak>\n```\n\nKeep claims atomic so you can later regroup them across sources. Tag each with a topic.\n\n## Step 2: Cluster into themes\n\nLay all the claims out and group them by what they're *about*, regardless of source.\nPatterns emerge when ideas from different authors sit together. Name each cluster with\na **theme** - a sentence that captures the shared insight, not just a topic word.\n\n```\nTheme: \"Remote teams ship faster but report weaker belonging.\"\n  - [Source A] productivity up 12% remote\n  - [Source C] async cuts cycle time\n  - [Source B] belonging scores down in fully-remote orgs\n```\n\n## Step 3: Find tensions and disagreements\n\nThe most valuable output is where sources **conflict**. For each tension:\n- State both positions and who holds them.\n- Hypothesize *why* they differ (different populations? definitions? time periods? incentives?).\n- Note what evidence would resolve it.\n\nDon't paper over disagreement - surfacing it is the point.\n\n## Step 4: Identify gaps\n\nWhat's **missing**? Note:\n- Questions no source answers.\n- Weakly-supported claims everyone repeats (an echo, not evidence).\n- Populations \u002F contexts not studied.\n\nGaps tell the reader where to be cautious and where new research\u002Fwork is needed.\n\n## Step 5: Write the \"so what\"\n\nEnd every theme and the document overall with implications:\n\n- **So what?** - why does this matter for the decision at hand?\n- **Now what?** - what should we do given this? Concrete recommendations.\n\nA synthesis that doesn't reach \"so what\" is just organized note-taking.\n\n## Output structure\n\n```\n# Synthesis: \u003Cquestion>\n\n## Executive summary (the so-what, up front)\n## Themes\n  ### Theme 1 - \u003Cinsight sentence>\n    Evidence: [sources]. So what: \u003C...>\n## Tensions & disagreements\n## Gaps & open questions\n## Implications & recommendations\n## Source list with confidence ratings\n```\n\n## Tips\n\n- **Synthesize across, not down** - organize by theme, never source-by-source.\n- **Weight by quality** - three weak blog posts don't outweigh one rigorous study.\n- **Quote sparingly**; paraphrase into your shared framework.\n- **Show your confidence** so readers can calibrate.\n\n## Anti-patterns\n\n- A list of source summaries with a conclusion bolted on - that's not synthesis.\n- Ignoring disagreement to present a tidy narrative.\n- Treating volume of mentions as truth - popularity isn't evidence.\n- Stopping at \"what\" without \"so what \u002F now what\".\n",{"name":5,"metadata":24,"description":7},{"title":25},"Research Synthesis","main","97a13607d669157a4a16d5ba79b77f208319f7b9","skills\u002Fresearch-synthesis",3,"https:\u002F\u002Fgithub.com\u002FSkillMedev\u002Fskills","https:\u002F\u002Fskillme.dev","https:\u002F\u002Fgithub.com\u002FSkillMedev","MCP-native catalog of Claude Agent Skills. Browse, recommend, install, and auto-apply skills in chat. Open source, every skill free and clonable on GitHub.","2026-10-14 03:19:31",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add SkillMedev\u002Fskills --skill research-synthesis",{"tool":41,"command":42},"bunx","bunx skills add SkillMedev\u002Fskills --skill research-synthesis",{"tool":44,"command":45},"pnpm","pnpm dlx skills add SkillMedev\u002Fskills --skill research-synthesis","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSkillMedev\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch-synthesis\u002FSKILL.md",true,[],[50,58,65,72,79,86],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":57},"01M75271B256DF3FX2VG5VRYEE","zone-2-cardio-plan","Use when someone asks to build a steady-state cardio plan, train an aerobic base or Zone 2, structure easy or endurance weekly cardio, train by heart-rate zones, or improve resting heart rate, VO2, or endurance. Builds a heart-rate-zone aerobic training block with session structure, modality choice, and progression. General fitness guidance, not medical advice. Do NOT use to design a strength or lifting program (use Strength Training Plan), high-intensity interval conditioning, HIIT, or circuits (use Conditioning & HIIT Program), or a mobility\u002Fflexibility routine (use Mobility Routine).","https:\u002F\u002Fgithub.com\u002FSkillMedev\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fzone-2-cardio-plan\u002FSKILL.md",[],[],"2026-11-11 18:27:18",{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":57},"01M7526VP1QBBKYBE17S1WR86Y","youtube-script-writer","Writes retention-engineered long-form YouTube scripts on a hook\u002Fbody\u002Fpayoff architecture - a first-30-seconds hook that survives the retention cliff, a beat-sheet body with mini-hooks and bridges, timed pattern interrupts, and a payoff that over-delivers - with B-roll and editing cues marked inline. Use when someone says \"script my next video\", \"my retention graph dies at the start\", \"tighten this draft\", or \"outline a video on X\". Do NOT use for the 3-second opener of TikTok, Reels, or Shorts - use video-hook-writer instead; do NOT use for spoken voiceover synced to on-screen tutorial actions - use narration-script instead; do NOT use for a sales demo built on a buyer's discovery notes - use demo-script instead; do NOT use to design the thumbnail and title - use thumbnail-concept instead.","https:\u002F\u002Fgithub.com\u002FSkillMedev\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fyoutube-script-writer\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":57},"01M7526P2T0WKMHDXS4Q58237T","win-back-campaign","Designs segmented win-back email sequences for dormant users - dormancy tiers, a three-beat sequence with a single proportional incentive, and a suppression rule - and measures success by re-activation, not opens. Use when someone says \"our users went quiet\", \"design a win-back campaign\", \"how do I re-engage lapsed customers\", \"should we email people who haven't logged in for months\", or lifecycle messaging has stopped landing with a lapsed segment. Do NOT use for recovering an unfinished checkout - use abandoned-cart-sequence instead. Do NOT use for diagnosing and fixing why active customers cancel - use churn-reduction instead. Do NOT use for building always-on onboarding or nurture flows - use email-drip-builder instead.","https:\u002F\u002Fgithub.com\u002FSkillMedev\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fwin-back-campaign\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":57},"01M7526HF2RCDJ50P93WRZRHVV","wikipedia-style","Writes neutral, verifiable, encyclopedic prose following Wikipedia's core content policies and manual of style - NPOV, inline citations, notability-backed claims, and a strict ban on promotional language. Use when someone asks \"write this like a Wikipedia article\", \"draft a Wikipedia page for this company or person\", \"make this neutral and encyclopedic\", or \"why does my article draft keep getting rejected\". Do NOT use for persuasive or opinion writing - use op-ed-writer instead; for thesis-driven academic papers, use academic-essay; for verifying claims in existing text, use fact-checker.","https:\u002F\u002Fgithub.com\u002FSkillMedev\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fwikipedia-style\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":57},"01M7526D43CTGRKGKNQ2GB0KVX","whitepapers","Structures and writes authoritative B2B whitepapers - a standalone executive summary, a data-sized problem statement, methodology, evidence-driven findings, recommendations, and a soft call to action - flagging every claim that needs a real citation. Use when a marketer asks \"write a whitepaper on this topic\", \"turn our research into a lead-gen asset\", \"make this credible enough for executives\", or a draft reads like a product pitch instead of analysis. Do NOT use for customer-story-driven proof - use case-study-builder instead; for policy audiences, use policy-brief.","https:\u002F\u002Fgithub.com\u002FSkillMedev\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fwhitepapers\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":57},"01M75268423Y3K50SY5WC2NX2G","white-space-analysis","Finds unmet market gaps by ranking jobs-to-be-done on importance versus satisfaction, overlaying them against current solutions and workarounds, and validating that each gap is real, winnable, and worth winning. Use when someone asks \"where are the gaps in this market\", \"what's underserved here\", \"where should we play next\", or is hunting for product, feature, or market-entry opportunities. Do NOT use for profiling competitors and building battle cards - use competitive-intelligence instead; for putting a dollar figure on an identified opportunity - use market-sizing instead; for extracting jobs-to-be-done from raw customer interviews - use jtbd-extractor instead.","https:\u002F\u002Fgithub.com\u002FSkillMedev\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fwhite-space-analysis\u002FSKILL.md",[],[]]