patent-examine
Iteratively examine and revise a draft U.S. utility patent application through prosecution-style dialogues with fresh subagents role-playing USPTO examiners. Each examiner performs a current-law and prior-art review, issues Office-Action-style rejections or requirements under 35 U.S.C. 101, 102, 103, 112 and related grounds, then reconsiders exact applicant arguments and proposed amendments until all issues are resolved. Apply an examiner-approved amendment package to the ground-truth application only after that examiner indicates allowability, and repeat until two independent fresh examiners clear the same final version. Use for simulated examination, mock prosecution, rejection-response iteration, or examiner stress-testing of a patent draft; not for a one-pass pre-filing checklist audit.
Install
With your agent
Install OMGSkills skill "gfodor/legal-skills:patent-examine" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/gfodor/legal-skills /tmp/legal-skills && ln -s /tmp/legal-skills/patent-examine ~/.claude/skills/patent-examineFrom README
Recurrent simulated patent examination Run a version-controlled applicant/examiner dialogue. Keep the main agent in the applicant/drafter role and one persistent subagent in the examiner role per cycle. Do not describe the result as an actual USPTO allowance or a guarantee of validity. Read before acting Read all of these files: references/examiner-protocol.md for the examiner's role and decision contract. references/office-action-format.md for rejection sufficiency and response rules. references/official-sources.md for the current-law and prior-art source hierarchy. Copy and complete assets/examination-intake.yaml. Use assets/examiner-handoff.md, assets/prior-art-validation.md, and assets/applicant-response.md in every cycle. If the sibling ../patent-audit skill is installed, read its SKILL.md and use its deterministic pre-pass to produce parsed.json, mechanical findings, claim dependencies, and date calculations.