‹ 首页

wiki-maintainer

@zavianx · 收录于 5 天前 · 上游提交 2 个月前

Maintain the Velaclaw memory wiki vault with deterministic pages, managed blocks, and source-backed updates.

适合你,如果维护着需要与代码或数据源保持一致的维基知识库

/ 通过 npx 安装 校验哈希
npx oh-my-skill add zavianx/vela/wiki-maintainer
/ 通过 bash 安装
curl -fsSL https://oh-my-skill.com/install.sh | bash -s -- zavianx/vela/wiki-maintainer
/ 已经装过?验证本机副本,不用重装
npx oh-my-skill verify zavianx/vela/wiki-maintainer
安装目标可用 --agent / --scope 或 --to 明确指定;省略时只会在唯一已存在的 agent 目录上自动选择,零命中或多命中会停止并提示。content_hash 缺失或不一致均拒装。
122GitHub stars
~366上下文体积 · 单文件
索引托管

怎么用

商店整理自技能原文 · 版本 bd323cc · 表述以原文为准
它做什么

装上后,Claude 会先检查 vault 状态,用 wiki 搜索和获取页面,进行窄范围编辑,运行 lint 检查,并使用 velaclaw wiki 命令维护。它导入外部记忆(bridge 模式)或本地路径(unsafe-local 模式,需同意),不覆盖人类笔记,优先更新已有实体。

什么时候触发

在记忆 wiki vault 内工作时触发,例如需要理解 vault 模式、搜索或编辑页面、运行 lint 检查,或在 bridge/unsafe-local 模式下导入内容时。

装好后可以这样说
触发 wiki_lint 发现矛盾、来源缺口和未解决问题。
技能原文 SKILL.md作者撰写 · MIT · bd323cc

Use this skill when working inside a memory-wiki vault.

  • Prefer wiki_status first when you need to understand the vault mode, path, or Obsidian CLI availability.
  • Prefer memory_search with corpus=all when the shared memory tools are available and you want one recall pass across durable memory plus the compiled wiki.
  • Use wiki_search to discover candidate pages when you want wiki-specific ranking/provenance, then wiki_get to inspect the exact page before editing or citing it.
  • Use wiki_apply for narrow synthesis filing and metadata updates when a tool-level mutation is enough.
  • Run wiki_lint after meaningful wiki updates so contradictions, provenance gaps, and open questions get surfaced before you trust the vault.
  • Use velaclaw wiki ingest, velaclaw wiki compile, and velaclaw wiki lint as the default maintenance loop.
  • In bridge mode, run velaclaw wiki bridge import before relying on search results if you need the latest public memory artifacts pulled in.
  • In unsafe-local mode, use velaclaw wiki unsafe-local import only when the user explicitly opted into private local path access.
  • Keep generated sections inside managed markers. Do not overwrite human note blocks.
  • Treat raw sources, memory artifacts, and daily notes as evidence. Do not let wiki pages become the only source of truth for new claims.
  • Keep page identity stable. Favor updating existing entities and concepts over spawning duplicates with slightly different names.
  • When creating or refreshing indexes, preserve Obsidian-friendly wikilinks if the vault render mode is obsidian.
按 MIT 许可原样转载,未经改动 · 在 GitHub 查看 →

评论

登录即可评论;带「已验证安装」的,是发布者名下有本店的安装或持有记录。