BD 阅读笔记
阅读笔记管理工具。当用户发送文章链接并说「阅读笔记」时激活。 支持微信公众号、微博、雪球、B站等平台的文章抓取。 自动分类到飞书云盘，生成 Markdown 格式阅读笔记。 触发条件： - 发送文章链接 + "阅读笔记" - "帮我记一下这篇文章" - "保存这篇文章"
As a process D 49/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The files contain someone else's key or token. If it is live, your agent will call third-party services under a stranger's identity; if it was revoked, the skill's scripts simply fail. Such a key often arrives with the author's whole workspace, personal data included.
The key is visible to everyone who downloaded the skill and has likely been copied by catalog-scanning bots already. Revoke it now, check bills and access logs, then reissue.
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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 · 4
✓ No critical or high findings
Medium and low: 4
-
medium Secrets in code
secret-labelled-tokenSKILL.md:85Labelled token / key literal (vendor format unknown — verify it is not a live credential)app_secret = "usgK…5CE"
-
medium Secrets in code
secret-labelled-tokenSKILL.md:414Labelled token / key literal (vendor format unknown — verify it is not a live credential)app_secret = "usgK…5CE"
-
low Secrets in code
secret-high-entropy-tokenSKILL.md:85High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)app_secret = "usgK…5CE"
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:414High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)app_secret = "usgK…5CE"
quoted
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 49/100
- 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
- 40Consistency. Frontmatter name (阅读笔记) differs from the folder (feishu-reading-notes)
- 100Tools and files. No external tools needed
- 100Steps. 36 steps
- 100Execution cost. Instruction body is 2236 tokens
- 100Running it twice. No mutating operations
- low 10 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
- -217 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +5Description quotes 2 example trigger phrases
- +3Description length 136: enough signal without eating the budget
- +4Structure: 35 headings
- +3Step-by-step instructions: 36 items
- +4Has examples (20 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 70.