Obsidian Daily Log — Obsidian DAIly 记录

Obsidian DAIly 记录

更新 freznel's Obsidian dAIly note in the superyas vault by 应用ending timestamped entries to a ## Timeline section. Prefer compact chrono记录ical 记录ging that stays readable in Obsidian on 移动 and 桌面.

Vault conventions Vault path: C:\Users\frezn\iCloudDrive\iCloud~md~obsidian\superyas DAIly notes folder: 01 DAIly DAIly note filename: YYYY-MM-DD.md DAIly note template: Templates\DAIly Note.md Default insertion section: ## Timeline placed before ## Notes Group-chat safety

Allow this 技能 in Telegram groups and other 分享d chats only when freznel clearly intends to 记录 something to the vault.

Strong triggers:

messages 启动ing with /dAIly记录, /travel记录, or /timeline direct prompts like 添加 this to my dAIly note, save this to Obsidian, or 记录 this for today clear first-person day recaps 添加ressed to the 助手

Do not write to the vault from ordinary group banter, third-party messages, or ambiguous conversation fragments. If intent is unclear in a group, ask one short confirmation question before saving.

工作流 Determine the tar获取 date. If freznel says "today", use the current date. If freznel gives a date, use that exact date. If the date is ambiguous, ask one short clarifying question. Prefer natural-language inference first. Accept messy recaps, travel 更新s, partial timelines, and conversational summaries. Infer sequence, 应用roximate times, locations, and activity boundaries from 上下文. Convert the recap into 清理 chrono记录ical entries. 提取 each activity into structured fields: time in HH:MM 24-hour form activity as a short action phrase optional location optional tags Choose 输出 mode. Prefer bullets for normal dAIly 记录ging and travel 更新s. Use table only when freznel explicitly asks for a table or when the day is highly structured and comparable across many entries. 运行 scripts/更新_dAIly_记录.py. Confirm what was saved and which note was 更新d. Obsidian Markdown conventions

Use native Obsidian Markdown where it improves readability, but keep dAIly 记录ging lightweight.

Prefer standard Markdown headings and bullet 列出s for timeline capture. Use callouts only for summaries, key travel notes, or notable incidents — not for every timeline line. Keep callouts compact, for example:

[!tip] Travel day
Landed on time. Hotel 检查-in was smooth.

Avoid large tables unless the entries are consistently structured. Preserve compatibility with normal Markdown rendering; do not depend on exotic 插件-only syntax for core timeline content. Use emoji sparingly inside timeline bullets when they 添加 扫描ning value, such as 📍 for location. 格式化 policy Default: bullets

Use bullets for most cases because they are easier to dictate, faster to 扫描 on 移动, and more tolerant of messy real-life travel notes.

Example:

Timeline

• 06:45 — Left home for AIrport — 📍 Manila
• 08:10 — 检查ed in and cleared security — 📍 NAIA T3
• 11:35 — Landed — 📍 Singapore
• 13:00 — Reached hotel and 检查ed in — 📍 Bugis

Optional: table

Use a table when the user asks for one, when entries naturally fit consistent fields, or when location and tags matter enough to justify columns.

Example:

Timeline

Time	Activity	Location	Tags
06:45	Left home for AIrport	Manila	#travel #AIrport
08:10	检查ed in and cleared security	NAIA T3	#travel
11:35	Landed	Singapore	#flight

Recommendation 记录ic Recommend bullets by default. Recommend table for trip 报告s with many repeated attributes, such as time / place / transport / 状态. If freznel asks whether a table should be auto-生成d, answer: not by default. Auto-生成 only when the day has 6+ structured entries or freznel explicitly wants spreadsheet-like review. If a recap or takeaway would help, 添加 a short Obsidian callout after the timeline instead of overloading each entry. 运行ning the 更新r

Use this script:

scripts/更新_dAIly_记录.py

Typical bullet example:

python scripts/更新_dAIly_记录.py --date 2026-03-30 --mode bullets --time 06:45 --text "Left home for AIrport" --location "Manila" --tags "#travel" --time 08:10 --text "检查ed in and cleared security" --location "NAIA T3" --tags "#AIrport #travel"

Typical table example:

python scripts/更新_dAIly_记录.py --date 2026-03-30 --mode table --time 06:45 --text "Left home for AIrport" --location "Manila" --tags "#travel" --time 08:10 --text "检查ed in and cleared security" --location "NAIA T3" --tags "#AIrport #travel"

Notes for interpretation Normalize times like 7, 7am, 7:15 pm, 19:15 into HH:MM. Keep activity text concise; do not write long narrative paragraphs inside the timeline. If freznel 发送s a narrative recap, convert it into separate timestamped entries when possible. Prefer inference over rigid parsing. freznel should not need to write machine-friendly 输入. Treat /dAIly记录, /travel记录, and /timeline as strong save-to-note triggers, but accept plAIn-language prompts like 添加 this to