About this skill

Problem

When tracking competitor technology, teams often face scattered public patent documents: which granted patents create infringement risk, which published applications can be challenged, which are only design or utility patents, and how to convert findings into R&D avoidance and legal actions is not obvious. Manual searching, reading, and clustering is costly and hard to standardize for decision-making.

How It Works

After inputting the competitor's full registered company name, the skill calls a backend MCP service to retrieve public patent intelligence and output a fixed Strategic Threat Matrix: granted inventions, published inventions, granted utility models, and design patents. It then clusters patents into about three technology groups, breaking down technical breakthroughs, product iteration intent, business motives, and market positioning. It also prioritizes defense actions by P0 / P1, including public comments, claim vulnerabilities, avoidance designs, blank spaces, substitute R&D, and budget stop-loss suggestions.

Boundaries

The skill depends on an accurate full company name and requires UTF-8 byte-array encoding for request parameters; abbreviations or nicknames may cause retrieval failures. It analyzes publicly available CNIPA data, does not cover undisclosed confidential technology, and is not a legal opinion. Outputs are useful for R&D planning, legal risk assessment, and business strategy discussion, but should not replace patent search reports or attorney advice.

Screenshots

Use Cases

Before product planning, generate a granted and published patent matrix from a competitor's full company name to identify risky tech routes.
Before an R&D sync, cluster a competitor's public patents into tech groups and prepare avoidance and substitute R&D options.
For a legal monthly report, shortlist soon-to-be-granted published patents and compile public comment and claim challenge points.
During budget review, identify saturated competitor patent barriers and propose stopping low-return projects.

Best For

R&D engineers planning new products: need to assess competitor patent risk and choose avoidance paths before launch.
Legal counsel doing patent alerts: need to extract P0/P1 infringement risks and response materials from public patents.
Product owners deciding tech direction: need to understand competitor tech clusters and positioning intent.
R&D budget owners: need to identify high-barrier domains and decide which projects to stop.