CF obsidian-markdown
技术写作员与内容创作者在构建Obsidian知识库时,当需要编写带双向链接、Callout或Frontmatter的复杂笔记,使用此技能可精准生成标准Markdown文档,完美支持wikilinks与嵌入,大幅提升知识管理与排版效率!
技术写作员与内容创作者在构建Obsidian知识库时,当需要编写带双向链接、Callout或Frontmatter的复杂笔记,使用此技能可精准生成标准Markdown文档,完美支持wikilinks与嵌入,大幅提升知识管理与排版效率!
As a process F 32/100 · Will not run — References files that are not bundled: Note%20Name.md, Note%20Name.md
ProcedureObsidianLaTeXGitHubSoftware developmenttype and topics are labelled automatically from the skill text
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.
For the model run — optional
- 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") - warning
missing-refreference to a missing file: Note%20Name.md - warning
missing-refreference to a missing file: Note%20Name.md
Process rating: all ten parameters 32/100
Will not run. References files that are not bundled: Note%20Name.md, Note%20Name.md
- 0Tools and files. 2 referenced file(s) missing: Note%20Name.md, Note%20Name.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
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 2 mutating operations with no state check
- 85Steps. 19 steps, 1 vague phrases
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2627 tokens
- 100Progress reporting. Reports progress
- low 20 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)
- +3Description length 117: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- -5TODO / placeholder text left in the skill
- +1No license
- +2Single-language instructions
- +4Structure: 57 headings
- +3Step-by-step instructions: 19 items
- +4Has examples (56 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 55.