Zotero Obsidian Bridge

Galaxy-Dawn/claude-scholar/skills/zotero-obsidian-bridge

by Galaxy-Dawn903787345d6aec134086afa2b97715a78fbde519No license5.7K starsListed Oct 9, 2026Updated Oct 9, 2026Repository updated 2 weeks ago

Use this skill when Zotero is the literature source of truth and the project KB should receive source notes under Sources/Papers plus project-linked synthesis in Knowledge and Writing.

AI-generated overview

Bridges Zotero literature into an Obsidian knowledge base by creating paper notes, synthesis, and a literature map.

What it does
This skill defines a workflow that moves papers from Zotero into a project knowledge base, producing one canonical paper note per paper under Sources/Papers, literature synthesis in Knowledge, writing-oriented outputs in Writing, and a derived graph at Maps/literature.canvas. It specifies an Evidence Record format with claim strength levels and a Claim Promotion Gate that requires promoted claims to trace back to an Evidence Record ID. It also ships a verification script and reference schemas for paper notes, collection inventory, and a local Zotero fallback.
When to use it
Use it when Zotero is the source of truth for literature and a project knowledge base should receive project-local source notes and linked synthesis. It fits literature ingestion, evidence tracking, and maintaining a derived literature map in Obsidian.
Requirements
Requires access to a Zotero library and an Obsidian-style project knowledge base with the expected folder structure. It ships an executable script (scripts/verify_paper_notes.py) and reference documents; a Python runtime is implied by the script.

Zotero Obsidian Bridge

Use this skill when papers live in Zotero and the project KB should receive project-local notes.

Default flow:

text
Zotero -> Sources/Papers -> Knowledge -> Writing -> Maps/literature.canvas

Rules:

  • one canonical paper note per paper under Sources/Papers/
  • literature synthesis goes to Knowledge/
  • writing-oriented outputs go to Writing/
  • Maps/literature.canvas is the default derived graph artifact
  • update _system/registry.md, 02-Index.md, and today's Daily/ after substantial ingestion

Evidence extraction requirement

Core papers and papers with reusable claims should include an evidence record. Abstract-only or placeholder notes may stay in To-Read until there is enough evidence to extract a reusable claim.

md
## Evidence Record
Evidence ID:Source:Source type: full paper | preprint | dataset | experiment artifact | project note | abstract-only | webpage placeholderSupports:Contradicts:Method / dataset / metric:Limitation:Project relevance:Claim strength: speculative | observed | supported | strong

Use ../research-ideation/references/research-contract.md as the shared contract for Evidence Records and claim strength definitions.

Before synthesis lands in Knowledge/ or Writing/, apply the shared Claim Promotion Gate:

  • every promoted claim must point back to an Evidence Record ID,
  • source type must be strong enough for the claim,
  • abstract-only and webpage-placeholder items cannot support durable claims,
  • allowed wording and forbidden stronger wording must be preserved when the claim may later enter a report, manuscript, or rebuttal.

When synthesis lands in Knowledge/, link the supporting paper notes explicitly. Do not promote literature synthesis that cannot point back to source notes.

Source and attribution

Source:Galaxy-Dawn/claude-scholarinskills/zotero-obsidian-bridgeat commit9037873

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal