frontier-sync

name

frontier-sync

description

Append-only frontier research synchronization for Obsidian technical documents, with interactive, scheduled, and review modes. Use when the user asks to update, create, maintain, refresh, schedule, automate, or periodically run a "前沿信息同步"/frontier update section in one or more Markdown technical notes. In interactive mode, propose 3-10 priority information sources and ask the user which to keep/add/remove before writing. In scheduled mode, use existing confirmed sources and append dated updates without deleting history. In review mode, collect and report candidate updates without editing files.

Frontier Sync

Overview

Synchronize frontier technical developments into Obsidian Markdown notes using an append-only workflow. The skill creates or maintains two sections near the end of each target document:

1. 前沿同步优先信息源
2. 前沿信息同步

Never delete or overwrite previous dated frontier updates.

Modes

Use one of three modes based on the user request:

1. Interactive mode: Use for first-time setup or manual refresh. Propose sources, ask for confirmation, then write sources and append the update.
2. Scheduled mode: Use for Codex scheduled automations or recurring runs. If the document already has 前沿同步优先信息源, use those existing confirmed sources and do not ask for source confirmation. If the source section is missing, do not invent and write sources unattended; append no frontier update and report that the document needs interactive setup first.
3. Review mode: Use when the user asks to preview, audit, or review possible frontier updates. Collect and summarize candidate updates, but do not edit files unless the user later approves.

For recurring jobs, prefer scheduled mode. The human chooses trusted sources once; the automation periodically checks those sources and appends concise updates only when useful.

Required Workflow

1. Identify Target Documents

Confirm the user-specified Markdown document(s). If the target is ambiguous, ask for the file path or note name.

Read each target document before proposing sources. Infer:

• Main technology or concept
• Adjacent concepts
• Existing source lists and references
• Existing 前沿同步优先信息源 / 前沿信息同步 sections
• Existing terminology style and language

For Obsidian notes, preserve frontmatter, wikilinks, headings, callouts, and existing section order.

2. Propose Priority Information Sources

Skip this step in scheduled mode when 前沿同步优先信息源 already exists.

For each document, propose 3-10 priority information sources. Prefer sources in this order:

1. Official specifications and standards
2. Official vendor documentation
3. Official SDK repositories and changelogs
4. High-quality engineering blogs from primary organizations
5. Peer-reviewed papers, arXiv surveys, or benchmark papers
6. Widely used framework documentation

Avoid low-signal sources unless the user explicitly asks for broad community sentiment:

• SEO blogs
• Content farms
• Unsourced social media posts
• Outdated tutorials
• Vendor marketing pages with no technical detail

Present sources as a table:

| 保留? | 信息源 | 类型 | 为什么优先参考 |
|------|--------|------|----------------|
| 建议保留 | ... | 官方文档/论文/SDK | ... |

3. Ask the Required User Question

Skip this step in scheduled mode when using an existing confirmed source list.

Stop and ask the user which sources to keep, remove, or add before writing the source list or frontier update.

Ask in plain language, for example:

这些是我建议作为该文档“前沿同步优先信息源”的来源。你希望保留哪些、删除哪些、或者补充哪些？你回复“都保留”也可以。

Do not proceed with web synthesis until the user answers. If the user explicitly says to decide yourself, proceed with the proposed set.

4. Write or Update the Priority Source Section

In scheduled mode, do not rewrite the priority source section unless the user explicitly asked the automation to maintain sources.

After the user confirms sources, update the target note.

If 前沿同步优先信息源 exists:

• Preserve user-approved existing sources unless the user removed them.
• Update the table with the confirmed source set.

If it does not exist:

• Insert the section near the end of the content, before 前沿信息同步 or before 参考资料.

Use this structure:

## 前沿同步优先信息源

以后更新本文的“前沿信息同步”时，优先参考以下信息源中最近发布或更新的相关内容：

| 优先级 | 信息源 | 类型 | 关注重点 |
|--------|--------|------|----------|
| 1 | [Source Name](https://example.com) | 官方规范 | ... |

5. Collect Recent Frontier Information

Use web browsing because frontier information is time-sensitive.

Query the confirmed priority sources first. Then optionally add recent papers, release notes, or official announcements when relevant.

Filter collected information:

• Prefer recent updates.
• Prefer sources with direct technical substance.
• Distinguish stable facts from inference.
• Ignore unrelated product marketing.
• Do not include rumors.

Scheduled mode filtering:

• Prefer no change over low-signal filler.
• If no meaningful update is found, either leave the document unchanged or append a short "no significant update" note only when the automation prompt requests it.
• Do not create long repetitive updates merely because the schedule fired.
• If several target documents are processed, report per-document status.

6. Append the Dated Frontier Update

If 前沿信息同步 does not exist, create it after 前沿同步优先信息源 and before 参考资料.

Append a new dated subsection under it. Do not edit, summarize away, or delete prior dated subsections.

Use the current local date in YYYY-MM-DD format:

## 前沿信息同步

### 2026-07-06

本次同步时，...

几个值得关注的方向：

1. **方向名**：说明。
2. **方向名**：说明。

可继续跟踪：

- [Source](https://example.com)

If a document already uses 前沿同步 instead of 前沿信息同步, keep the existing heading unless the user asks to rename it. For new documents, prefer 前沿信息同步.

In review mode, output the proposed dated update in the chat instead of editing the document.

7. Preserve Append-Only History

Never remove previous dated entries such as:

### 2026-07-06

If today's date already exists, append a new paragraph under the same date only when the user asks to expand today's update. Otherwise create a date with a suffix:

### 2026-07-06 补充

Writing Guidelines

• Match the document's language. For Chinese technical notes, write in Chinese.
• Keep the frontier update concise but source-backed.
• Use links for cited sources.
• Clearly mark uncertainty: "从资料可以推断..." when inferring.
• Do not over-quote sources.
• Preserve existing terminology rules in the document.
• For Obsidian notes, use wikilinks for local notes and Markdown links for web URLs.

Safety and Quality Checks

Before final response:

1. Verify the priority source section exists.
2. Verify the frontier update section exists.
3. Verify previous dated updates were not deleted.
4. Verify new links are valid Markdown links.
5. Report which files were updated.

For scheduled mode, also verify:

1. Every edited document already had confirmed priority sources.
2. Documents missing priority sources were skipped and reported.
3. No existing dated update was removed or rewritten.
4. No empty or low-signal scheduled update was appended.

Optional Reference

For detailed section templates and source selection examples, read references/section-templates.md.