patent — Claude Code plugin: prior-art and IP landscape search
A Claude plugin for patent work: prior art, freedom-to-operate, competitive landscape. Output is an editable .docx with a verdict and ranked hits.
/plugin marketplace add alirezarezvani/claude-skills
/plugin install patent@claude-code-skillsWhat patent does
This plugin will not act as generic patent help. Before any search starts, it makes you pick one of five sub-use-cases: novelty, freedom-to-operate, competitive landscape, acquisition diligence, or litigation prior-art. That choice drives the search strategy, the ranking, and what the report stresses.
Inside sit an agent cs-patent, a slash command cs-patent, and the patent skill with three scripts: citation_tracker.py, family_resolver.py, sub_use_case_router.py. Searches run against Google Patents, Espacenet and USPTO, with WebSearch covering academic work adjacent to patents. You get a Word file with a verdict, the closest art with claim text pulled out, a CPC-class landscape, family-resolved hits and a full audit log.
Requirements: web_fetch, WebSearch, bash_tool with curl, and the Node.js docx library. A Lens.org key is optional and BYOK — supply one and the report gains a citation-graph section. Trademarks, copyright and trade secrets fall outside its scope, and it says so at intake. Treat the output as search signal, not legal advice: the plugin tells you to see a patent attorney before filing or licensing.
What it helps with
- check whether a product infringes someone's active patents
- test an invention for novelty before filing
- map patents in a field and see which filers are most active
- verify that a company truly owns the portfolio it claims
- find art that can knock out one specific patent in a dispute
Example prompts for the agent
- Run a prior art search for my invention — pick the sub-use-case first
- Do an FTO analysis for this product and flag risk claim by claim
- Build a patent landscape for this field, broken down by CPC class
How to install patent
Plugin marketplace
/plugin marketplace add alirezarezvani/claude-skills/plugin install patent@claude-code-skillsStep by step, with commands for each platform: Claude Code plugins: marketplaces, installing, and building your own
Questions about patent
How do I install patent in Claude Code?
Add the marketplace first: /plugin marketplace add alirezarezvani/claude-skills. Then install the plugin itself: /plugin install patent@claude-code-skills.
What does patent do?
It runs a patent search under one of five sub-use-cases — novelty, FTO, landscape, diligence or litigation prior-art — and produces a .docx with a verdict, ranked hits and an audit log.
Do I need a Lens.org key?
No, it is optional and BYOK. With a key the report gains a citation-graph section; without one, searches still cover Google Patents, Espacenet and USPTO.
Source text
patent · MIT
# patent
Patent prior-art and landscape intelligence skill. Refuses to be "generic patent help" — every invocation commits to **one of five sub-use-cases** before any search runs, and the chosen sub-use-case dictates the entire search strategy, ranking heuristics, and DOCX emphasis.
## The 5 Sub-Use-Cases
| Sub-use-case | Search strategy | DOCX emphasis |
|---|---|---|
| **Novelty search** (am I novel) | Narrow + claims-text focused | Closest art + claim-differentiation |
| **Freedom-to-operate** (will I get sued) | Broad + active patents only; jurisdiction-filtered | FTO flags + claim-by-claim risk |
| **Competitive landscape** (who plays here) | Breadth + filer tally + CPC trends | Filer map + investment hotspots |
| **Acquisition diligence** (does target really own X) | Specific assignee + portfolio scope + assignment chain | Portfolio table + ownership verification |
| **Litigation prior-art** (kill a specific patent) | Target patent + adjacent art before priority date | Knock-out candidates ranked by relevance |
**Out of scope:** trademark, copyright, trade-secret. Flagged at intake.
## Sibling skill relationship
Part of the **research pack** (sibling of `pulse`, `litreview`, `grants`, `dossier`). Shares Agent Integrity Rules. Adds:
- **Sub-use-case routing** as a non-skippable Q2 commitment (refuses generic "patent help")
- **CPC/IPC class follow-up** queries (catches art keyword search misses)
- **Family resolution** (deduplicates same-invention filings across jurisdictions)
- **Date discipline** (filing vs priority vs publication vs grant — surfaces legally-relevant date per sub-use-case)
- **Mandatory legal disclaimer** for novelty + FTO sub-use-cases
## Source spec
`megaprompts/11-patent-megaprompt.md` (maintainer-local draft spec — gitignored, not in the public repo) (PR #657).
## Plugin layout
```
research/patent/
├── .claude-plugin/plugin.json
├── README.md
├── agents/cs-patent.md
├── commands/cs-patent.md
└── skills/patent/
├── SKILL.md
├── references/
│ ├── sub_use_case_routing.md ← 5-sub-use-case canon (7+ sources)
│ ├── cpc_classification_canon.md ← CPC/IPC class follow-up rationale (7+ sources)
│ └── legal_disclaimer_discipline.md ← when + why mandatory (7+ sources)
└── scripts/
├── citation_tracker.py ← multi-source three-count (Google Patents + Espacenet + USPTO + Lens.org)
├── family_resolver.py ← deduplicates same-invention across jurisdictions
└── sub_use_case_router.py ← deterministic search-strategy selection from intake answers
```
## Dependencies
- **`web_fetch`** — Required (Google Patents, Espacenet, USPTO)
- **`WebSearch`** — Required (academic prior art adjacent to patents)
- **`bash_tool` + `curl`** — Required for Lens.org if BYOK key
- **Node.js `docx` library** — Required
- **Lens.org API key** — Optional, BYOK; enables citation-graph section
## License
MIT.
© Alireza Rezvani · MIT · alirezarezvani/claude-skills
