patent-review

Generate a multi-round examiner-style office action for patent claims and specification.

Updated May 20, 2026
One-click install
npx skills add https://github.com/lightrain-a/medtrace-aris --skill patent-review-lightrain-a
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: patent-review
Source: https://github.com/lightrain-a/medtrace-aris/tree/main/.vendor/aris/skills/patent-review
Command: npx skills add https://github.com/lightrain-a/medtrace-aris --skill patent-review-lightrain-a

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you find weaknesses in your patent application by simulating a patent examiner’s office action, so you can improve claims and specification before filing.

Core Features & Use Cases

  • Examiner-style office action: Evaluates clarity, written description, enablement, novelty, non-obviousness, claim scope, and specification quality.
  • Iterative improvements: Runs a multi-round review where critical and major issues are addressed first.
  • Actionable change log: Produces a traceable improvement report documenting fixes and updated scores.
  • Use Case: You suspect your claims may be indefinite, insufficiently supported, or vulnerable to prior art and obviousness arguments, and you want targeted, jurisdiction-aware critique.

Quick Start

Use the patent-review skill to generate a multi-round examiner-style office action for your drafted claims and specification.

Frequently Asked Questions about patent-review

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

FAQPage Schema
How do I get a patent examiner-style review before filing my application?

To get a patent examiner-style review, you can run this skill to simulate an office action by submitting your drafted claims, full specification, and prior art context for a structured critique on novelty and obviousness.

What does an examiner review check for in a patent application?

An examiner review checks your patent application for vulnerabilities including claim clarity, written description, enablement, novelty, non-obviousness, claim scope, and overall specification quality to identify weaknesses before filing.

How do I prepare my claims and specification for an office action simulation?

To prepare for an office action simulation, draft your claims and full specification, gather relevant prior art context, and ensure you have the files ready for the system to read and analyze.

Can I get a jurisdiction-aware obviousness assessment for my patent claims?

Yes, you can get a jurisdiction-aware obviousness assessment by providing your jurisdiction context, allowing the review to apply jurisdiction-relevant novelty and non-obviousness evaluations to your drafted claims.

Does the patent review process support iterative improvements to claims?

Yes, the patent review process supports iterative improvements by running a multi-round review where critical and major issues are addressed first, producing a traceable change log documenting fixes and updated scores.

What limitations exist when analyzing prior art for an office action?

A limitation is that the analysis requires reading claims and specification files to send a structured office-action prompt, meaning incomplete prior art context or missing file inputs may reduce the accuracy of the vulnerability assessment.