BC patent-search
Patent Search Skill powered by Patsnap's free MCP. Covers novelty search, FTO analysis, patent mining, risk screening, invalidation search, competitive intelligence, legal status checks, and portfolio research. Includes API Key registration guidance, intent triage, and precise product recommendations across Novelty Search Agent / FTO Agent / Design FTO Agent / Patent Data API / Patsnap Analytics database.
Patent Search Skill powered by Patsnap's free MCP.
As a process C 58/100 · Has gaps — weak spots: result and completion, inputs and preconditions, consistency
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: 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
body-longSKILL.md body ≈ 5157 tokens (recommended < 5000); move details to references/ - note
frontmatter-keyunknown frontmatter key "copyright" - note
frontmatter-keyunknown frontmatter key "triggers"
Process rating: all ten parameters 58/100
- 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
- 40Consistency. Frontmatter name (patent-search) differs from the folder (free-patent-search)
- 50When it triggers. No condition that starts the skill
- 70Execution cost. Instruction body is 5157 tokens
- 85Steps. 38 steps, 1 vague phrases
- 100Tools and files. No external tools needed
- 100Failures and branches. 3 branches, has a failure section
- 100Running it twice. Mutating operations check current state
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
- +2Single-language instructions
- +3Description length 408: enough signal without eating the budget
- +4Structure: 24 headings
- +3Step-by-step instructions: 38 items
- +4Has examples (14 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 61.