BF article-organizer-builder
生成器技能（元技能）——专为 Obsidian 用户设计：当用户想构建/生成一个「文章收藏整理」类 Skill（把公众号/网页文章批量提炼为结构化笔记、按主题分类归档进 vault 收藏夹、三依据去重防重复收藏、清理源文件）时使用； 生成的笔记自动带 frontmatter 标签、相关笔记双链与单一总索引 MOC，直接织入 Obsidian 知识图谱。 也用于把个人化的收藏整理 skill 转换为可复用的通用模板。触发词：构建收藏整理skill、生成文章整理skill、 收藏整理skill怎么做、做一个文章归档skill、obsidian收藏整理、article organizer skill builder。 使用时读取 references/builder-prompt.md 中的通用构建规范，收集用户的路径与分类信息，现场生成一个全新独立的目标 skill 写入 ~/.workbuddy/skills/。
生成器技能（元技能）——专为 Obsidian 用户设计：当用户想构建/生成一个「文章收藏整理」类 Skill（把公众号/网页文章批量提炼为结构化笔记、按主题分类归档进 vault 收藏夹、三依据去重防重复收藏、清理源文件）时使用； 生成的笔记自动带 frontmatter 标签、相关笔记双链与单一总索引…
As a process F 35/100 · Will not run — References files that are not bundled: scripts/scan.py, scripts/cleanup.py, references/classification.md
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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: 3. 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") - warning
missing-refreference to a missing file: scripts/scan.py - warning
missing-refreference to a missing file: scripts/cleanup.py - warning
missing-refreference to a missing file: references/classification.md - note
frontmatter-keyunknown frontmatter key "agent_created"
Process rating: all ten parameters 35/100
- 0Tools and files. 3 referenced file(s) missing: scripts/scan.py, scripts/cleanup.py, references/classification.md
- 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
- 100Steps. 12 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 189 tokens
- 100Running it twice. No mutating operations
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
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 411: enough signal without eating the budget
- +4Structure: 3 headings
- +3Step-by-step instructions: 12 items
- +4Reference files are cited in the instructions (1 of 1)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 59.