AB weasleys-wizard-wheezes-obsidian-kanban
Create, normalize, and reorganize Obsidian Kanban plugin markdown boards. Display name: Weasleys Wizard Wheezes - Obsidian Kanban. Use when working with Obsidian Kanban `.md` files, turning ledgers, review ledgers, tables, checklists, audit notes, or issue lists into board columns and cards, reformatting existing Kanban boards for readability, or preserving full content while making cards easier to scan. Trigger on requests like “把台账转成 Obsidian 看板”, “整理这个 Kanban 文件”, “优化看板格式但不要删内容”, or “把 Markdown 清单改成 Kanban”.
As a process B 70/100 · Nearly there — weak spots: result and completion, inputs and preconditions, progress reporting
How to improve
- 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
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 2, column 14: description: Create, normalize, and reorganize Obsidian Kanban plugin markdown … ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value
Process rating: all ten parameters 70/100
- 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
- 70Failures and branches. 4 branches
- 100Tools and files. No external tools needed
- 100Steps. 77 steps
- 100When it triggers. States when to use and when not to
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1249 tokens
- 100Running it twice. Mutating operations check current state
- 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
- +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
- +5Description quotes 4 example trigger phrases
- +3Description length 516: enough signal without eating the budget
- +4Structure: 16 headings
- +3Step-by-step instructions: 77 items
- +4Has examples (3 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 79.