plugins/pm-research/skills/literature-review/SKILL.md
Structure and write a literature review for any research topic. Use when asked to write a literature review, systematic review summary, narrative review, or research background section. Produces a structured review with thematic organisation, critical analysis, and gap identification.
npx skillsauth add mohitagw15856/pm-claude-skills literature-reviewInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Structures and writes literature reviews — from background sections of a dissertation through to standalone narrative reviews for publication.
Databases: [PubMed, EMBASE, PsycINFO, etc.] Search terms: [Key terms and Boolean combinations] Inclusion criteria: Study types, population, date range, language Exclusion criteria: [List] Results: [n] identified → [n] after deduplication → [n] screened → [n] included
Organised thematically — not chronologically. Each theme = one section.
Structure per thematic section:
[Theme heading]
[Opening: state what this section covers and what evidence shows overall]
[Evidence synthesis: present what multiple studies found, compare and contrast. Do NOT summarise one paper then the next — synthesise across them: "Three studies found X (Smith, 2019; Jones, 2020; Lee, 2021), while two found Y, with the difference attributable to..."]
[Critical analysis: note methodological strengths and weaknesses — sample sizes, study designs, generalisability, risk of bias]
[Closing: transition to next theme]
| Author, year | Study design | Population | n | Key findings | Quality/Limitations | |---|---|---|---|---|---|
Well-established: [What literature consistently shows] Contested: [Areas where evidence is mixed and why] Missing: [Gaps the field needs to address] How your study addresses the gap: [If this is for a research proposal]
[3-5 sentences. Current state of knowledge and what is needed next]
For each paper: internal validity, external validity, bias types, effect size significance vs clinical significance, funding conflicts.
business
Analyze why deals are won and lost and turn it into an action plan. Use when asked to run a win/loss analysis, review closed-won and closed-lost deals, understand why the team is losing to a competitor, or summarize sales feedback into patterns. Produces a structured win/loss report with themes, win/loss rates by segment and competitor, representative quotes, and prioritized actions for product, marketing, and sales.
development
Route a fuzzy request to the right skill in this library. Use when the user is unsure which skill fits, asks 'which skill should I use for X', describes a task without naming a skill, or when a request could plausibly match several skills. Produces a best-fit recommendation with the inputs to gather, a runner-up with the tie-breaker, and a workflow recipe when the job spans multiple skills.
testing
Triage a vulnerability or scanner finding — assess real severity, exploitability, and how urgently to fix. Use when asked to triage a CVE, prioritize scanner/pentest findings, assess a vuln's risk, or decide what to patch first. Produces a triage verdict: CVSS-informed severity adjusted for your context, exploitability, real risk, a fix/mitigation, and an SLA — so you fix what matters, not just what's red.
development
Stand up a Voice of Customer (VoC) program that turns feedback into action. Use when asked to build a VoC program, design a customer feedback loop, consolidate feedback sources, or set up a closed-loop feedback process. Produces a VoC program design — objectives, feedback sources and channels, a taxonomy, collection and analysis cadence, closed-loop routing, ownership, and success metrics.