Patent — Prior-Art + Landscape Intelligence
Patent — Prior-Art + Landscape Intelligence is a specialized skill for patent prior-art and landscape analysis. It commits to one of five sub-use-cases (novelty, FTO, landscape, diligence, litigation) via a forcing intake, then searches multiple patent databases and produces an editable Word document with verdict, ranked closest art, landscape, and strategy recommendations.
✨ What it does
- Forcing intake with six questions to commit to a sub-use-case before searching.
- Searches Google Patents, Espacenet, USPTO, and optionally Lens.org for citation signals.
- Extracts independent claim 1 and key dependent claims from closest art.
- Performs CPC-class-aware landscape analysis and family resolution.
- Generates an 8-section Word document with verdict, ranked art, landscape, FTO flags, strategy, and audit log.
- Enforces agent integrity rules: sequential searches, rate limiting, source discipline, and three-count tracking.
🎯 When to use it
- When the user requests a prior art search for an invention (e.g., 'prior art search for [invention]').
- When the user asks for a freedom-to-operate analysis for a product.
- When the user needs a competitive landscape of a technology area.
- When the user is evaluating a patent portfolio for acquisition.
- When the user needs to find prior art to invalidate a specific patent.
🚀 How to use
Trigger by asking for patent prior-art or landscape analysis, e.g., 'prior art search for [invention]' or 'freedom to operate analysis for [product]'. The skill will ask six intake questions one at a time; answer them precisely. It requires web_fetch and WebSearch tools, Node.js with docx package, and optionally a Lens.org API key. Example prompts:
Prior art search for a new type of battery that uses graphene electrodes.
Freedom to operate analysis for our new medical device in the US and EU.
📄 Output: An editable Word document (.docx) with verdict, ranked closest art, landscape, FTO flags, strategy recommendations, and audit log.
📦 Add this skill to Claude Code
# 1. Get the skills repo
git clone --depth 1 https://github.com/alirezarezvani/claude-skills /tmp/claude-skills
# 2. Copy this skill into your project (or ~/.claude/skills for all projects)
mkdir -p .claude/skills
cp -r /tmp/claude-skills/research/patent/skills/patent .claude/skills/patentSkill source: research/patent/skills/patent/SKILL.md
⚠️ Good to know
Produces search signal, not legal advice; always recommends consulting a patent attorney before filing or licensing decisions. Trademark, copyright, and trade-secret questions are out of scope.
❓ FAQ
What sub-use-cases does the skill support?
It supports five: novelty search, freedom-to-operate, competitive landscape, acquisition diligence, and litigation prior-art hunting.
Does the skill require a Lens.org API key?
No, Lens.org is optional; if not provided, citation graph signals are skipped and manual review is recommended.
What is the output format?
The output is a Word document (.docx) with eight sections including executive summary, closest prior art, landscape, citation signals, geographic coverage, FTO flags, strategy, and audit log.
🤖 Overview, features, install steps and FAQ were generated from the project's SKILL.md on Sep 4, 2026. Always check the original source before running commands.