BF patent-panorama-insights-stats
用于专利全景项目的环节2。它消费 patent-panorama-insights-search（环节1）产出的已验证 `search_config.json`、`candidate_pool.csv` 和 `core_recall.csv`，生成全景统计（趋势、申请人格局、技术构成、竞品画像）、按分支组织的核心专利索引（默认采信环节1召回排序，仅在必要时做有边界的兜底核查）和价值信号交叉挖掘文件。所有统计直接从检索式聚合，不需要逐件专利标引。
用于专利全景项目的环节2。它消费 patent-panorama-insights-search（环节1）产出的已验证 searchconfig.json、candidatepool.csv 和…
As a process F 40/100 · Will not run — References files that are not bundled: examples/大模型联盟专利洞察/outputs/panorama_stats_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/panorama_stats_report.html - note
frontmatter-keyunknown frontmatter key "copyright"
Process rating: all ten parameters 40/100
- 0Tools and files. 1 referenced file(s) missing: examples/大模型联盟专利洞察/outputs/panorama_stats_report.html
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 50Failures and branches. 0 branches, has a failure section
- 100Steps. 75 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3861 tokens
- 100Running it twice. No mutating operations
- low 18 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 224: enough signal without eating the budget
- +4Structure: 28 headings
- +3Step-by-step instructions: 75 items
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 65.