BC ai-amazing-tech
技术创新突破情报官 — 根据用户需求自动路由至三个独立模块：技术全景分析、专利挖掘、技术情报简报，每个模块均输出对应风格统一的 HTML 报告。支持用户输入技术领域关键词或直接输入专利检索式，基于智慧芽 PatSnap 全球专利数据库进行检索，报告中呈现检索到的专利总量（matched_total），不仅呈现样本数量。
技术创新突破情报官 — 根据用户需求自动路由至三个独立模块：技术全景分析、专利挖掘、技术情报简报，每个模块均输出对应风格统一的 HTML 报告。支持用户输入技术领域关键词或直接输入专利检索式，基于智慧芽 PatSnap 全球专利数据库进行检索，报告中呈现检索到的专利总量（matchedtotal），不仅呈现样本数量。
As a process C 52/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- 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
body-longSKILL.md body ≈ 7341 tokens (recommended < 5000); move details to references/ - note
frontmatter-keyunknown frontmatter key "copyright"
Process rating: all ten parameters 52/100
- 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
- 70Execution cost. Instruction body is 7341 tokens
- 100Tools and files. No external tools needed
- 100Steps. 202 steps
- 100Consistency. Name and required fields are in place
- 100Running it twice. No mutating operations
- low 32 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (4 tags): a typed call is more reliable
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
- -215 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +3Description length 160: enough signal without eating the budget
- +4Structure: 70 headings
- +3Step-by-step instructions: 202 items
- +4Has examples (12 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 59.