Organize papers from Zotero into an Obsidian project knowledge base. The skill separates source notes, research synthesis, and writing outputs, requiring evidence records and source links before findings become claims used in later work.
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.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
Use this skill when papers live in Zotero and the project KB should receive project-local notes.
Default flow:
Zotero -> Sources/Papers -> Knowledge -> Writing -> Maps/literature.canvas
Rules:
Sources/Papers/Knowledge/Writing/Maps/literature.canvas is the default derived graph artifact_system/registry.md, 02-Index.md, and today's Daily/ after substantial ingestionCore 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.
## Evidence Record
Evidence ID:
Source:
Source type: full paper | preprint | dataset | experiment artifact | project note | abstract-only | webpage placeholder
Supports:
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:
When synthesis lands in Knowledge/, link the supporting paper notes explicitly. Do not promote literature synthesis that cannot point back to source notes.
No reviews yet. Tell others what you thought.
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.
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.
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.
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.
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.
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.
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.