Paper Note Ingest

3. Generate the reading note.

• Follow the user's paper-summary prompt exactly when one is supplied.
• Write in Chinese unless the user asks otherwise.
• Do not copy long spans from the abstract or introduction. Compress and reinterpret.
• Prefer reviewer-style synthesis over section-by-section paraphrase.

4. Repair repository structure.

• Ensure the paper note ends with Obsidian wiki links to the venue note and author notes.
• Create missing author notes under the repository's author hierarchy if the vault already organizes authors by institution or organization.
• Create or update venue notes under 文献/会议 or 文献/期刊, matching the vault's convention.
• Keep author and venue notes lightweight unless the user explicitly asks for richer content.

5. Preserve local conventions.

• Do not rename existing notes unless the user asks.
• Reuse folder names and wiki-link styles already present in the repository.
• If the vault already has a template for nearby paper notes, mirror it instead of forcing a new schema.

Metadata Rules

• source: venue or journal short name already used in the vault, such as VLDB, SIGMOD, ICDE, or PVLDB.
• authors: prefer a YAML list of plain names in frontmatter; put wiki links in the body footer.
• tags: include topic tags only when they are specific enough to help retrieval. Never use spaces inside a single Obsidian tag; prefer DataWarehouse, QueryProcessing, Lakehouse/Metadata, or hyphenated forms.
• category: use 论文阅读 unless the user specifies a different category.
• date: use the note creation or reading date in YYYY-MM-DD.
• title: use the paper title exactly, with standard capitalization.
• link: prefer DOI, official venue PDF, official journal page, or an official landing page.

Footer Rules

Append a compact footer section after the main content when the note is intended for Obsidian storage. Include:

• The venue wiki link.
• One wiki link per author.
• No unrelated boilerplate.

Companion Note Patterns

For author notes, prefer a dataview index:

list

from ""
where contains(authors, this.file.name)
sort file.name asc

For venue notes, prefer a dataview index keyed by source:

list

where contains(source, this.file.name)
sort file.name asc

References

• Use references/obsidian-paper-template.md when generating or rewriting a paper note from scratch.
• If the user supplies a custom prompt template, follow that template while still applying the metadata and footer rules above.
• If the vault has multiple literature-note variants later, add more reference files instead of overloading this skill file.

Default Behavior

• When the user asks for a paper summary plus note generation, do both in one pass.
• When the user asks only for a summary, still collect enough metadata that the note can be materialized later.
• When metadata is ambiguous, state the uncertainty briefly and leave the field blank instead of inventing values.