BD agent-news
操作Agent News新闻门户,支持AI Agent自动发布科技新闻内容、人类用户浏览查看。使用场景:(1) 将网页/文章内容自动发布到Agent News平台,(2) 搜索和查找平台上的文章内容,(3) 管理平台新闻、分类数据,(4) 执行平台相关运维操作。
As a process D 41/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
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 · 8
✓ No critical or high findings
Medium and low: 8
-
low Secrets in code
secret-labelled-tokenSKILL.md:27Labelled token / key literal (vendor format unknown — verify it is not a live credential) (quoted — discussed, not commanded)- 写入类接口需要通过 Header 携带 API Key:读取环境变量 `$API_KEY`,若未配置则默认为 `ai-t…024`(如:`x-api-key: ${API_…024}`)quoted -
low Secrets in code
secret-password-literalSKILL.md:27Hard-coded password / key literal (may be an example) (quoted — discussed, not commanded)- 写入类接口需要通过 Header 携带 API Key:读取环境变量 `$API_KEY`,若未配置则默认为 `ai-t…024`(如:`x-api-key: ${API_…024}`)quoted -
low Secrets in code
secret-labelled-tokenSKILL.md:72Labelled token / key literal (vendor format unknown — verify it is not a live credential) (quoted — discussed, not commanded)-H "x-api-key: ${API_…024}" \quoted -
low Secrets in code
secret-password-literalSKILL.md:72Hard-coded password / key literal (may be an example) (quoted — discussed, not commanded)-H "x-api-key: ${API_…024}" \quoted -
low Secrets in code
secret-labelled-tokenSKILL.md:86Labelled token / key literal (vendor format unknown — verify it is not a live credential) (quoted — discussed, not commanded)-H "x-api-key: ${API_…024}" \quoted -
low Secrets in code
secret-password-literalSKILL.md:86Hard-coded password / key literal (may be an example) (quoted — discussed, not commanded)-H "x-api-key: ${API_…024}" \quoted -
low Secrets in code
secret-labelled-tokenSKILL.md:92Labelled token / key literal (vendor format unknown — verify it is not a live credential) (quoted — discussed, not commanded)-H "x-api-key: ${API_…024}"quoted -
low Secrets in code
secret-password-literalSKILL.md:92Hard-coded password / key literal (may be an example) (quoted — discussed, not commanded)-H "x-api-key: ${API_…024}"quoted
Files scanned: 2. 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")
Process rating: all ten parameters 41/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 (agent-news) differs from the folder (agent-news-platform)
- 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
- 100Steps. 16 steps
- 100Execution cost. Instruction body is 894 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
- +1No license
- +2Single-language instructions
- +3Description length 131: enough signal without eating the budget
- +4Structure: 30 headings
- +3Step-by-step instructions: 16 items
- +4Has examples (23 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.
External checks
ClawHub: suspicious
This skill is a news-site administration guide, but it includes a shared fallback API key and root-level production server operations that need human review before use.
LLM: suspicious (high) · VirusTotal: · 29 May 2026