BF obsidian-core-notes
Maintain Obsidian vault core-file notes, topic synthesis notes, folder indexes, and graph links. Use when working in an Obsidian vault or document/code workspace and creating, editing, moving, deleting, scanning, summarizing, or organizing files that may need `.core.md`, `专题综合.core.md`, `资料索引.md`, or `核心文件索引.md`.
Maintain Obsidian vault core-file notes, topic synthesis notes, folder indexes, and graph links.
As a process F 38/100 · Will not run — References files that are not bundled: references/core-file-rules.md, references/obsidian-linking.md, references/topic-synthesis-core-notes.md
How to improve
- The text references files that are not there: add them or drop the references.
- 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: 0. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: references/core-file-rules.md - warning
missing-refreference to a missing file: references/obsidian-linking.md - warning
missing-refreference to a missing file: references/topic-synthesis-core-notes.md
Process rating: all ten parameters 38/100
- 0Tools and files. 3 referenced file(s) missing: references/core-file-rules.md, references/obsidian-linking.md, references/topic-synthesis-core-notes.md
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 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
- 55Failures and branches. 1 branches
- 100Steps. 31 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 951 tokens
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
- +1No license
- +2Single-language instructions
- +3Description length 314: enough signal without eating the budget
- +4Structure: 6 headings
- +3Step-by-step instructions: 31 items
- +4Has examples (5 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.