obsidian-literature-workflow

Organizes project literature reviews in Obsidian from paper notes to synthesis and canvas graphs.

Updated Mar 23, 2026
One-click install
npx skills add https://github.com/hanasho744/codex --skill obsidian-literature-workflow-hanasho744
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: obsidian-literature-workflow
Source: https://github.com/hanasho744/codex/tree/main/.agents/skills/obsidian-literature-workflow
Command: npx skills add https://github.com/hanasho744/codex --skill obsidian-literature-workflow-hanasho744

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Managing a project-scoped literature review in Obsidian often leads to scattered paper notes, unsupported claims, and synthesis that loses track of its sources. This Skill enforces a structured pipeline from Sources/Papers through Knowledge synthesis to Writing handoff, with an evidence gate so only claims backed by evidence records reach drafts. ## Core Features & Use Cases - Structured paper notes and claim extraction: Paper notes live under Sources/Papers with a defined schema, and claims carry claim type, strength, evidence, limitations, and project relevance. - Evidence-gated synthesis: Literature overview, method taxonomy, research gaps, and claim maps are generated in Knowledge, and writing artifacts like related-work drafts are produced only after claims pass the evidence gate. - Literature canvas generation: A Python script builds Maps/literature.canvas as an argument map with paper, claim, method, and gap nodes grouped by subfield, plus a legacy Mermaid graph option. - Use Case: After importing a batch of Zotero paper notes, run the workflow to refresh synthesis notes and regenerate the literature canvas so the project graph reflects the latest reading. ## Quick Start Ask the assistant to run the obsidian-literature-workflow to build the literature canvas and refresh the Knowledge synthesis notes for the current project.

Frequently Asked Questions about obsidian-literature-workflow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build a literature canvas in Obsidian from paper notes?▼

Run the build_literature_canvas.py script against your project root. It reads paper notes under Sources/Papers, parses frontmatter and wikilinks, and writes an argument-map canvas to Maps/literature.canvas with paper, claim, method, and gap nodes.

How do I structure literature review notes in Obsidian?▼

Keep paper notes under Sources/Papers using the paper note schema with metadata, claims, methods, evidence, and limitations. Synthesis such as literature overviews, method taxonomies, and research gaps belongs in Knowledge and must link back to supporting paper notes.

What is an evidence gate in a literature review workflow?▼

An evidence gate requires every promoted claim to carry an evidence record ID, source type, claim strength, and allowed wording before it can flow into writing or rebuttal. Weak notes like abstract-only pages can update coverage but cannot support Knowledge or Writing conclusions.

Can I generate a Mermaid literature graph instead of a canvas?▼

Yes, the build_literature_graph.py script produces a legacy Mermaid-based map note at Knowledge/Literature-Map.md. The canvas at Maps/literature.canvas is the default, and the Mermaid note is kept only for backwards compatibility.

When should I refresh the Obsidian literature canvas?▼

Refresh the canvas after new Zotero-sourced paper notes are added, when paper notes gain new linked_knowledge edges or wikilinks, after synthesis notes are updated, or after a batch ingestion or normalization pass changes many relationships.