AB screen-cross-border-patent-risk-ip
Perform a preliminary cross-border patent and design-right risk screen for an e-commerce or consumer product using product images, a product page, or a technical description. Use when a seller, importer, manufacturer, product team, or IP analyst asks about patent risk, FTO screening, product-launch risk, market-entry risk, design patents, registered designs, utility models, or possible design-around options in one or more target markets. Analyze technical patents, utility models where available, and jurisdiction-appropriate design rights; provide evidence-backed market-specific risk triage, not legal clearance.
Perform a preliminary cross-border patent and design-right risk screen for an e-commerce or consumer product using product images, a product page, or a…
As a process B 70/100 · Nearly there — weak spots: inputs and preconditions, running it twice, progress reporting
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
- note
frontmatter-keyunknown frontmatter key "copyright"
Process rating: all ten parameters 70/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 3 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 60Result and completion. Output format stated, no completion criterion
- 70Execution cost. Instruction body is 4120 tokens
- 85Steps. 145 steps, 1 vague phrases
- 100Tools and files. No external tools needed
- 100When it triggers. States when to use and when not to
- 100Consistency. Name and required fields are in place
- low 11 top-level sections: this looks like several domains in one skill
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)
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 618: enough signal without eating the budget
- +4Structure: 39 headings
- +3Step-by-step instructions: 145 items
- +3Output format is stated explicitly
Quality base 70; lint remarks subtract, signals add up to 100. Result: 82.