Zsun79/LitReviewSkill / skills/write-literature-review
write-literature-review
VerifiedIterative literature-review workflow for a research topic. Use this skill to draft up to 10 search keywords, build a seed set from OpenAlex title-and-abstract matches, expand by backward and forward citations, screen candidates by title and abstract, repeat until no new relevant papers remain, rank the final set, inspect up to 30 full texts, build a concept-reference knowledge graph, and write a literature review grounded only in the final included references.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 5.5 KB |
| agents/openai.yaml | config | 238 B |
| references/citation format/APA.md | markdown | 846 B |
| references/citation format/Chicago Author-Date.md | markdown | 903 B |
| references/citation format/Harvard.md | markdown | 938 B |
| references/citation format/IEEE.md | markdown | 808 B |
| references/citation format/MLA.md | markdown | 723 B |
| references/citation format/Vancouver.md | markdown | 748 B |
| references/review_template.md | markdown | 2.2 KB |
| references/review_writing.md | markdown | 4.0 KB |
| references/workflow.md | markdown | 8.7 KB |
| references/workflow_logging.md | markdown | 3.2 KB |
| scripts/build_knowledge_graph.py | script | 7.7 KB |
| scripts/lit_review_pipeline.py | script | 30.0 KB |
references/review_template.md
View on GitHub# Title
## Abstract
- Briefly state the topic, scope, and purpose of the review
- Summarize key themes or findings
- Highlight the main insight or contribution
---
## 1. Introduction
- Introduce the research area and its importance
- Provide necessary background context
- Identify key problems, debates, or gaps in the field
- State the purpose and scope of the review
- Outline the structure of the paper
---
## 2. Background and Key Concepts
- Define essential terms and concepts
- Provide theoretical or historical context if needed
- Clarify how terms are used in this review
---
## 3. Conceptual Framework / Organization of the Literature
- Explain how the literature is organized (e.g., by themes, methods, theories, time periods)
- Justify this structure
- Provide a roadmap for the main sections
---
## 4. Review of the Literature
### 4.1 Theme / Category A
- Describe the main idea or approach
- Summarize representative studies (grouped, not one-by-one)
- Highlight common methods, findings, or arguments
- Discuss strengths and limitations
### 4.2 Theme / Category B
- Same structure as above
### 4.3 Theme / Category C
- Same structure as above
*(Add more sections as needed)*
---
## 5. Synthesis and Comparative Analysis
- Compare different themes, approaches, or schools of thought
- Identify patterns, consistencies, and contradictions
- Discuss relationships between different strands of research
- Highlight overall trends in the literature
---
## 6. Critical Evaluation
- Assess the quality and robustness of existing research
- Identify methodological limitations or biases
- Evaluate the strength of evidence and arguments
- Discuss what is well-established vs. uncertain
---
## 7. Research Gaps
- Identify areas that are underexplored or unresolved
- Point out limitations in current knowledge
- Explain why these gaps matter
---
## 8. Future Directions
- Suggest promising directions for future research
- Propose improvements in methods, theory, or data
- Connect future work to identified gaps
---
## 9. Conclusion
- Summarize key insights from the review
- Reiterate the main contribution of the paper
- Emphasize the significance of the topic
---
## References
- List all cited works in a consistent academic formatRelated skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |