brycewang-stanford/Auto-Empirical-Research-Skills / skills/33-Galaxy-Dawn-claude-scholar/skills/obsidian-literature-workflow
obsidian-literature-workflow
VerifiedUse this skill when the user keeps paper notes inside an Obsidian project knowledge base and wants filesystem-first literature review, explicit agent-first Zotero ingestion, `Papers/` plus `Knowledge/` synthesis, collection-wide normalization, and a default literature canvas without Obsidian MCP.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 3.8 KB |
| references/CANVAS-WORKFLOW.md | markdown | 1.7 KB |
| references/GRAPH-WORKFLOW.md | markdown | 768 B |
| references/PAPER-NOTE-SCHEMA.md | markdown | 1.3 KB |
| scripts/build_literature_canvas.py | script | 22.6 KB |
| scripts/build_literature_graph.pyexecutable | script | 9.4 KB |
references/PAPER-NOTE-SCHEMA.md
View on GitHub# Paper Note Schema
Use this schema when normalizing or creating durable paper notes in `Papers/`.
## Required frontmatter
```yaml
---
type: paper
title: "Paper Title"
project: project-slug
authors:
- Author A
year: 2026
venue: "Venue"
doi: "10.xxxx/xxxxx"
url: "https://..."
citekey: "author2026paper"
status: read
updated: 2026-03-16T00:00:00Z
---
```
## Recommended frontmatter for knowledge mapping
```yaml
keywords:
- decoding
concepts:
- shared geometry
methods:
- contrastive learning
related_papers:
- "Papers/Neighbor-Paper"
linked_knowledge:
- "Knowledge/Literature-Overview"
- "Knowledge/Method-Families"
```
## Recommended sections
- `## Claim`
- `## Research question`
- `## Method`
- `## Evidence`
- `## Strengths`
- `## Limitation`
- `## Direct relevance to repo`
- `## Relation to other papers`
- `## Knowledge links`
- `## Optional downstream hooks`
## Working rules from real collection passes
- Prefer one canonical note per paper and keep the schema aligned across the whole covered set.
- When the user asks to check **all** papers, perform a coverage pass rather than stopping at a representative subset.
- Use `zotero_key` as the durable join key between Zotero items and Obsidian notes.
- Keep `Direct relevance to repo` concrete enough to drive experiments, writing, or review prioritization.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |