
patent-review
Get an external patent examiner review of a patent application. Use when user says "专利审查", "patent review", "审查意见", "examiner review", or wants critical feedback on patent claims and specification.
- Installs
- 493
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/wanshuiyin/auto-claude-code-research-in-sleep --skill patent-review- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads patent-review automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Patent Examiner Review via Codex MCP (xhigh reasoning)
Before each reviewer slot, follow Selectable Reviewers: resolve invocation →
.aris/reviewer.json→ Claude Code default (Codex MCP) withreviewer_route.pythrough the canonical helper resolver, preserving this slot's tier, fresh contexts, source/image inputs and deterministic gates. Codex examples/pins below apply only tobackend=codex; other routes use their own first-call/reply contract. Save the route and actual returned identity; unavailable selections areREVIEW_UNAVAILABLE. Classify acceptance from actual families/completion/scope. Forward invocation reviewer/model/effort overrides to reviewer-bearing children. Generation workers are unchanged.
Get a multi-round patent examiner review of the patent application based on: $ARGUMENTS
Adapted from /research-review. The reviewer persona is a patent examiner, not a paper reviewer.
Constants
REVIEWER_MODEL = gpt-6-astra— Model used via Codex MCPREVIEW_ROUNDS = 2— Number of review roundsEXAMINER_PERSONA = "patent-examiner"— GPT-6-Astra persona
Prerequisites
- Codex MCP Server configured:
claude mcp add codex -s user -- python3 "$HOME/aris_repo/mcp-servers/codex-exec/server.py" # your ARIS clone's path
Inputs
patent/CLAIMS.md— all drafted claimspatent/specification/— all specification sectionspatent/figures/numeral_index.md— reference numeral mappingpatent/PRIOR_ART_REPORT.md— known prior artpatent/INVENTION_DISCLOSURE.md— invention structure
Workflow
Step 1: Gather Patent Context
Before calling the external reviewer, compile a comprehensive briefing:
- Read all claims (independent + dependent)
- Read specification sections (at least summary and detailed description)
- Read prior art report for context
- Identify: core inventive concept, claim scope, known prior art, target jurisdiction
Step 2: Round 1 — Full Examiner Review
Send to REVIEWER_MODEL via mcp__codex__codex with xhigh reasoning:
Resolve this reviewer slot first; the following is the
backend=codexexample.
mcp__codex__codex:
model: gpt-6-astra
config: {"model_reasoning_effort": "xhigh"}
prompt: |
You are a senior patent examiner at the [USPTO/CNIPA/EPO].
Examine this patent application and issue a detailed office action.
CLAIMS:
[all claims]
SPECIFICATION SUMMARY:
[key sections: title, technical field, background, summary, abstract]
PRIOR ART KNOWN:
[prior art references]
PATENTABILITY STANDARDS TO APPLY:
[US: 35 USC 101/102/103/112 | CN: Articles 22, 26 | EP: Articles 54, 56, 83, 84]
Please issue an office action covering:
1. CLAIM CLARITY (112(b)/Art 84):
- Are all terms definite?
- Any indefinite functional language?
- Antecedent basis issues?
2. WRITTEN DESCRIPTION (112(a)/Art 83 first para):
- Does the spec support ALL claim scope?
- Any claim elements without spec support?
3. ENABLEMENT (112(a)/Art 83):
- Can a POSITA practice the invention?
- Any missing algorithm/structure for functional claims?
4. NOVELTY (102/Art 54):
- Would any known reference anticipate any claim?
- Identify the closest single reference.
5. NON-OBVIOUSNESS (103/Art 56):
- Would any combination render claims obvious?
- What is the motivation to combine?
6. CLAIM SCOPE:
- Are independent claims broad enough to be commercially valuable?
- Do dependent claims provide meaningful fallback positions?
- Any claims that are too broad (likely rejected) or too narrow (not valuable)?
7. SPECIFICATION QUALITY:
- Language issues (subjective terms, relative terms, result-to-be-achieved)
- Reference numeral consistency
- Missing embodiments
Format your response as a formal office action with:
- GROUNDS OF REJECTION for each issue (cite statute)
- SUGGESTED AMENDMENTS for each issue
- OVERALL PATENTABILITY SCORE: 1-10
Be rigorous and specific. This is a real examination.
Step 3: Implement Fixes (Round 1)
Based on the examiner's office action:
-
CRITICAL issues (102 rejection, 112 indefiniteness, missing enablement):
- Must be fixed before proceeding
- Amend claims or add specification support
-
MAJOR issues (103 obviousness, weak claim scope, missing support):
- Should be fixed or argued
- Consider claim amendments or specification additions
-
MINOR issues (language quality, numeral consistency, formatting):
- Fix if time permits
- Document in output for later cleanup
For each fix:
- Show the specific change (old claim -> new claim)
- Explain how the fix addresses the examiner's concern
Step 4: Round 2 — Follow-Up Review
Use mcp__codex__codex-reply with the threadId from Round 1:
Resolve this reviewer slot first; the following is the
backend=codexexample.
mcp__codex__codex-reply:
threadId: [from Round 1]
# inherits the thread's model/effort — do not re-send
prompt: |
Here is the revised patent application after addressing your office action.
CHANGES MADE:
[list of all changes with rationale]
REVISED CLAIMS:
[updated claims]
REVISED SPECIFICATION EXCERPTS:
[changed sections]
Please re-examine:
1. Are the previous rejections overcome?
2. Are there new issues introduced by the amendments?
3. What is the updated patentability score?
4. Any remaining grounds for rejection?
Step 5: Generate Improvement Report
Write patent/PATENT_REVIEW.md:
## Patent Review Report
### Application Summary
[Title, claims count, jurisdiction]
### Review Round 1
#### Office Action Summary
[Key findings from examiner]
#### Issues Found
| # | Type | Severity | Claim/Section | Issue | Citation | Fix Applied |
|---|------|----------|--------------|-------|----------|-------------|
| 1 | Clarity | CRITICAL | Claim 3 | Indefinite term "rapid" | 112(b) | Defined in spec |
| 2 | Novelty | MAJOR | Claim 1 | Ref X anticipates element C | 102 | Amended claim |
#### Score After Round 1: [X]/10
### Review Round 2
#### Follow-Up Assessment
[Are previous rejections overcome?]
#### Remaining Issues
[Any issues still outstanding]
#### Score After Round 2: [X]/10
### Recommendations
[Final recommendations before proceeding to jurisdiction formatting]
- [ ] All CRITICAL issues resolved
- [ ] All MAJOR issues resolved or argued
- [ ] Specification supports all claim amendments
- [ ] Ready for jurisdiction formatting
Key Rules
- The reviewer persona must be a patent examiner, not a paper reviewer or academic.
- Always use
model_reasoning_effort: "xhigh"for maximum analysis depth. - Address CRITICAL and MAJOR issues before proceeding to the next phase.
- Document all changes in the review report for traceability.
- If the patentability score is below 5/10 after Round 2, recommend significant rework before filing.
- The review is advisory -- actual prosecution may proceed differently.
FAQ
What does the patent-review skill do?
Get an external patent examiner review of a patent application. Use when user says "专利审查", "patent review", "审查意见", "examiner review", or wants critical feedback on patent claims and specification.
How do I install patent-review?
Run npx skills add https://github.com/wanshuiyin/auto-claude-code-research-in-sleep --skill patent-review in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/patent-review/ (personal) or .claude/skills/patent-review/ (project).
Which AI agents can use patent-review?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is patent-review safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains patent-review?
It is published by wanshuiyin in wanshuiyin/auto-claude-code-research-in-sleep. It has 493 recorded installs.
More from wanshuiyin/auto-claude-code-research-in-sleep
paper-figure
wanshuiyin/auto-claude-code-research-in-sleep
Generate publication-quality figures and tables from experiment results. Use when user says "画图", "作图", "generate figures", "paper figures", or needs plots for a paper.
semantic-scholar
wanshuiyin/auto-claude-code-research-in-sleep
Search published venue papers (IEEE, ACM, Springer, etc.) via Semantic Scholar API. Complements /arxiv (preprints) with citation counts, venue metadata, and TLDR. Use when user says "search semantic scholar", "find IEEE papers", "find journal papers", "venue papers", "citation search", or wants published literature beyond arXiv preprints.
research-lit
wanshuiyin/auto-claude-code-research-in-sleep
Search and analyze research papers, find related work, summarize key ideas. Use when user says "find papers", "related work", "literature review", "what does this paper say", or needs to understand academic papers.
idea-discovery
wanshuiyin/auto-claude-code-research-in-sleep
Workflow 1: Full idea discovery pipeline to go from a broad research direction to validated, pilot-tested ideas. Use when user says "找idea全流程", "idea discovery pipeline", "从零开始找方向", or wants the complete idea exploration workflow.
idea-creator
wanshuiyin/auto-claude-code-research-in-sleep
Generate and rank research ideas given a broad direction. Use when user says "找idea", "brainstorm ideas", "generate research ideas", "what can we work on", or wants to explore a research area for publishable directions.
arxiv
wanshuiyin/auto-claude-code-research-in-sleep
Search, download, and summarize academic papers from arXiv. Use when user says "search arxiv", "download paper", "fetch arxiv", "arxiv search", "get paper pdf", or wants to find and save papers from arXiv to the local paper library.
Popular code quality & workflow skills
grill-me
mattpocock/skills
A relentless interview to sharpen a plan or design.
improve-codebase-architecture
mattpocock/skills
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
handoff
mattpocock/skills
Compact the current conversation into a handoff document for another agent to pick up.
domain-modeling
mattpocock/skills
Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.
codebase-design
mattpocock/skills
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
diagnosing-bugs
mattpocock/skills
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.