BF xiaohongshu-inspiration
小红书内容灵感聚合技能,覆盖选题灵感全链路:关键词爆款笔记搜索(相关性/热度/时效三维评分)、批量获取作品数据(支持 Excel/HTML 导出)、每日爆款 TOP50 爆发榜、低粉爆款挖掘(粉丝<5000 点赞>500)、账号日/周/月榜 TOP50、同阶对标与高阶标杆推荐。当用户需要小红书灵感、爆款搜索、笔记查询、批量获取作品、每日爆款、低粉爆款、账号榜单、涨粉榜、对标账号推荐时使用。触发词:小红书灵感、小红书爆款、小红书搜索、小红书爬取、每日爆款、低粉爆款、小红书榜单、日榜周榜月榜、对标账号。严禁任何联网搜索。
As a process F 33/100 · Will not run — References files that are not bundled: 链接, work_url
The same skill appears in 1 more place: ClawHub
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 · 2
✓ No critical or high findings
Medium and low: 2
-
low Secrets in code
secret-password-literalscripts/fetch_explosive_articles.py:152Hard-coded password / key literal (may be an example)api_key = match.group(1).strip()
-
low Dangerous commands
cmd-shell-rcSKILL.md:47Writes to a shell startup file (security demo / example; quoted — discussed, not commanded)配置示例:`echo 'export REDFOX_API_KEY=ak_xxx' >> ~/.zshrc && source ~/.zshrc`;验证:`echo $REDFOX_API_KEY`。Windows:`[Environment]::SetEnvironmentVariable("REDFOX_API_KEY", "<值>", "User")` 后重启终端。demoquoted
Files scanned: 22. 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: 链接 - warning
missing-refreference to a missing file: work_url - note
frontmatter-keyunknown frontmatter key "dependency"
Process rating: all ten parameters 33/100
- 0Tools and files. 2 referenced file(s) missing: 链接, work_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
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 1 mutating operations with no state check
- 100Steps. 41 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2521 tokens
- low 11 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)
- +3Output format is not stated: the model decides each time
- -239 emoji in the instructions: noise for the model
- -31 of 10 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 261: enough signal without eating the budget
- +4Structure: 30 headings
- +3Step-by-step instructions: 41 items
- +4Has examples (12 code blocks)
- +4Reference files are cited in the instructions (5 of 5)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 61.