Skip to content
cccskills
FreePublished on GitHub

obsidian-literature-workflow

Organizes project literature reviews in Obsidian, turning paper notes into linked summaries, method categories, research gaps, and a visual map. Writing drafts and comparison tables follow only when claims meet the required evidence checks.

OriginalShow the original 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.

Run score Not tested

See how to install

Good for

  • Organizing paper notes for a research project
  • Comparing methods across papers
  • Identifying research gaps supported by evidence
  • Preparing a related-work draft from supported claims

Files included (11)

  • SKILL.md1.7 KB
  • references/CANVAS-WORKFLOW.md1.7 KB
  • references/CLAIM-EXTRACTION.md2.0 KB
  • references/GRAPH-WORKFLOW.md768 B
  • references/LITERATURE-CANVAS.md145 B
  • references/LITERATURE-OVERVIEW.md132 B
  • references/METHOD-TAXONOMY.md137 B
  • references/PAPER-NOTE-SCHEMA.md163 B
  • references/RESEARCH-GAPS.md106 B
  • scripts/build_literature_canvas.py22.6 KB
  • scripts/build_literature_graph.py9.4 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

agent-identifier

FreeSummary

Create and configure Claude Code agents using Markdown files with YAML configuration headers. Define when each agent should run, write its responsibilities and workflow, choose models and tools, and check configuration and triggering behavior.

  • Create a Claude Code subagent
  • Define triggering conditions with concrete examples
  • Configure an agent's model, color, and tools
Galaxy-Dawn/claude-scholar5.9KUpdated Oct 19, 2026

Add datasets, models, and other components to machine learning projects using consistent registration and creation patterns. The skill guides file placement, configuration, and automatic module loading so new components fit the project's established architecture.

  • Adding a registered Dataset class
  • Creating a model driven by configuration
  • Wiring registration and creation logic in a new module
Galaxy-Dawn/claude-scholar5.9KUpdated Oct 19, 2026

bug-detective

FreeSummary

Investigate code errors through a structured process using reproduction steps, logs, and testable explanations. The workflow guides fault isolation, fixes, and follow-up checks, with common error patterns for Python, JavaScript/TypeScript, and Bash/Zsh.

  • Investigating an error using logs and reproduction steps
  • Finding why code broke after a recent change
  • Troubleshooting common shell script errors
Galaxy-Dawn/claude-scholar5.9KUpdated Oct 19, 2026

Check academic references for existence, accurate publication details, and support for the claims being cited. This guide explains how to verify sources, obtain bibliography entries, and flag references that cannot be confirmed.

  • Checking references suggested by AI
  • Verifying authors, titles, and publication years
  • Checking whether a paper supports a cited claim
Galaxy-Dawn/claude-scholar5.9KUpdated Oct 19, 2026

Review code changes and pull requests for correctness, security, performance, and test quality. The skill helps prioritize issues, write specific and constructive feedback, and create shared review checklists and standards for a development team.

  • Reviewing code changes and pull requests
  • Writing review comments with clear priorities and fixes
  • Creating shared review checklists for a team
Galaxy-Dawn/claude-scholar5.9KUpdated Oct 19, 2026

Create reusable slash commands, prompts invoked by typing a slash, for Claude Code. The skill explains Markdown structure, arguments, file references, tool permissions, and plugin integration so recurring tasks can follow a defined workflow.

  • Turning recurring prompts into slash commands
  • Creating review commands with arguments and file references
  • Sharing project-specific commands with a team
Galaxy-Dawn/claude-scholar5.9KUpdated Oct 19, 2026

See all skills by Galaxy-Dawn

Report a problem with this skill