BD xiaohongshu-ai-feed
AI小红书信息源 — 每日自动扫描小红书 AI 相关笔记，按互动量（点赞/分享/评论）筛选最火内容，智能聚类生成精美 HTML 日报，支持封面图、数据指标和每日订阅。当用户需要 AI 小红书日报、小红书AI热点、AI小红书内容、小红书信息源、xhs ai feed 时使用。
AI小红书信息源 — 每日自动扫描小红书 AI 相关笔记，按互动量（点赞/分享/评论）筛选最火内容，智能聚类生成精美 HTML 日报，支持封面图、数据指标和每日订阅。当用户需要 AI 小红书日报、小红书AI热点、AI小红书内容、小红书信息源、xhs ai feed 时使用。
As a process D 46/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 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
- 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 · 5
✓ No critical or high findings
Medium and low: 5
-
medium Dangerous commands
cmd-persistencescripts/fetch_xhs_ai.py:472Persistence mechanism (cron / launchd / scheduled task / autorun registry) (string literal in code, not executed)f'(crontab -l 2>/dev/null; echo "{cron_line}") | crontab -',code literal -
low Dangerous commands
cmd-cron-mentionscripts/fetch_xhs_ai.py:472Mentions editing / listing crontab (string literal in code, not executed)f'(crontab -l 2>/dev/null; echo "{cron_line}") | crontab -',code literal -
low Dangerous commands
cmd-cron-mentionscripts/fetch_xhs_ai.py:503Mentions editing / listing crontab (string literal in code, not executed)f'crontab -l 2>/dev/null | grep -v "{script_path}" | crontab -',code literal -
low Dangerous commands
cmd-cron-mentionscripts/fetch_xhs_ai.py:509Mentions editing / listing crontab (string literal in code, not executed)warn("自动移除 crontab 失败，请手动执行: crontab -e")code literal -
low Dangerous commands
cmd-shell-rcSKILL.md:57Writes to a shell startup file (documentation table row)| 写入 shell 配置 | `echo 'export REDFOX_API_KEY=ak_你的密钥' >> ~/.zshrc && source ~/.zshrc` |
table
Files scanned: 6. 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 46/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
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 100Steps. 5 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 506 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 137: enough signal without eating the budget
- +4Structure: 9 headings
- +3Step-by-step instructions: 5 items
- +4Has examples (2 code blocks)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.