BC fto-search
FTO (Freedom-to-Operate) patent infringement risk search and analysis skill. Use this skill when users need FTO search, patent infringement analysis, patent risk assessment, competitor patent investigation, or pre-launch patent search. Supports text description or image input, searches via Google Patents or Patsnap, outputs complete FTO analysis report (with feature comparison table, search queries, relevant patent list, infringement risk conclusion). Trigger keywords: FTO, patent infringement, patent search, patent risk, technical feature comparison, Freedom to Operate.
As a process C 52/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- 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
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 2, column 14: description: FTO (Freedom-to-Operate) patent infringement risk search and analy… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value
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
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 3 mutating operations with no state check
- 40Consistency. Frontmatter name (fto-search) differs from the folder (patent-fto)
- 65Failures and branches. 3 branches
- 100Tools and files. No external tools needed
- 100Steps. 37 steps
- 100Execution cost. Instruction body is 3486 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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
- -218 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +3Description length 577: enough signal without eating the budget
- +4Structure: 28 headings
- +3Step-by-step instructions: 37 items
- +4Has examples (11 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.