Use this skill when papers are collected in Zotero but the user wants detailed reading notes, project-linked literature synthesis, collection-wide paper-note coverage checks, and a connected knowledge map inside the bound Obsidian project knowledge base.
SkillScore86Maintained
Automatic
◆Knowledge Management pack
Last verified 8/8/2026
What it changes
Passed 16 of 19 test cases with the skill, and 11 of 19 without it.
Without skill59%
With skill86%
Checks it passed that the model alone missed
Verification is executed using scripts/verify_paper_notes.py.
The lightweight presentation canvas is saved to Maps/literature-main.canvas.
Ingested literature notes are targeted primary to Papers/ and Knowledge/ folders.
and 3 more in the full report
6 fixed13 passed either way3 still failing0 broke
Pass-rate lift
+27 pp
Tokens
+48%
Agent turns
0%
Response time
-36%
Model gemini-3.6-flashMeasured 8/8/2026v119 of 22 cases passed with skill · 19 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 6
Prompt
After generating the primary argument map canvas at Maps/literature.canvas, I want a lightweight presentation visual diagram with semantic edge filtering. What path should be used for this optional presentation canvas?
What was checked, without and with the skill
Checked
Without skill
With skill
The lightweight presentation canvas is saved to Maps/literature-main.canvas.
Missed
Passed
case-10 · gemini-3.6-flash · 8/8/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md106 lines6 filesincludes scripts
Zotero Obsidian Bridge
Bridge Zotero as the literature source of truth with Obsidian as the durable project knowledge base.
Use this skill when the user wants to:
collect and organize papers in Zotero,
read papers from Zotero MCP,
create or update one detailed paper note per paper under Obsidian Papers/,
synthesize those notes into Knowledge/ notes,
verify that a whole Zotero collection has complete canonical note coverage,
visualize the literature structure as a default Obsidian canvas.
Core stance
Zotero owns collection, metadata, attachments, PDF full text, annotations.
Prefer filesystem-first Obsidian notes; do not require Obsidian MCP.
Use this as an explicit, agent-first skill for Zotero ingestion.
Prefer Papers/ + Knowledge/ as the default bridge targets.
Prefer Maps/literature.canvas as the default graph artifact.
Prefer a strong review schema inside each canonical paper note:
Claim
Method
Evidence
Limitation
Direct relevance to repo
Relation to other papers
Treat some Zotero webpage items as valid literature sources when they still expose useful metadata, attachment text, or fulltext.
Default workflow
Resolve the current project via $obsidian-project-memory.
If the repo is already bound, use the existing vault.
If it looks like a research repo but is not bound, bootstrap it first.
Read Zotero items from the target collection/query.
If the user asked for a full collection pass, prefer full coverage over a small representative subset.
If the transport path through MCP is failing but a local zotero-mcp source checkout or Python environment is available, use that local fallback to read metadata/fulltext instead of stopping the workflow.