CF url-to-obsidian
通过网址获取网页内容并创建为 Obsidian 笔记。支持技术文档、博客文章、GitHub README 等类型网页。 支持可选的中文翻译（代码块、命令、包名、URL 保持不变），排版结构清晰简洁。 优先使用 opencli web read 抓取，不可用时自动降级到 Firecrawl、fetchWebContent、fetch。 使用前会主动收集信息：链接地址、笔记名称、存储位置、是否翻译 —— 信息不明确时提供选项让用户选择， 用户也可一键确认默认建议。自动生成 frontmatter、标签和来源信息。 Triggers on: 保存网址到obsidian、网页转obsidian笔记、url to obsidian、抓取网页到 obsidian、 save url to obsidian、fetch and save to obsidian、把这个网页保存到 obsidian、 收藏到 obsidian、保存到 obsidian 知识库、存档页面到 obsidian
通过网址获取网页内容并创建为 Obsidian 笔记。支持技术文档、博客文章、GitHub README 等类型网页。 支持可选的中文翻译（代码块、命令、包名、URL 保持不变），排版结构清晰简洁。 优先使用 opencli web read 抓取，不可用时自动降级到…
As a process F 39/100 · Will not run — References files that are not bundled: 子页面URL, URL
What is at stake
The skill contains fragments that, in the wrong hands, cost money or data. Below: what the installer risks and what the author should do.
The skill contains commands that delete files, rewrite disks or execute code fetched from the network. The agent may run them without asking if it believes the instructions require it.
Replace destructive commands with safe equivalents that ask for confirmation, scope them to one folder, and stop piping curl into a shell: pin a version and a checksum.
How to improve
- Address the high-severity findings: each costs 18 safety points. If one is a false positive, add the rule id to guard.allow in spec.yaml.
- 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 · 1
-
high Dangerous commands
cmd-pipe-to-shellreferences/template.md:88Downloads and executes remote code from an unrecognised host (pipe to shell)curl -sS https://starship.rs/install.sh | sh
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: 子页面URL - warning
missing-refreference to a missing file: URL
Process rating: all ten parameters 39/100
- 0Tools and files. 2 referenced file(s) missing: 子页面URL, URL
- 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
- 30Running it twice. 1 mutating operations with no state check
- 70When it triggers. States when to use, but not when not to
- 100Steps. 163 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3602 tokens
- low 12 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (4 tags): a typed call is more reliable
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
- -41 reference files, but SKILL.md never points to them: the model will not open them
- +1No license
- +2Single-language instructions
- +3Description length 442: enough signal without eating the budget
- +4Structure: 42 headings
- +3Step-by-step instructions: 163 items
- +4Has examples (20 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 59.