BF tech-evolution-analysis
基于 TRIZ 11 进化路线 + SVOP 功能化 + patsnap 四轨检索(专利+论文)的技术进化趋势分析 7 步流水线。当用户给出一个产品名称(如智能手表、AR 眼镜、扫地机器人、新能源车电池等)并希望识别该产品的进化方向、空白点、跨域类比候选、3-5-10 年下一代形态预测、灰犀牛与黑天鹅技术信号时调用。触发关键词:技术进化、进化趋势、下一代形态、TRIZ 进化树、空白点、跨域类比、技术路线图、黑天鹅信号、灰犀牛技术、技术预测
基于 TRIZ 11 进化路线 + SVOP 功能化 + patsnap 四轨检索(专利+论文)的技术进化趋势分析 7 步流水线。当用户给出一个产品名称(如智能手表、AR 眼镜、扫地机器人、新能源车电池等)并希望识别该产品的进化方向、空白点、跨域类比候选、3-5-10…
As a process F 35/100 · Will not run — References files that are not bundled: assets/README.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 · 0
✓ No critical or high findings
Files scanned: 13. 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: assets/README.md - note
frontmatter-keyunknown frontmatter key "copyright"
Process rating: all ten parameters 35/100
- 0Tools and files. 1 referenced file(s) missing: assets/README.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
- 100Steps. 51 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1184 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
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 221: enough signal without eating the budget
- +4Structure: 10 headings
- +3Step-by-step instructions: 51 items
- +4Reference files are cited in the instructions (6 of 6)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 65.