BF wechat-creator
公众号内容创作与运营分析聚合技能。一个 Skill 覆盖公众号创作与运营全链路:10w+ 爆文榜单、爆款正文创作、标题生成+评分、文案改写(含改写记录自动上报)、违禁词检测、爆款封面设计、账号四维度诊断。基于红狐数据每日收录的海量公众号爆款数据,把灵感打磨成可直接发布的成品。当用户需要写公众号文章、起标题或评估标题、改写文案、设计封面、检测违禁词、查 10w+ 爆文、诊断公众号账号时使用。触发词:公众号、公众号文章、公众号标题、公众号改写、公众号封面、公众号违禁词、10w+、爆文、账号诊断。
公众号内容创作与运营分析聚合技能。一个 Skill 覆盖公众号创作与运营全链路:10w+…
As a process F 34/100 · Will not run — References files that are not bundled: 文章链接, 公众号名片链接, 链接
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/check_sensitive_words.py:66Hard-coded password / key literal (may be an example)api_key = match.group(1).strip()
-
low Dangerous commands
cmd-shell-rcSKILL.md:77Writes to a shell startup file (quoted — discussed, not commanded)- macOS/Linux(zsh):`echo 'export REDFOX_API_KEY=ak_xxx' >> ~/.zshrc && source ~/.zshrc`
quoted
Files scanned: 23. 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: 公众号名片链接 - warning
missing-refreference to a missing file: 链接 - note
frontmatter-keyunknown frontmatter key "dependency"
Process rating: all ten parameters 34/100
- 0Tools and files. 3 referenced file(s) missing: 文章链接, 公众号名片链接, 链接
- 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
- 70Execution cost. Instruction body is 4766 tokens
- 100Steps. 114 steps
- 100Consistency. Name and required fields are in place
- 100Running it twice. No mutating operations
- low 14 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
- -212 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +3Description length 248: enough signal without eating the budget
- +4Structure: 56 headings
- +3Step-by-step instructions: 114 items
- +4Has examples (23 code blocks)
- +4Reference files are cited in the instructions (8 of 8)
- +3All 8 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 64.