本文へ移動
cccskills
無料GitHub で公開

obsidian-literature-workflow

Use 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.

インストール方法を見る

含まれるファイル(6)

  • SKILL.md3.8 KB
  • references/CANVAS-WORKFLOW.md1.7 KB
  • references/GRAPH-WORKFLOW.md768 B
  • references/PAPER-NOTE-SCHEMA.md1.3 KB
  • scripts/build_literature_canvas.py22.6 KB
  • scripts/build_literature_graph.py9.4 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Obsidian Literature Workflow

Handle the literature sub-workflow inside the filesystem-first Obsidian project knowledge base.

Role in the workflow

This is a supporting skill under obsidian-project-memory.

Use it when the user says things like:

  • “My papers are in Obsidian”
  • “Read papers from Zotero and create notes in the vault”
  • “Review the notes under Papers/”
  • “Generate literature knowledge notes from this project vault”
  • “Connect paper notes to project knowledge”
  • “Show me the literature structure as a map/graph”
  • “Check whether all papers already have detailed notes”

Assumptions

  • The project is already bound through .claude/project-memory/registry.yaml, or can be imported with obsidian-project-bootstrap
  • Durable paper notes live under Papers/ inside Research/{project-slug}/
  • Obsidian note writing is done through the filesystem; no Obsidian MCP is required
  • Zotero may still be used as the source of metadata/full text; use $zotero-obsidian-bridge when the source corpus is in Zotero

Default workflow

  1. Read bound project memory and locate the vault root.
  2. If the source papers are in Zotero, explicitly use $zotero-obsidian-bridge to pull them into canonical Papers/*.md notes.
  3. Scan Papers/ and adjacent synthesis notes using filesystem tools.
  4. Normalize note metadata and structure using $obsidian-markdown.
    • Prefer the standardized review schema:
      • Claim
      • Method
      • Evidence
      • Limitation
      • Direct relevance to repo
      • Relation to other papers
  5. Query narrowly first:
    • read the relevant paper notes,
    • then the linked Knowledge/ notes,
    • and only then open Writing/ if the user asked for a review or comparison deliverable.
  6. Prefer updating existing paper notes and literature synthesis notes over creating sibling notes.
  7. Default literature synthesis should land in Knowledge/, not Experiments/ or Results/:
    • update Knowledge/Literature-Overview.md
    • update Knowledge/Method-Families.md
    • update Knowledge/Research-Gaps.md when the synthesis is stable enough to deserve canonical notes.
  8. If the source is a named collection and the user cares about completeness, maintain a collection inventory note with explicit coverage mapping.
  9. Refresh Maps/literature.canvas after major paper-note changes or batch note creation.
    • Prefer argument-map structure over dense all-to-all links.
    • Prefer semantic filtering and edge thinning.
    • Create Maps/literature-main.canvas only when a lightweight presentation graph is needed.
  10. Update the daily note and project memory with what changed.

Default outputs

  • Papers/ remains first-class: one durable paper note per paper whenever possible
  • Knowledge/ holds durable literature synthesis notes
  • Maps/literature.canvas is the default visual graph surface
  • literature work should usually produce at least one of:
    • new or updated paper notes,
    • new or updated knowledge notes,
    • literature-canvas refresh,
    • optional writing synthesis when requested

Default stance

Do not assume by default:

  • Concepts/
  • Datasets/
  • .base views

The literature workflow may create Maps/literature.canvas by default. Other artifacts still require explicit justification.

References

Load only what is needed:

  • references/PAPER-NOTE-SCHEMA.md - detailed paper-note frontmatter and sections
  • references/CANVAS-WORKFLOW.md - how and when to refresh Maps/literature.canvas

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

a1

無料

VS-Enhanced Research Question Refiner - Prevents Mode Collapse and derives differentiated research questions Enhanced VS 3-Phase process: Modal question avoidance, alternatives presentation, differentiated RQ recommendation Use when: refining research ideas, formulating research questions, clarifying scope Triggers: research question, 연구 질문, PICO, SPIDER, research idea

日本語の概要は準備中です。原文の説明を表示しています。

brycewang-stanford/Auto-Empirical-Research-Skills4,6032026年10月12日 更新

a2

無料

VS-Enhanced Theoretical Framework Architect with Critique & Visualization Full VS 5-Phase process: Modal theory avoidance, Long-tail exploration, differentiated framework presentation Absorbed A3 (Devil's Advocate) critique and A6 (Conceptual Framework Visualizer) capabilities Use when: building theoretical foundations, designing conceptual models, deriving hypotheses, critiquing frameworks, visualizing models Triggers: theoretical framework, 이론적 프레임워크, conceptual model, 개념적 모형, hypothesis derivation, critique, devil's advocate, 반론, visualization, diagram

日本語の概要は準備中です。原文の説明を表示しています。

brycewang-stanford/Auto-Empirical-Research-Skills4,6032026年10月12日 更新

a5

無料

Agent A5 - Paradigm & Worldview Advisor - Philosophical foundations for research design. Covers ontology, epistemology, axiology, and methodology alignment. Use when: establishing philosophical foundations, justifying methodological choices, writing positionality statements Triggers: paradigm, 패러다임, ontology, epistemology, worldview, 세계관, philosophical foundations, 철학적 기초

日本語の概要は準備中です。原文の説明を表示しています。

brycewang-stanford/Auto-Empirical-Research-Skills4,6032026年10月12日 更新

Academic paper writing skill with 12-agent pipeline. v2.5: Style Calibration (learn author's writing voice from past papers) + Writing Quality Check (writing quality checklist for natural prose). Supports IMRaD, literature review, theoretical, case study, policy brief, and conference paper structures. APA 7.0 (default), Chicago, MLA, IEEE, Vancouver citation formats. Bilingual abstracts (zh-TW + EN). Multi-format output (LaTeX, DOCX, PDF, Markdown). Triggers on: write paper, academic paper, paper outline, write abstract, revise paper, check citations, convert to LaTeX, guide my paper, parse reviews, revision roadmap, 寫論文, 學術論文, 論文大綱, 寫摘要, 修改論文, 檢查引用, 引導我寫論文, 帶我規劃論文, 逐章規劃, 論文架構, 審查意見, 修訂路線圖.

日本語の概要は準備中です。原文の説明を表示しています。

brycewang-stanford/Auto-Empirical-Research-Skills4,6032026年10月12日 更新

Systematic writing framework for philosophy and interdisciplinary academic papers from optimized outline to submission-ready manuscript. Use when users want to: (1) write a paper from a detailed outline, (2) ensure quality control during writing, (3) maintain consistency across chapters, (4) prepare a submission-ready manuscript, or (5) systematically execute a planned paper. Triggered by phrases like 'write the paper from this outline,' 'compose the full manuscript,' 'execute the outline,' or when users have completed strategic planning (academic-paper-strategist skill) and are ready to write. Takes optimized outline as input; outputs complete manuscript with iterative quality checks.

日本語の概要は準備中です。原文の説明を表示しています。

brycewang-stanford/Auto-Empirical-Research-Skills4,6032026年10月12日 更新

Multi-perspective academic paper review with dynamic reviewer personas. Simulates 5 independent reviewers (EIC + 3 peer reviewers + Devil's Advocate) with field-specific expertise. Supports full review, re-review (verification), quick assessment, methodology focus, and Socratic guided modes. Triggers on: review paper, peer review, manuscript review, referee report, review my paper, critique paper, simulate review, editorial review.

日本語の概要は準備中です。原文の説明を表示しています。

brycewang-stanford/Auto-Empirical-Research-Skills4,6032026年10月12日 更新

brycewang-stanford のスキルをすべて見る

このスキルの問題を報告する