.claude/skills/lit-review/SKILL.md
Structured literature search and synthesis with citation extraction and gap identification
npx skillsauth add pedrohcgs/claude-code-my-workflow lit-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.
Conduct a structured literature search and synthesis on the given topic.
Input: $ARGUMENTS — a topic, paper title, research question, or phenomenon to investigate.
Parse the topic from $ARGUMENTS. If a specific paper is named, use it as the anchor.
Search for related work using available tools:
master_supporting_docs/supporting_papers/ for uploaded papersWebSearch to find recent publications (if available)WebFetch to access working paper repositories (if available).bib file for papers already in the projectOrganize findings into these categories:
Identify gaps and opportunities:
Extract citations in BibTeX format for all papers discussed.
Save the report to quality_reports/lit_review_[sanitized_topic].md
# Literature Review: [Topic]
**Date:** [YYYY-MM-DD]
**Query:** [Original query from user]
## Summary
[2-3 paragraph overview of the state of the literature]
## Key Papers
### [Author (Year)] — [Short Title]
- **Main contribution:** [1-2 sentences]
- **Method:** [Identification strategy / data]
- **Key finding:** [Result with effect size if available]
- **Relevance:** [Why it matters for our research]
[Repeat for 5-15 papers, ordered by relevance]
## Thematic Organization
### Theoretical Contributions
[Grouped discussion]
### Empirical Findings
[Grouped discussion with comparison across studies]
### Methodological Innovations
[Methods relevant to the topic]
## Gaps and Opportunities
1. [Gap 1 — what's missing and why it matters]
2. [Gap 2]
3. [Gap 3]
## Suggested Next Steps
- [Concrete actions: papers to read, data to obtain, methods to consider]
## BibTeX Entries
```bibtex
@article{...}
---
## Important
- **Be honest about uncertainty.** If you cannot verify a citation, say so.
- **Prioritize recent work** (last 5-10 years) unless seminal papers are older.
- **Note working papers vs published papers** — working papers may change.
- **Do NOT fabricate citations.** If you're unsure about a paper's details, flag it for the user to verify.
testing
Stage, commit, push, open a PR, and merge to main. Use ONLY on explicit commit intent — user says "commit", "ship it", "push this", "open a PR", "merge to main", "let's commit this", or prefixes with `/commit`. Do NOT auto-invoke on vague end-of-task phrases ("we're done", "wrap up") — those require explicit confirmation first. Runs the standard commit-PR-merge cycle; never force-pushes or skips hooks.
testing
Perform adversarial visual audit of Quarto or Beamer slides checking for overflow, font consistency, box fatigue, and layout issues.
testing
Validate bibliography entries against citations in all lecture files. Structural checks (missing/unused entries, malformed fields) by default; `--semantic` adds citation-drift detection, DOI verification, and style-consistency checks.
testing
Translate Beamer LaTeX to Quarto RevealJS. Multi-phase workflow with TikZ extraction and QA.