/obsidian-literature-workflow
Use this skill for project-scoped literature review built on Sources/Papers, with synthesis landing in Knowledge, writing handoff in Writing, and the default literature canvas under Maps/literature.canvas.
$ npx -y skills add Galaxy-Dawn/claude-scholar --skill obsidian-literature-workflow --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/obsidian-literature-workflow
Context preview
The summary Claude sees to decide when to auto-load this skill.
Use this skill for project-scoped literature review built on Sources/Papers, with synthesis landing in Knowledge, writing handoff in Writing, and the default literature canvas under Maps/literature.canvas.
SKILL.md
obsidian-literature-workflow.SKILL.mdname: obsidian-literature-workflow
description: Use this skill for project-scoped literature review built on Sources/Papers, with synthesis landing in Knowledge, writing handoff in Writing, and the default literature canvas under Maps/literature.canvas.
version: 1.0.0
Obsidian Literature Workflow
This skill owns the **project literature workflow**.
Main flow
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`
Read more
name: obsidian-literature-workflow description: Use this skill for project-scoped literature review built on Sources/Papers, with synthesis landing in Knowledge, writing handoff in Writing, and the default literature canvas under Maps/literature.canvas. version: 1.0.0
Obsidian Literature Workflow
This skill owns the **project literature workflow**.
Main flow
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`
Semi-automated research assistant for academic research and software development. Supports Claude Code, Codex CLI, Kimi Code CLI, and OpenCode across ideation, coding, experiments, writing, and publication.
Repo: Galaxy-Dawn/claude-scholar
Other skills on claude-scholar.
- /agent-identifier
Use when creating or configuring Claude Code agents and their frontmatter.
Open skill - /architecture-design
Use only when creating new registrable ML components that require Factory or Registry patterns.
Open skill - /bug-detective
This skill should be used when the user asks to "debug this", "fix this error", "investigate this bug", "troubleshoot this issue", "find the problem", "something is broken", "this isn't working", "why is this failing", or reports errors/exceptions/bugs. Provides systematic
Open skill - /citation-verification
This skill provides reference guidance for citation verification in academic writing. Use when the user asks about "citation verification best practices", "how to verify references", "preventing fake citations", or needs guidance on citation accuracy. This skill supports
Open skill - /code-review-excellence
This skill should be used when the user asks to review a diff or pull request, write review comments, audit code quality, establish review standards, or improve how a team performs code review.
Open skill - /command-development
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in
Open skill

