BF patent-research-analyst
科研立项专利检索与分析 Agent——输入技术问题与初步技术方案，自动执行「信息收集→多轮专利检索→五维分析（技术路线/立项查新/FTO风险/竞对跟踪/新公开专利）→HTML+Word双格式报告输出」全流程。融合 PatSnap 智慧芽全球专利数据，生成包含7章正文+3个附录的完整专利分析报告。触发词：专利检索分析、立项查新、FTO分析、技术路线分析、竞对跟踪、专利风险排查、帮我做专利检索。
科研立项专利检索与分析 Agent——输入技术问题与初步技术方案，自动执行「信息收集→多轮专利检索→五维分析（技术路线/立项查新/FTO风险/竞对跟踪/新公开专利）→HTML+Word双格式报告输出」全流程。融合 PatSnap…
As a process F 35/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 · 0
✓ No critical or high findings
Files scanned: 2. 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: 链接 - note
frontmatter-keyunknown frontmatter key "copyright"
Process rating: all ten parameters 35/100
- 0Tools and files. 1 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
- 100Steps. 121 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2317 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
- -245 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +3Description length 197: enough signal without eating the budget
- +4Structure: 30 headings
- +3Step-by-step instructions: 121 items
- +4Has examples (6 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 63.