BF linkfox-skill-creator
跨境电商专业 skill 创建向导。把运营、选品、广告、物流、合规等专家脑子里的业务经验,通过 30-45 分钟的结构化访谈沉淀为 agent 可执行的高质量 skill。触发:帮我写一个 XX skill / 把我这个经验做成 skill / 封装一下我做 XX 的方法 / 把这套 SOP 变成技能 / 沉淀 XX 流程 / 生成专业 skill / 创建新技能 / 专家经验沉淀 / create a new skill
跨境电商专业 skill 创建向导。把运营、选品、广告、物流、合规等专家脑子里的业务经验,通过 30-45 分钟的结构化访谈沉淀为 agent 可执行的高质量 skill。触发:帮我写一个 XX skill / 把我这个经验做成 skill / 封装一下我做 XX 的方法 / 把这套 SOP 变成技能 / 沉淀…
As a process F 33/100 · Will not run — References files that are not bundled: scripts/*.py, scripts/api_call.py, references/interview-record.md
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 · 1
✓ No critical or high findings
Medium and low: 1
-
low Secrets in code
secret-high-entropy-tokenreferences/interview-record-schema.md:313High-entropy token-like string (may be an id, hash or a credential)privacy_review: no_s…:00+08:00
Files scanned: 27. 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: scripts/*.py - warning
missing-refreference to a missing file: scripts/api_call.py - warning
missing-refreference to a missing file: references/interview-record.md - warning
missing-refreference to a missing file: templates/SKILL.md.tpl - warning
missing-refreference to a missing file: templates/script-skeleton.py.tpl - note
frontmatter-keyunknown frontmatter key "authored_by"
Process rating: all ten parameters 33/100
- 0Tools and files. 5 referenced file(s) missing: scripts/*.py, scripts/api_call.py, references/interview-record.md
- 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. 3 mutating operations with no state check
- 100Steps. 44 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1709 tokens
- 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
- +1No license
- +2Single-language instructions
- +3Description length 213: enough signal without eating the budget
- +4Structure: 17 headings
- +3Step-by-step instructions: 44 items
- +4Has examples (2 code blocks)
- +4Reference files are cited in the instructions (9 of 9)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 63.