obsitero-paper-note-writer

name	obsitero-paper-note-writer
description	Use when an Obsitero-synced paper Markdown note with local PDF access should be updated in place with managed AI notes generated by reading the PDF directly

Obsitero Paper Note Writer

When to Use

Use this skill when:

• The target is an Obsitero-synced paper Markdown note.
• The note has local_file frontmatter pointing to the PDF, or the PDF path is otherwise available.
• The user wants Codex to write or refresh the managed # AI Notes section in the same note.

Do not use it when there is no paper Markdown note, no accessible local PDF, or the user only wants to edit personal notes.

Inputs

• target_note: absolute path to the Obsitero-synced Markdown note.
• pdf: resolved from local_file frontmatter first, or from an explicit local PDF path.

Reference template: note-template.md

Workflow

1. Read target_note and resolve the local PDF.
2. Inspect/read the local PDF directly with available PDF and text tools as needed.
3. Identify Teaser and Pipeline figure numbers and explain why they matter. In the watcher workflow, local runtime tooling creates image files after Codex returns.
4. Preserve YAML frontmatter exactly.
5. Preserve # My Notes and its content exactly.
6. Preserve # Zotero Notes and its content exactly.
7. Generate # AI Notes content matching the template structure.
8. Place Teaser and Pipeline entries under # AI Notes / ## 关键图表, never under # My Notes; in watcher-generated output, leave image embeds empty and include explicit Figure/Fig. references in **说明**.
9. Replace only the managed block between <!-- OBSITERO-AI-START --> and <!-- OBSITERO-AI-END -->.

If the markers are missing, replace an existing # AI Notes section with a new marked block. If no # AI Notes section exists, insert the marked block after # My Notes and before # Zotero Notes when that section exists.

Page Contract

The note uses H1 sections as working areas:

• # My Notes: user-owned; never edit.
• # AI Notes: managed by this skill; may be regenerated as one block.
• # Zotero Notes: synced content; never edit.

Keep frontmatter at the top. Keep unknown sections in their existing relative position unless insertion of # AI Notes requires placing the managed block between # My Notes and # Zotero Notes.

AI Notes Structure

Match templates/note-template.md:

• ## 元信息
• ## 一句话总结
• ## 核心贡献
• ## 关键图表
• ## 问题背景
• ## 方法详解
• ## 关键公式
• ## 实验结果
• ## 批判性思考

Writing rules:

• Ground claims in the PDF; do not invent missing metadata or results.
• Prefer the paper's title, authors, year, venue/source, project page, and code link when available.
• Explain the problem, why the method is reasonable, how modules connect, and what the real contribution is.
• Include only key equations, each with LaTeX, meaning, and symbol notes.
• Teaser and Pipeline identification is mandatory to attempt for ## 关键图表; use teaser/overview and pipeline/architecture/method figures when identifiable.
• In watcher runs, Codex must not claim to write image files. The local extractor owns crops and will include the figure body plus caption when successful. If a required figure cannot be identified reliably, keep its embed empty and explain 未提及 or the reason in # AI Notes.
• Keep experiment notes focused on main results, ablations, and numerical evidence for central claims.
• Include strengths, limitations, and possible improvements in ## 批判性思考.

Common Mistakes

• Changing frontmatter.
• Editing or moving # My Notes.
• Editing or moving # Zotero Notes.
• Appending duplicate # AI Notes sections.
• Replacing content outside the OBSITERO-AI markers when a marked block exists.
• Filling the note from stale intermediate text instead of reading the local PDF directly.