AC applicant-tech-patent-retrieval
面向指定申请人并限定技术主题开展专利检索。适用于用户需要检索某公司/申请人在特定技术领域的专利、构建“申请人优先 + 技术主题约束”的智慧芽检索式、扩展申请人法律主体和名称变体、拆解技术主题为可检索要素、组合申请人表达式与主题公式、按申请和简单同族去重，并生成检索数据集及 Markdown/Word 报告的场景。不适用于没有技术主题限制的纯申请人全量检索、没有目标申请人的纯技术全景分析，或检索完成后的下游技术筛选任务。
面向指定申请人并限定技术主题开展专利检索。适用于用户需要检索某公司/申请人在特定技术领域的专利、构建“申请人优先 + 技术主题约束”的智慧芽检索式、扩展申请人法律主体和名称变体、拆解技术主题为可检索要素、组合申请人表达式与主题公式、按申请和简单同族去重，并生成检索数据集及 Markdown/Word…
As a process C 53/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.
- 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: 5. 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") - note
frontmatter-keyunknown frontmatter key "copyright"
Process rating: all ten parameters 53/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
- 100Tools and files. No external tools needed
- 100Steps. 149 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2648 tokens
- 100Running it twice. No mutating operations
- low The response is described with custom markup (3 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
- +1No license
- +2Single-language instructions
- +3Description length 211: enough signal without eating the budget
- +4Structure: 18 headings
- +3Step-by-step instructions: 149 items
- +4Has examples (10 code blocks)
- +4Reference files are cited in the instructions (2 of 2)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.