본문으로 건너뛰기
cccskills
무료GitHub에 공개

literature-review

Write a literature review. Use when the user says "literature review", "lit review", "review the literature", "summarize prior research", "what does the research say about", "synthesize research on", "background section", "related work section", "what has been studied on this topic", or needs to systematically identify, synthesize, and critically evaluate existing research on a topic - even if they don't explicitly say "literature review".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

실행 점수 미검증

설치 방법 보기

포함된 파일(1)

  • SKILL.md6.1 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Overview

Based on Research Design (Creswell & Creswell) and Research Methods in Education (Cohen, Manion & Morrison). A literature review is not a list of summaries - it is a critical synthesis that builds the case for your research question. Creswell's standard: the literature review should justify why your study is needed by showing what is known, what is contested, and what gap remains.

The test: after reading the literature review, does the reader understand why this specific research question matters and has not been adequately answered before?

Workflow

Step 1: Define the review scope

Before writing, establish the boundaries:

Research question or topic: [the specific question being investigated]
Time range: [e.g. 2010–2024, or "foundational works from 1980s onward"]
Disciplines included: [e.g. cognitive psychology, education research, HCI]
Disciplines excluded: [e.g. clinical medicine, economics]
Source types: [peer-reviewed journals / conference papers / books / grey literature]
Databases searched: [Google Scholar / PubMed / IEEE Xplore / JSTOR / etc.]
Search terms: [list primary and secondary keywords used]
Inclusion criteria: [what makes a study relevant]
Exclusion criteria: [what disqualifies a study]
Number of sources reviewed: [total found vs. total included]

Step 2: Organize by theme, not by author

Do not write "Smith (2019) found X. Jones (2020) found Y. Lee (2021) found Z." Organize by what the research says, then attribute:

Structure options:

  • Thematic: group by concept or finding ("Three perspectives on X have emerged...")
  • Chronological: use only when the evolution of ideas is itself the argument
  • Methodological: when comparing what different research methods reveal
  • Conceptual: when mapping the theoretical frameworks in a field

Step 3: Write the introduction

Set the context and state what the review covers:

[Introduce the topic and why it matters - 1 paragraph]
[State the scope of the review - what is and isn't covered]
[Preview the structure - "This review first examines X, then Y, before identifying the gap that motivates the present study"]

Step 4: Synthesize each theme

For each theme:

  1. State the consensus or dominant finding
  2. Present supporting evidence (cite multiple sources, not one)
  3. Identify contradictions or limitations in the literature
  4. Explain what remains unresolved

Template per theme:

[Theme heading]

The predominant view is that [consensus finding] (Author A, year; Author B, year; Author C, year).
[1-2 sentences elaborating the finding with specific detail]

However, this consensus is challenged by [contrasting finding] (Author D, year; Author E, year).
[Explain the tension: different populations? different methods? different operationalizations?]

Methodologically, most studies in this area [limitation, e.g. rely on self-report measures /
use small convenience samples / are conducted in Western WEIRD populations], which limits
generalizability to [context of your study].

The specific question of [your research angle] remains underexplored. [Cite the one or two
closest prior attempts, and explain why they don't fully answer your question.]

Step 5: Write the gap statement

This is the most important paragraph in the review. It must:

  • Acknowledge what IS known
  • Precisely name what is NOT known
  • Explain why that gap matters
  • Position your study as the logical next step
While substantial research has established [what is known], the literature has not
adequately addressed [specific gap]. Existing studies have either [limitation A] or
[limitation B]. To date, no study has examined [your specific angle] in [your context /
population / method]. This gap is consequential because [why it matters practically or
theoretically]. The present study addresses this gap by [brief description of your approach].

Step 6: Summarize and transition

Close the review with:

  1. A 3-5 sentence synthesis of the major themes
  2. A restatement of the gap
  3. A transition to your research question or hypotheses

Anti-Patterns

1. Annotated bibliography disguised as literature review Bad: Para 1 = summary of Smith. Para 2 = summary of Jones. Para 3 = summary of Lee. Good: Para 1 = consensus finding with Smith, Jones, Lee as evidence. Para 2 = contradictions with Davis and Patel as evidence.

2. Gap statement that's too vague Bad: "More research is needed in this area." Good: "No study has examined the relationship between X and Y in [specific population], despite theoretical predictions that [mechanism] should produce [effect]."

3. Only citing supportive literature Bad: Every source confirms the same point. Good: Literature review actively seeks and presents contradictory findings. Addressing them strengthens, not weakens, your argument.

4. Methodology ignored Bad: Treat all findings as equal regardless of study design. Good: Note when findings come from RCTs vs. correlational studies, large samples vs. small, and what that means for confidence in the conclusion.

Quality Checklist

  • Scope explicitly defined (time range, disciplines, databases, search terms)
  • Organized by theme, not by author
  • Each theme presents consensus, contradictions, and limitations
  • Citations support claims with multiple sources, not single authorities
  • Study quality and methodology noted where relevant
  • Gap statement names specifically what is unknown, not just that "more research is needed"
  • Gap is linked to why it matters (theoretical or practical significance)
  • Review closes with a clear transition to the research question or hypotheses
  • All claims have citations; no uncited assertions about what "research shows"

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Rate any product, feature, or experience on the 11-star scale (Brian Chesky's Airbnb thought experiment). Use when user says "rate this experience", "11-star", "star rating", "experience audit", "how good is this", "experience rating", "product audit", "quality assessment", or wants to evaluate product quality and identify improvement paths. Also trigger when user wants to benchmark a feature, assess where a product stands, or map out what "great" looks like - even if they don't explicitly say "11-star".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

qa-aman/claude-skills212026년 10월 19일 업데이트

Generate A/B copy variants grounded in Eugene Schwartz's awareness and market-sophistication stages and John Caples' tested-headline discipline. Every variant declares its angle, the awareness stage it targets, and a falsifiable hypothesis, and the skill recommends which pair to test first and what delta counts as signal. Use when the user says "A/B test this", "write variants", "give me options", "test different angles", "copy variants", "ab copy", "test this headline", "multiple versions", "which version is better", or wants to test copy before publishing. For reviewing copy that already exists, see copy-review. For sample size and stopping rules, see growth-experiment. For diagnosing a page rather than its words, see page-cro. For full paid ad sets by platform, see ad-campaign-writer.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

qa-aman/claude-skills212026년 10월 19일 업데이트

Design statistically rigorous experiments to test data science hypotheses. Use when the user says "design an A/B test", "run an experiment", "test this hypothesis", "is this difference significant", "how many samples do I need", "randomized controlled trial", "causal inference", "uplift test", "holdout group", "significance test", "power calculation", "avoid p-hacking", or needs to determine whether an observed effect is real before making a product or model decision. For lean build-measure-learn product experiments without the statistics, use experiment-design instead.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

qa-aman/claude-skills212026년 10월 19일 업데이트

Write measurable acceptance criteria for requirements or user stories. Use when the user says "write acceptance criteria", "definition of done", "how do we test this", "fit criteria", "given when then", "Gherkin scenarios", "what does done look like", "testable conditions", "how will we know this works" - even if they don't explicitly say "acceptance criteria".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

qa-aman/claude-skills212026년 10월 19일 업데이트

Build a strategic account plan for winning, retaining, or expanding a named account. Use when the user says "build an account plan", "strategic account planning", "how do I grow this account", "account expansion strategy", "whitespace analysis", "QBR prep", "key account review", "map the stakeholders in this account", "land and expand plan", "how do I break into [company]", or wants a structured strategy for a specific account.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

qa-aman/claude-skills212026년 10월 19일 업데이트

Write paid ad copy for LinkedIn, Google, Meta, and YouTube. Produces multiple variants per platform, each targeting a different Eugene Schwartz awareness level and Cialdini persuasion principle. Use when the user asks for ad copy, ad variants, "write LinkedIn ads", Google ads, Meta ads, paid social copy, ad headlines, or wants creative for a paid campaign. Reads brand voice, ICP, and positioning from knowledge/. For organic social posts, see linkedin-post or social-calendar. For the landing page the ad points at, see landing-page-writer. For testing variants, see ab-copy-writer.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

qa-aman/claude-skills212026년 10월 19일 업데이트

qa-aman의 스킬 모두 보기

이 스킬의 문제 신고