obsidian-literature-workflow
The obsidian-literature-workflow skill manages project-scoped literature review pipelines within Obsidian, directing paper sources through knowledge synthesis to writing outputs. Use this skill to organize literature notes, extract validated claims with evidence records, identify research gaps, and generate related-work drafts and comparison matrices that flow from curated source materials into structured writing artifacts.
git clone --depth 1 https://github.com/Galaxy-Dawn/claude-scholar /tmp/obsidian-literature-workflow && cp -r /tmp/obsidian-literature-workflow/skills/obsidian-literature-workflow ~/.claude/skills/obsidian-literature-workflowSKILL.md
# Obsidian Literature Workflow
This skill owns the **project literature workflow**.
## Main flow
```text
Sources/Papers/ -> Knowledge/ -> Writing/ -> Maps/literature.canvas
```
## Default outputs
- `Sources/Papers/{paper-slug}.md`
- `Knowledge/Literature Overview.md`
- `Knowledge/Method Taxonomy.md`
- `Knowledge/Research Gaps.md`
- `Knowledge/Claim Map.md`
- `Writing/related-work-draft.md` only after promoted claims pass the evidence gate
- `Writing/comparison-matrix.md` only after promoted claims pass the evidence gate
- `Maps/literature.canvas`
## Rules
- paper notes stay under `Sources/Papers/`
- literature synthesis does not live inside source notes
- every synthesis note must link its supporting source notes
- every research gap must carry evidence
- every promoted claim must carry an Evidence Record ID, source type, claim strength, allowed wording, and forbidden stronger wording when it may flow into writing or rebuttal
- weak paper notes, abstract-only pages, and webpage placeholders may update coverage or `To-Read`, but they cannot support `Knowledge` or `Writing` conclusions
- default graph output is `Maps/literature.canvas`
- do not generate extra canvases unless explicitly requested
## Read next
- `references/PAPER-NOTE-SCHEMA.md`
- `references/LITERATURE-OVERVIEW.md`
- `references/CLAIM-EXTRACTION.md`
- `references/METHOD-TAXONOMY.md`
- `references/RESEARCH-GAPS.md`
- `references/LITERATURE-CANVAS.md`Expert code review specialist. Proactively reviews code for quality, security, and maintainability. Use immediately after writing or modifying code. MUST BE USED for all code changes.
Use this agent when the user provides a Kaggle competition URL or asks to learn from Kaggle winning solutions. Examples:
Use this agent when the user asks to "conduct literature review", "search for papers", "analyze research papers", "identify research gaps", "review related work", or mentions starting a research project. This agent integrates with Zotero for automated paper collection, organization, and full-text analysis. Examples:
Use this agent when the user provides a research paper (PDF/DOCX/arXiv link) or asks to learn writing patterns from papers, extract venue-specific writing signals, study paper structure, or mine rebuttal strategies. The agent writes extracted knowledge into the active installed paper-miner writing memory for ml-paper-writing. It does not maintain project-specific writing memory.
Use this agent when the user asks to "write rebuttal", "respond to reviewers", "analyze review comments", or needs help with academic paper review response. This agent specializes in systematic rebuttal writing with professional tone and structured responses.
Test-driven development guide for writing tests first, implementing the smallest passing change, and keeping verification tight. Use when the user explicitly wants TDD or when a task should be driven by failing tests before code.
Run a blocker-first post-experiment workflow: validate evidence, produce strict statistical analysis when possible, and generate a decision-oriented results report only when the analysis bundle is sufficient. Uses results-analysis + results-report as a gated two-stage workflow.
Commit changes following Conventional Commits format (local only, no push).