patent-review

Generate multi-round patent examiner office actions assessing patentability risks.

2|1|Updated Apr 19, 2026
One-click install
npx skills add https://github.com/raja21068/AutoResearch --skill patent-review-raja21068
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: patent-review
Source: https://github.com/raja21068/AutoResearch/tree/main/skills/aris/patent-review
Command: npx skills add https://github.com/raja21068/AutoResearch --skill patent-review-raja21068

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps inventors and patent teams turn a draft patent into an examiner-style assessment so you can identify likely clarity, support, novelty, and obviousness weaknesses before filing.

Core Features & Use Cases

  • Multi-round patent examiner review: Performs a structured office-action style critique across claim clarity, written description, enablement, novelty, non-obviousness, and specification quality.
  • Jurisdiction-aware patentability standards: Applies USPTO/CNIPA/EPO standards and tailors the evaluation to the likely jurisdiction context.
  • Actionable amendment guidance and traceability: Produces suggested claim/spec changes and a review report documenting issues, fixes, and updated scores.
  • Use case: When you receive or anticipate “审查意见/office action” risks, run this review to harden your claims and specification by addressing critical rejections first.

Quick Start

Use the patent-review skill to send your patent package (patent/CLAIMS.md, patent/specification/, patent/figures/numeral_index.md, patent/PRIOR_ART_REPORT.md, and patent/INVENTION_DISCLOSURE.md) for a two-round examiner-style office action and improvement report.

Frequently Asked Questions about patent-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I get an examiner-style patent office action before filing?▼

To get an examiner-style patent office action before filing, submit your drafted patent claims and full specification context. The review performs a multi-round critique assessing clarity, written description, enablement, novelty, and non-obviousness.

Can I apply USPTO, CNIPA, and EPO patentability standards to my drafted claims?▼

Yes, you can apply USPTO, CNIPA, and EPO patentability standards to drafted claims. The review tailors jurisdiction-aware evaluations across clarity, support, novelty, and obviousness to match your specific jurisdiction context.

How do I review patent claims for obviousness and enablement risks?▼

You review patent claims for obviousness and enablement risks by sending your patent package, including claims and specification, for a structured office-action style critique. This generates actionable amendment guidance and a traceability report.

What prior art and specification inputs do I need for a patent claim review?▼

For a patent claim review, you need inputs including CLAIMS.md, specification files, figure numeral index, prior art report, and invention disclosure. These markdown inputs provide the execution-grounded context required for reviewer-grade critique.

Does patent office action simulation work without Codex MCP integration?▼

No, patent office action simulation requires Codex MCP integration to function. It also requires access to specific patent markdown inputs and uses xhigh reasoning to generate reviewer-grade critique and amendment recommendations.

What is the best way to harden patent claims after receiving an office action?▼

The best way to harden patent claims after receiving an office action is running a structured examiner-style review. It prioritizes critical rejections and produces suggested claim and specification changes with updated scores.