BC vault-master-pro
Obsidian 知识库（vault）管理专家，基于 `obsidian-cli` 操作本地 Markdown 笔记。聚焦多库管理、 安全重构（移动/改名不断链）、附件治理、跨库搜索，让笔记系统长期保持井井有条。 核心能力: - 多库发现与切换：自动识别系统中的所有 vault，按需切换默认库 - 安全重构：`move`/`rename` 自动更新所有 `[[wikilinks]]` 与 Markdown 链接 - 附件治理：扫描游离附件、按规则归位、清理孤儿文件 - 跨库搜索：标题搜索 + 全文搜索 + 上下文片段 - 批量操作模板：批量改名、批量打标签、批量归档 适用场景: - 个人知识库长期维护（避免越用越乱） - 工作/个人多库切换管理 - 重构笔记结构而不破坏链接 - 定期清理无主附件与孤儿笔记 差异化: - 多库发现 + 切换流程，原版只给单库操作 - 附件治理（扫描/归位/清理孤儿），原版未涉及 - 批量操作模板，原版只给单条命令 - 重构安全检查清单，原版只提"会更新链接" 触发关键词: obsidian, vault, 知识库, 笔记, wikilink, 移动, 重命名, 附件, 双链, mocs
Obsidian 知识库（vault）管理专家，基于 obsidian-cli 操作本地 Markdown 笔记。聚焦多库管理、 安全重构（移动/改名不断链）、附件治理、跨库搜索，让笔记系统长期保持井井有条。 核心能力: - 多库发现与切换：自动识别系统中的所有 vault，按需切换默认库 -…
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: 2. 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. 3 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 1309 tokens
- low 11 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 520: enough signal without eating the budget
- +4Structure: 25 headings
- +3Step-by-step instructions: 17 items
- +4Has examples (13 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 70.