Assess patent novelty and non-obviousness against prior art. Use when user says "专利查新", "patent novelty", "可专利性评估", "patentability check", or wants to evaluate if an invention is patentable.
85%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Before each reviewer slot, follow Selectable Reviewers: resolve invocation →
.aris/reviewer.json→ Codex default (fresh native reviewer) 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.
Assess patentability of: $ARGUMENTS
Adapted from /novelty-check for patent legal standards. Research novelty is NOT the same as patent novelty.
REVIEWER_MODEL = gpt-6-astra — Fresh Codex examiner; same-family provisional in the base mirrorNOVELTY_STANDARD = patent — Always use legal patentability standard, not research contribution standard$ARGUMENTSpatent/PRIOR_ART_REPORT.md (output of /prior-art-search)patent/INVENTION_BRIEF.md if existsLoad ../shared-references/patent-writing-principles.md for novelty/non-obviousness standards.
Load ../shared-references/patent-format-us.md for 102/103 analysis framework.
From the invention description, extract the key claim elements that would define the invention's scope:
For each preliminary claim, test against EACH prior art reference in PRIOR_ART_REPORT.md:
Single-reference test: Does any single reference disclose ALL claim elements?
| Claim Element | Ref 1 | Ref 2 | Ref 3 | ... |
|---|---|---|---|---|
| Feature A | Yes/No + evidence | |||
| Feature B | Yes/No + evidence | |||
| Feature C | Yes/No + evidence | |||
| Feature D | Yes/No + evidence |
Verdict per reference:
If the invention is novel (passes Step 2), test for obviousness:
Two/three-reference combination test: Can 2-3 references be combined to render the claim obvious?
For each combination of the top references:
Format as a matrix:
| Combination | Primary | Secondary | Missing Elements | Motivation to Combine | Obvious? |
|---|---|---|---|---|---|
| Ref1 + Ref2 | Ref1 | Ref2 | Feature D | Same field, similar problem | Yes/No |
Call REVIEWER_MODEL via a dedicated Codex reviewer agent at xhigh reasoning:
Resolve this reviewer slot first; the following is the
backend=codexexample.
spawn_agent:
model: gpt-6-astra
reasoning_effort: xhigh
message: |
You are a senior patent examiner at the [USPTO/CNIPA/EPO].
Examine the following invention for patentability.
INVENTION: [invention description + preliminary claims]
PRIOR ART: [prior art references with key teachings]
Please analyze:
1. Anticipation (novelty): Does any single reference anticipate any claim?
2. Obviousness: Can any combination of references render claims obvious?
3. Claim scope: Are the claims broad enough to be valuable?
4. Recommended amendments if any claim is rejected.
Be rigorous and cite specific references.For each target jurisdiction, provide a patentability assessment:
Under 35 USC 102/103 (US):
Under Article 22 CN Patent Law (CN):
Under Article 54/56 EPC (EP):
Write patent/NOVELTY_ASSESSMENT.md:
## Patentability Assessment
### Invention Summary
[description]
### Overall Assessment
[PATENTABLE / PATENTABLE WITH AMENDMENTS / NOT PATENTABLE]
### Anticipation Analysis
[claim-by-claim matrix against each reference]
### Obviousness Analysis
[combination analysis with motivation to combine]
### Review-Independence Metadata
[summary of GPT-6-Astra examiner feedback]
### Recommended Claim Amendments
[If claims need modification to overcome prior art, suggest specific amendments]
### Risk Factors
[What could cause rejection during actual prosecution?]ca70fe2
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.