BF patent-panorama-insights-report
在专利全景项目的环节 4/4（环节4）使用本技能。它会把环节2统计/价值信号、环节3标引体系（tech_breakdown / key_questions / patent_packages）以及 SaaS 回流的 tagged_pool 转化为技术演进路线、护城河/价值交叉解读，并生成自包含 HTML 洞察报告（report.html + report_manifest.json）。
在专利全景项目的环节 4/4（环节4）使用本技能。它会把环节2统计/价值信号、环节3标引体系（techbreakdown / keyquestions / patentpackages）以及 SaaS 回流的 taggedpool 转化为技术演进路线、护城河/价值交叉解读，并生成自包含 HTML…
As a process F 33/100 · Will not run — References files that are not bundled: examples/大模型联盟专利洞察/outputs/report.html
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: 3. 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: examples/大模型联盟专利洞察/outputs/report.html - note
frontmatter-keyunknown frontmatter key "copyright"
Process rating: all ten parameters 33/100
- 0Tools and files. 1 referenced file(s) missing: examples/大模型联盟专利洞察/outputs/report.html
- 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. 68 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3543 tokens
- low 13 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 194: enough signal without eating the budget
- +4Structure: 20 headings
- +3Step-by-step instructions: 68 items
- +4Has examples (3 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 65.