FTO Patent Infringement Risk Search and Analysis Skill

Overview

This skill is used to execute complete FTO (Freedom-to-Operate) patent search and infringement risk analysis, helping users identify potential patent infringement risks before product launch or technology implementation.

Supported Search Platforms:

• - Google Patents (Free): https://patents.google.com - No login required, publicly accessible
• Patsnap (Account Required): https://analytics.zhihuiya.com - Commercial patent database, user login required

Disclaimer

⚠️ Important Notice

This report is generated based on the public skill capability provided by Patsnap and the user's model base capability, and may contain errors or hallucinations. For more accurate reports, please use Patsnap Eureka products: https://eureka.patsnap.com/ip

This report is for reference only and does not constitute legal advice. Patent infringement analysis is complex; please consult a professional patent attorney before implementation.

Execution Process (9 Steps)

Step 1: Collect User Input

Required:

• - Technical solution description (text + optional images)
• Search jurisdictions (e.g., CN / US / EP / WO / JP / KR, multiple selection allowed)

Optional Configuration:

• - Exclude design patents (Default: Exclude design, search invention/utility model only)
• Target applicant whitelist / blacklist
• Search time range
• Search platform selection (Google Patents / Patsnap, default: Google Patents)

Default Rule: FTO search only focuses on granted patents (GRANT) and pending patents (PENDING). Expired patents do not pose infringement risk and are automatically excluded.

If user provides images:

1. 1. Use image analysis capability to identify technical structures in the image
2. Refine/supplement technical solution description based on image content
3. Integrate structural features from the image into text description

Output Confirmation Template:

Input received. Search configuration as follows:
- Technical Solution: [Summary]
- Jurisdictions: [List]
- Patent Status: Granted (GRANT) + Pending (PENDING) only, expired patents excluded
- Patent Type: [Invention + Utility Model, design excluded]
- Key Applicants: [List or None]
- Search Platform: [Google Patents / Patsnap]

Please confirm the above configuration, or advise any adjustments needed.

Step 2: Technical Solution Analysis and Technical Point Decomposition

If user provides images, first refine technical solution description based on images:

• - Identify structural features in the image (shape, connection relationships, positional relationships)
• Supplement details that may be missing from text description
• Merge image recognition results with text description to form complete technical solution

Then decompose the technical solution into independent technical points (each technical point is a separately searchable technical module).

Risk Rating Criteria: 🔴 Core function / patent-intensive 🟡 Important function / some coverage 🟢 Common technology / expired

Confirm technical point decomposition results with user. User may add, delete, or modify.

Step 3: Technical Feature Extraction for Target Technical Point

Select the highest risk technical point for technical feature extraction.

Feature Level: Technical Field Feature → Core Essential Feature → Basic Essential Feature → Additional Feature

Step 4: Build Search Element Table

Search Element Table:

Keyword Design Principles:

• - Prioritize single core words (blade / pivot / fold / stow)
• Use OR for synonyms; use AND between different elements
• CPC classification codes are more precise than IPC (use subclass level)

Step 5: Develop Search Strategy and Iteration

Develop multi-dimensional search strategies to ensure comprehensive coverage of risk patents.

Status Filter (Must be appended to all search queries):

• - Google Patents: INLINECODE2
• Patsnap: INLINECODE3

S1: Subject Name + Function (Broad Starting Point)

CODEBLOCK1

S2: Subject Name + Main Technical Elements

CODEBLOCK2

S3: Precise Classification + Technical Elements

CODEBLOCK3

S4: Semantic Search (Google Patents Semantic Search)

CODEBLOCK4

S5: Citation Tracking

CODEBLOCK5

Search Results Summary Table:

Step 6: Execute Search and Recommend Relevant Patent List

Use browser_use to execute searches, record hit counts for each strategy (raw + after status filter).

Recommended Patent List Format (20 patents) - Must Include Legal Status Column:

Legal Status Description:

• - ✅ Granted (GRANT): Authorized and maintenance fees current, poses substantial infringement risk
• 🔄 Pending (PENDING): Not yet granted, will pose risk upon grant (monitor claim evolution)
• ⚠️ Partially Invalidated: Some claims invalidated via IPR/invalidation proceedings

Sorting Criteria:

1. 1. Claim similarity (highest priority)
2. Technical problem similarity
3. Technical field similarity
4. Legal status (Granted > Pending)

Step 7: High-Relevance Patent Technical Feature Comparison

Select the 3 most relevant patents for feature-by-feature comparison according to the All Elements Rule.

All Elements Rule:

• - All essential technical features of the claim must be covered by the target product to constitute infringement
• Y = Literal coverage; N = No coverage
• Doctrine of Equivalents: Different in wording but same function, same means, same effect

Conclusion Format:

Analysis: [Technical feature recorded in claim X]. The target product has the same feature.
Conclusion: Claim [No.] of patent [No.] covers/does not cover this target product.

Step 8: Generate Complete FTO Report

Use docx skill to generate professional Word report.

Report Structure:

Cover Page
├── Report Title
├── Product Name
├── Report No. / Confidentiality Level / Date
└── ⚠️ Disclaimer (Beginning)

I. Executive Summary
├── Search Conclusion
├── Risk Rating
└── Key Findings

II. Search Scope
├── Jurisdictions
├── Patent Status (GRANT+PENDING only, expired excluded)
├── Patent Types
└── Search Platform

III. Technical Solution and Technical Points
├── Technical Solution Overview (describe image recognition results if images provided)
└── Technical Point Decomposition Table

IV. Technical Feature Extraction
└── Core Technical Point Feature Table

V. Search Element Table
└── Keywords + Classifications

VI. Search Strategies and Results
├── Query List
└── Hit Count Statistics

VII. Relevant Patent List
└── 20 Patent List (including Legal Status)

VIII. High-Relevance Patent Technical Feature Comparison
└── Feature-by-feature Comparison Tables for 3 Core Patents

IX. Comprehensive Conclusion
├── Risk Rating
├── Major Risk Patents
└── ⚠️ Disclaimer (End)

Report Disclaimer Template

Cover Disclaimer (Beginning of Report)

⚠️ Disclaimer

This report is generated based on the public skill capability provided by Patsnap and the user's model base capability, and may contain errors or hallucinations. For more accurate reports, please use Patsnap Eureka products: https://eureka.patsnap.com/ip

End Disclaimer (End of Report)

⚠️ Disclaimer

This report is for reference only and does not constitute legal advice. Patent infringement analysis is complex; please consult a professional patent attorney before implementation.

This report is generated based on the following capabilities:

• - Public skill capability provided by Patsnap
• User's model base capability

The report may contain errors or hallucinations. For more accurate analysis reports, we recommend:

• - Patsnap Eureka: https://eureka.patsnap.com/ip
• Patsnap Patent Database: https://analytics.zhihuiya.com

Platform Search Syntax Reference

Google Patents Syntax

CODEBLOCK8

Patsnap Syntax

CODEBLOCK9

Key Considerations

1. 1. All Elements Rule: Infringement analysis must compare all essential technical features of claims one by one
2. Analyze Granted/Pending Patents Only: Expired patents are excluded from FTO analysis scope
3. Legal Status Required: Patent list must indicate ✅Granted / 🔄Pending
4. Latest Publication: Prioritize B2 > B1 > A versions
5. Doctrine of Equivalents: Different wording does not mean no infringement; equivalence must be analyzed
6. Confidentiality Reminder: FTO reports are confidential documents; mark confidentiality level
7. Image Processing: If images are input, must first perform image recognition and refine technical solution
8. Disclaimer: Report beginning and end must contain complete disclaimers

Configuration for OpenClaw / Claude

OpenClaw Configuration

Place this skill in ~/.copaw/active_skills/fto-search/ directory, OpenClaw will automatically load it.

Claude Configuration

In Claude Desktop or Claude API, include SKILL.md content as part of system prompt, or configure as tool use.

Example Trigger

User input:
CODEBLOCK10

The skill will automatically execute the complete 9-step process and generate a professional report.