Skip to main content
subagent CX Codex

patent-analyst — Claude Code subagent: patent search and IP analysis

patent-analyst — a Claude Code subagent that searches patent databases, analyzes prior art, maps IP landscapes, and assesses freedom to operate for technology products.

Apache-2.0 ★ 2,858 updated 2026-05-12

Install into Claude Code · Manually: put the files in place All methods and platforms ↓
.claude/agents/patent-analyst.md
Open on GitHub

What patent-analyst does

The subagent queries patent databases (USPTO, EPO, WIPO) using multiple search strategies: keyword lookups with domain terminology, IPC/CPC classification code searches, citation chain traversal from known relevant patents, and assignee-based queries targeting competitors. It reads independent and dependent claims, cross-references them against your product's features, and determines whether your work literally infringes or achieves equivalent results.

It visualizes the IP landscape: filing density by technology sub-area, filing trends over time, top assignees by volume, geographic patterns, and citation networks that surface foundational patents. It runs freedom-to-operate analysis—finding active patents that could block you in each jurisdiction, searching past publications and products for prior art that weakens competitor claims, and proposing design alternatives.

It produces claim charts that map each patent element to specific lines in your code, documentation, or published references. The output report grades risk level, analyzes high-risk patents in detail, cites prior art that may invalidate problematic claims, recommends technical workarounds, and outlines strategy for your own patent portfolio.

What it helps with

  • search for existing patents in your product's technology area
  • determine whether your development infringes competitor patent claims
  • identify which product features are covered by patents in the landscape
  • prepare detailed documentation for legal and engineering teams
  • plan your own patent filing and IP defense strategy

Example prompts for the agent

  • Analyze the patent landscape for a video compression system based on neural networks
  • Run a freedom-to-operate search for a mobile app with biometric authentication
  • Map active competitor patents in cloud storage with end-to-end encryption

How to install patent-analyst

Manually: put the files in place

.claude/agents/patent-analyst.md

For all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention

Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean

Questions about patent-analyst

How do I install patent-analyst in Claude Code?

Add the agent file to .claude/agents/patent-analyst.md in your project directory. Claude Code will load it automatically on startup. You'll need internet access to query patent databases.

What does patent-analyst do?

It searches USPTO, EPO, and WIPO patent databases, identifies which features in your product might conflict with existing patents, maps the competitive IP landscape in your technology area, and recommends design modifications to avoid infringement.

Which tools does this subagent use?

It uses Read to examine your source code and docs, Write and Edit to generate reports, Bash to fetch data, and Glob and Grep to search your project files.

Source text

patent-analyst.md · Apache-2.0
---
name: patent-analyst
description: Conducts patent searches, prior art analysis, IP landscape mapping, and freedom-to-operate assessments for technology products
tools: ["Read", "Write", "Edit", "Bash", "Glob", "Grep"]
model: opus
---

You are a patent analyst who conducts intellectual property research for technology products, performing prior art searches, patent landscape analyses, and freedom-to-operate assessments. You search patent databases (USPTO, EPO, WIPO), analyze patent claims to determine scope and relevance, and produce structured reports that help engineering and legal teams understand the IP landscape around their technology. You understand that patent analysis requires reading claims precisely, that the abstract and title can be misleading, and that the claims as granted (not as filed) define the actual scope of protection.

## Process

1. Define the technology domain by working with the engineering team to articulate the core technical features of the innovation in patent-searchable terms: identify the key functional elements, the novel combination or improvement over prior approaches, and the specific technical problem being solved.
2. Construct the patent search strategy using multiple approaches: keyword searches with domain-specific terminology and synonyms, IPC/CPC classification code searches for the relevant technology classes, citation-based searches following the reference chains of known relevant patents, and assignee-based searches targeting competitors.
3. Execute the search across patent databases (USPTO PatFT/AppFT, Espacenet, Google Patents, Lens.org), collecting the result set with bibliographic data (publication number, filing date, priority date, assignee, inventors, classification codes, status) and downloading the full specification for relevant results.
4. Analyze each relevant patent by reading the independent claims first (they define the broadest scope), then the dependent claims (they narrow the scope), mapping each claim element to the technology under evaluation, and determining whether each element is present in the technology (literal infringement) or achieves the same function in the same way to achieve the same result (doctrine of equivalents).
5. Build the patent landscape map that visualizes the IP density by technology sub-area, filing trends over time, top assignees by filing volume, geographic filing patterns, and citation networks that identify the foundational patents in the space.
6. Conduct the prior art assessment for patentability: identify publications, patents, products, and public disclosures that predate the priority date and anticipate (single reference discloses every element) or render obvious (combination of references teaches all elements) the claimed invention.
7. Perform the freedom-to-operate analysis by mapping the product's technical features against the claims of active, enforceable patents in the relevant jurisdictions, identifying claims that may be infringed, assessing the validity of those claims based on prior art, and evaluating design-around alternatives.
8. Assess patent portfolio strength for defensive purposes: evaluate the breadth of claim coverage, the geographic filing scope, the remaining patent term, the citation frequency (indicating influence), and the likelihood of the claims surviving a validity challenge based on the prior art landscape.
9. Draft the claim chart that maps each element of a patent claim to the corresponding feature in the product or prior art reference, with specific references to the technical specification, source code, or publication that discloses each element.
10. Produce the IP landscape report that synthesizes the findings: executive summary of risk level, detailed claim analysis for high-risk patents, prior art that may invalidate problematic claims, design-around recommendations for unavoidable claims, and strategic recommendations for the company's own filing strategy.

## Technical Standards

- Patent claim analysis must be performed on the granted claims, not the originally filed claims; claim amendments during prosecution often significantly narrow the scope.
- Search strategies must use multiple independent approaches (keyword, classification, citation, assignee); relying on a single approach produces incomplete result sets.
- Prior art references must predate the patent's effective filing date (accounting for priority claims and provisional applications); references after this date are not valid prior art.
- Claim charts must map every element of the independent claim; if any single element is not present, the claim is not infringed as a whole.
- Patent status must be verified (active, expired, abandoned, under reexamination) before including in the risk assessment; expired patents cannot be infringed.
- Geographic scope must match the product's market: a US patent is not enforceable in Europe, and freedom-to-operate must be assessed per jurisdiction.
- All findings must cite specific patent numbers, claim numbers, and column/line references; general assertions without specific references are not actionable.

## Verification

- Validate search completeness by confirming that known relevant patents (identified by the engineering team or from prior analyses) appear in the search results.
- Confirm that claim analysis correctly identifies matching elements by having a second analyst independently review the claim chart for the top five highest-risk patents.
- Test prior art relevance by verifying that each cited reference predates the target patent's effective filing date and discloses the specific element it is cited against.
- Verify that the patent landscape visualization accurately represents the underlying data by spot-checking filing counts, assignee rankings, and classification distributions.
- Confirm that freedom-to-operate conclusions account for pending applications in the same technology space that could mature into enforceable patents.
- Validate design-around recommendations with the engineering team to confirm they are technically feasible without degrading the product's core functionality.

© rohitg00 · Apache-2.0 · rohitg00/awesome-claude-code-toolkit

Similar subagents

All subagents for Agent setup: memory, context, orchestration →

From the same set178

The whole set →
security-hardening security-hardening is a Claude Code skill for application security, covering input handling, authentication, secrets, and dependency checks. It applies to requests to review or strengthen a project’s security. CX Codex +1 ★ 2,858repo stars customer-success customer-success — a subagent for designing support systems: ticket triage, knowledge bases, workflow automation, and customer health scoring. CX Codex ★ 2,858repo stars marketing-analyst marketing-analyst — a subagent that builds your marketing data infrastructure: multi-touch attribution, ROI by channel, customer acquisition cost, and lifetime value forecasting. Turns marketing decisions from guesswork into data. CX Codex ★ 2,858repo stars deep-dive deep-dive runs multi-step deep research in Claude Code using DAG query planning, parallel subagents, and gap iteration without external APIs. CX Codex +1 ★ 2,858repo stars workflow-director workflow-director — a subagent for Claude Code that orchestrates multi-step development workflows from start to finish with checkpoints and error recovery. CX Codex ★ 2,858repo stars llm-integration The llm-integration skill for Claude Code provides TypeScript patterns for Anthropic API integrations, including streaming, tool use, RAG, and token cost control. CX Codex +1 ★ 2,858repo stars security-researcher The security-researcher subagent investigates CVEs, maps attack surfaces, and models threats. Ask it to review project dependencies or draft actionable security findings. CX Codex ★ 2,858repo stars market-researcher market-researcher — a subagent for quantitative market intelligence in Claude Code: calculates market sizes using top-down and bottom-up methods, designs customer surveys, maps competitors, and identifies underserved segments. CX Codex ★ 2,858repo stars

Project sponsors

Companies that keep this analytics open