Obsidian vault automation for configured vaults such as `obsidian-2026`: vault status/doctor, host Git sync/status with Obsidian Git plugin fallback only whe...
记忆
Obsidian Vaults Workflow Helper
试用Work with Obsidian-style Markdown vaults and local knowledge bases. Use when the user needs to organize notes, add frontmatter, repair links, design vault wo...
它能做什么
Work with Obsidian-style Markdown vaults and local knowledge bases. Use when the user needs to organize notes, add frontmatter, repair links, design vault wo...
技能文档
Work Productivity Obsidian Vaults Workflow Helper
Use this skill when a user wants their notes to remain plain Markdown while still gaining structure, repeatable workflows, and safe automation.
Read references/requirement-plan.md for the demand evidence and original planning criteria.
Vault Intake
Gather or infer:
- Vault root path and any folders that must not be edited.
- Note naming conventions, frontmatter schema, tags, aliases, and link style.
- Whether attachments, canvases, daily notes, tasks, or dataview queries are in scope.
- Desired output: cleanup plan, template set, migration, index note, or automation script.
Workflow
- Inspect the vault layout before recommending changes.
- Separate read-only analysis from file mutations; propose a dry-run summary for bulk edits.
- Normalize metadata carefully: preserve existing YAML keys, note aliases, timestamps, and user formatting unless the user asks otherwise.
- Repair links and backlinks using vault-relative paths; avoid breaking embeds and attachments.
- Produce templates or scripts only when the repeated workflow justifies them.
- Verify by sampling changed notes and checking for unresolved wiki links, duplicate tags, or malformed frontmatter.
Guardrails
- Never rewrite a whole vault blindly.
- Avoid cloud-only sync assumptions; keep procedures local-file friendly.
- Prefer reversible changes, backups, or generated patch plans for large migrations.
- Treat personal notes as sensitive content; summarize structure without exposing private text unnecessarily.
Outputs
- Vault audit with risks and recommended structure.
- Markdown templates for notes, projects, meetings, or daily logs.
- Frontmatter migration plan or script.
- Link repair and index-building checklist.
Validation Checklist
- Paths and excluded folders are explicit.
- Bulk edits have a dry-run or rollback path.
- Markdown, YAML frontmatter, links, and attachments remain valid.
- The workflow fits Obsidian without requiring proprietary storage.
Triggers
Keywords: Obsidian, vault, Markdown notes, frontmatter, backlinks, wiki links, dataview, daily notes, knowledge base.
Example requests:
Clean up my Obsidian vault without breaking links.Use $work-productivity-obsidian-vaults-workflow-helper to add frontmatter templates to these notes.Plan a migration from loose Markdown files into an Obsidian vault.
相关技能
Help users with Validated demand: Agent users show strong demand for Obsidian-style workflows on Clawhub. They need practical help fixing bugs, hardening set...
Maintain Obsidian vault core-file notes, topic synthesis notes, folder indexes, and graph links. Use when working in an Obsidian vault or document/code works...
Obsidian 知识库(vault)管理专家,基于 `obsidian-cli` 操作本地 Markdown 笔记。聚焦多库管理、 安全重构(移动/改名不断链)、附件治理、跨库搜索,让笔记系统长期保持井井有条。 核心能力: - 多库发现与切换:自动识别系统中的所有 vault,按需切换默认库 - 安全重构:`m...
Operate an Obsidian knowledge base as a persistent LLM wiki using a raw-to-source-to-wiki pattern. Use when Codex or another agent needs to ingest raw notes,...
Build a searchable local knowledge base from an Obsidian vault's "笔记同步助手" inbox, then answer with citations, topic cards, update logs, and daily digests for...