vault-template/system/skills/note-structuring/SKILL.md
自動從對話建立筆記、填 frontmatter、建立連結。觸發詞:「記一下」「幫我寫筆記」「這讓我想到」
npx skillsauth add azuma520/obsidian-graph-query note-structuringInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
從對話中自動辨識筆記類型、填寫 frontmatter、建立知識連結。
| 規則 | 要求 | |------|------| | 主動但不強迫 | 討論中有明確知識內容才建議建筆記,閒聊不要硬建 | | 類型判斷 | 根據內容辨識筆記類型,不確定就問用戶 | | 連結為先 | 建筆記時主動搜尋可能的連結對象 |
觸發 → 辨識筆記類型 → 搜尋相似筆記 → 建議 tags/領域 → 用戶確認 → 填 frontmatter → 建連結 → 完成
建立筆記時,在填寫 frontmatter 前:
原則:
| 用戶說 | 工作流 | |--------|--------| | 「記一下」「幫我寫筆記」「建立筆記」 | workflows/create-note.md | | 「這讓我想到 XX」「跟 XX 有關」「連結到 XX」 | workflows/link-notes.md |
搜尋筆記:
<CLI> vault="<VAULT>" search "<搜尋詞>"
建立筆記:
<CLI> vault="<VAULT>" create "<路徑>" --content "<內容>"
設定屬性:
<CLI> vault="<VAULT>" property:set "<路徑>" "<key>" "<value>"
data-ai
Generate comprehensive knowledge graph reports for Obsidian vaults. Combines multiple graph queries (vault-stats, hubs, bridges, orphans-rich) to produce a structured 4-module analysis report with data summary tables. Requires obsidian-graph-query skill installed. Use for: vault report, knowledge report, vault analysis, vault health, knowledge graph report, 知識圖譜報告, vault 分析.
testing
Run graph queries on Obsidian vault link structure: neighbors (N hops), shortest path, connected clusters, hub notes, bridge/articulation points, enriched orphans, relationship summaries, vault-wide statistics. Supports configurable frontmatter relationship fields. Use for: knowledge graph, note relationships, graph query, link analysis, note connections, hub notes, cluster analysis, bridge notes, relationship summary, vault stats, find path between notes, analyze connections, show orphans, 筆記關係, 連結分析, 孤立筆記, 知識圖譜, 樞紐筆記, vault 統計.
tools
Use when work should span one or more detached tasks but still behave like one job with a single owner context. TaskFlow is the durable flow substrate under authoring layers like Lobster, ACPX, plugins, or plain code. Keep conditional logic in the caller; use TaskFlow for flow identity, child-task linkage, waiting state, revision-checked mutations, and user-facing emergence.
tools
# Lobster Lobster executes multi-step workflows with approval checkpoints. Use it when: - User wants a repeatable automation (triage, monitor, sync) - Actions need human approval before executing (send, post, delete) - Multiple tool calls should run as one deterministic operation ## When to use Lobster | User intent | Use Lobster? | | ------------------------------------------------------ | --------------------------