patent-examine

Simulates iterative USPTO examination of utility patent applications with fresh examiner subagents.

391|46|Updated Aug 12, 2026
One-click install
npx skills add https://github.com/gfodor/legal-skills --skill patent-examine-gfodor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: patent-examine
Source: https://github.com/gfodor/legal-skills/tree/main/patent-examine
Command: npx skills add https://github.com/gfodor/legal-skills --skill patent-examine-gfodor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve? Drafting a utility patent application without knowing how it will survive USPTO examination leads to costly rejections and wasted filing fees. This Skill stress-tests a draft application through simulated prosecution dialogues before filing, surfacing 101, 102, 103, and 112 issues early. ## Core Features & Use Cases - Simulated Office Actions: Fresh-context subagents role-play USPTO examiners, issuing Office-Action-style rejections with verified prior-art mappings under current statutes, rules, and MPEP guidance. - Version-Locked Amendment Cycles: A deterministic Python script tracks ground-truth and proposed-candidate hashes so only examiner-cleared amendment packages are promoted to the authoritative application. - Prior-Art Validation Gate: Every 102/103 rejection is independently audited against the full reference text, with a formal accuracy-challenge protocol before any claim narrowing. - Use Case: An inventor with a pre-filing draft runs repeated examination cycles until two independent fresh examiners clear the same version, producing a prosecution record, issue ledger, and allowance-ready application. ## Quick Start Use the patent-examine skill to iteratively examine and revise my draft utility patent application until two fresh examiners independently find the same version allowable.

Frequently Asked Questions about patent-examine

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

FAQPage Schema
How do I simulate a USPTO patent examination before filing?

Provide the complete draft application, filing and priority facts, and known prior art. The skill spawns a fresh examiner subagent that searches prior art, issues a simulated Office Action, and iterates on your responses and amendments until clearance or impasse.

What patent rejection grounds does simulated examination cover?

It covers 35 U.S.C. 101 eligibility, 102 anticipation, 103 obviousness, and 112(a)/(b)/(f) issues, plus restrictions, objections, and formal requirements. Each prior-art ground requires a contextual limitation chart with verified pin cites.

Does a simulated patent examiner clearance guarantee allowance?

No. The output is an AI simulation, not legal advice, an actual USPTO examination, or assurance of allowance, validity, or enforceability. The skill explicitly prohibits representing results as a real allowance.

How does the skill prevent unapproved changes to the patent application?

It maintains separate ground-truth and proposed-candidate versions tracked by SHA-256 hashes through the cycle_state.py script. An examiner clearance applies only to the exact hashed candidate, and promotion fails on any hash mismatch.

When should I use a pre-filing audit instead of simulated examination?

Use a one-pass checklist audit for mechanical and formal pre-filing review. Use this examination loop when you need adversarial prior-art rejections, amendment iteration, and multi-examiner stress-testing of claim scope.