BC vault-sync-engine
Obsidian 多端同步引擎，解决 iCloud/Dropbox 同步冲突、插件配置漂移、`.obsidian/` 目录混乱、 移动端笔记丢失四大痛点。支持 Git 同步、选择性同步、冲突自愈与配置版本化。 核心能力: - 同步方案选型：Git（推荐）/ iCloud / Dropbox / Syncthing / Obsidian Sync - 选择性同步：笔记同步、`.obsidian/` 不同步或分设备同步 - 冲突检测与自愈：自动识别冲突文件、三路合并、保留冲突副本 - 插件配置治理：按设备类型分配置、敏感配置排除同步 - 同步健康看板：上次同步时间、冲突数、未推送提交数 适用场景: - 桌面+手机+平板多端使用 Obsidian - 团队/家庭共享部分笔记但保留各自配置 - 把 Obsidian 当 Git 仓库做版本化知识管理 - iCloud/Dropbox 同步频繁出问题的用户 差异化: - 同步方案决策表（含免费/付费/自建），原版未提同步 - 选择性同步规则（`.obsidian/` 分设备），原版无此概念 - 冲突自愈流程（三路合并 + 副本保留），原版无冲突处理 - 同步健康看板，原版无监控 触发关键词: obsidian, sync, 同步, 多端, icloud, dropbox, git, 冲突, conflict, 移动端
Obsidian 多端同步引擎，解决 iCloud/Dropbox 同步冲突、插件配置漂移、.obsidian/ 目录混乱、 移动端笔记丢失四大痛点。支持 Git 同步、选择性同步、冲突自愈与配置版本化。 核心能力: - 同步方案选型：Git（推荐）/ iCloud / Dropbox / Syncthing /…
As a process C 51/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - note
frontmatter-keyunknown frontmatter key "slug" - note
frontmatter-keyunknown frontmatter key "displayName" - note
frontmatter-keyunknown frontmatter key "summary" - note
frontmatter-keyunknown frontmatter key "tools"
Process rating: all ten parameters 51/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 7 mutating operations with no state check
- 100Tools and files. Tools declared in frontmatter
- 100Steps. 17 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1434 tokens
- low 10 top-level sections: this looks like several domains in one skill
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +3Description length 591: enough signal without eating the budget
- +4Structure: 27 headings
- +3Step-by-step instructions: 17 items
- +4Has examples (15 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 70.