Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Litreview

ASecurity

Literature review skill for academic, R&D, and professional research. Covers search strategy, source assessment (quality, relevance, recency), thematic synthesis, citation management, and the discipline of reproducible reviews. Use when conducting a systematic literature review, building a research bibliography, or preparing a research-grounded report.

847 stars
0 votes
0 copies
1 views
Added 5/29/2026
ai-agentspythongobashawsdatabase

Works with

cli

Security Analysis

A100/100

Pro scans all 7 files and shows the line behind each finding

Scanned 5/29/2026

$npx -y skills add borghei/Claude-Skills --skill litreview --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Litreview?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Litreview
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/borghei-litreview/badge)](https://www.skillsdirectory.com/skills/borghei-litreview)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: litreview
description: >
  Literature review skill for academic, R&D, and professional research.
  Covers search strategy, source assessment (quality, relevance, recency),
  thematic synthesis, citation management, and the discipline of
  reproducible reviews. Use when conducting a systematic literature
  review, building a research bibliography, or preparing a
  research-grounded report.
license: MIT + Commons Clause
metadata:
  version: 1.0.0
  author: borghei
  category: research
  domain: research
  updated: 2026-05-27
  tags: [literature-review, research, citation, synthesis, prisma, academic]
---

# Literature Review

A structured literature-review skill grounded in PRISMA-style protocols
(adapted for non-medical fields), source-assessment frameworks, and
thematic synthesis patterns.

## When to use this skill

- Conducting a **systematic literature review** on a specific question
- Building a **research bibliography** for a paper, report, or grant
- Performing a **scoping review** to map a field
- Auditing an existing review for **gaps, bias, or methodological flaws**
- Synthesizing findings from a **structured set of sources**
- Preparing a **research-grounded section** of a longer report

## Inputs the advisor expects

- Research question(s) — specific, answerable
- Inclusion / exclusion criteria
- Time bound (e.g., past 5 years)
- Geographic / domain bound
- Source types accepted (peer-reviewed, gray literature, conference)
- Existing seed sources (if any)

## Workflows

### Workflow 1 — Plan and execute the search

1. Refine the research question (PICO / PEO format works).
2. Run `search_strategy_builder.py` against the question + criteria to
   produce a search strategy (database list, queries, filters).
3. Execute searches; capture results.

```bash
python3 litreview/scripts/search_strategy_builder.py \
  --input question.json --format markdown
```

### Workflow 2 — Score source quality and relevance

1. Capture each source with metadata (authors, date, venue, methodology).
2. Run `source_quality_scorer.py` to grade each on 6 quality dimensions
   + relevance to question.
3. Triage: include / exclude / read-in-full.

```bash
python3 litreview/scripts/source_quality_scorer.py \
  --input sources.json --format markdown
```

### Workflow 3 — Synthesize findings into themes

1. Tag each source with themes + key findings.
2. Run `thematic_synthesis_builder.py` to cluster sources by theme,
   surface evidence strength, identify gaps.

```bash
python3 litreview/scripts/thematic_synthesis_builder.py \
  --input tagged_sources.json --format markdown
```

## Decision frameworks

### Search strategy — the PICO frame
- **P**opulation / problem
- **I**ntervention / phenomenon of interest
- **C**omparator (if relevant)
- **O**utcome

A well-framed question makes search and synthesis tractable.

### Inclusion / exclusion criteria
- Year range
- Language
- Source type (peer-reviewed, gray, conference, preprint)
- Methodology (empirical, theoretical, review)
- Geographic scope
- Quality threshold

Publish criteria up front; apply consistently.

### Source quality dimensions

| Dimension | Question |
|-----------|----------|
| Methodology | Is the method sound? |
| Sample / dataset | Is it adequate for the claim? |
| Peer review | Has it been peer-reviewed? |
| Reproducibility | Is data / code available? |
| Recency | Is it current? |
| Citation impact | Has it been cited / accepted? |

A single sub-dimension is rarely fatal; the combination matters.

### Synthesis approaches

| Approach | When |
|----------|------|
| Narrative synthesis | Heterogeneous sources; explanatory |
| Thematic synthesis | Multiple sources address common themes |
| Meta-analysis | Quantitative, comparable studies |
| Realist synthesis | Complex interventions; context-mechanism-outcome |
| Scoping review | Mapping a field rather than answering specific question |

For most non-clinical fields, **thematic synthesis** is the default.

## Common engagements

### "Help me build the literature review for my paper"
1. Frame the research question (PICO).
2. Define inclusion criteria.
3. Identify search databases / repositories.
4. Execute searches; deduplicate.
5. Screen titles + abstracts; full-text the candidates.
6. Tag and synthesize.
7. Write: gaps, themes, my contribution.

### "Audit my draft literature review"
1. Check the search strategy: reproducible? comprehensive?
2. Check inclusion criteria: applied consistently?
3. Check synthesis: themes substantiated?
4. Check gap identification: real gaps, or convenient?
5. Check citation balance: not over-relying on a single source / group.

### "Map the landscape of [research area]"
1. Conduct a scoping review (different from systematic).
2. Less stringent quality criteria; broader scope.
3. Goal: map the field, not answer specific question.
4. Output: themes, gaps, key authors, key venues.

## Anti-patterns to avoid

- **Search strategy that's "Google Scholar for keywords."** Not reproducible.
- **Inclusion criteria written after seeing results.** Cherry-picking.
- **Synthesizing only confirming sources.** Bias.
- **Citing without reading.** Cite chains repeat errors.
- **No quality scoring.** All sources weighted equally.
- **No gap discussion.** Reader can't see what's not known.
- **Over-reliance on one author / group / venue.** Hidden bias.
- **No PRISMA-style flow diagram (for systematic reviews).** Process opaque.

## References

- `references/search-strategy-and-prisma.md` — search patterns, PRISMA discipline
- `references/source-quality-assessment.md` — quality dimensions, common assessments
- `references/synthesis-and-citation-management.md` — synthesis approaches, citation hygiene

## Related skills

- `research/grants` — grant proposals built on literature
- `research/patent` — IP-focused literature search
- `research/dossier` — intelligence research patterns
- `product-team/research-summarizer` — synthesizing qualitative research

Attribution

borgheiborghei
View sourceSee grades on GitHubMore from borghei →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698461 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →