Install any skill in seconds. Free to start, no credit card required.
Get Started Free →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.
.claude/skills/wanshuiyin-patent-novelty-check/SKILL.md| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-07 | ✗→✓ | ▲ Improved | 84% | 0% |
| case-08 | ✗→✓ | ▲ Improved | 27% | 0% |
| case-09 | ✗→✓ | ▲ Improved | 103% | 0% |
| case-11 | ✗→✓ | ▲ Improved | 1% | 0% |
| case-12 | ✗→✓ | ▲ Improved | 631% | 0% |
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:
textspawn_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:
markdown## 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?]
| Case | Status | Duration (ms) | Turns | Tokens | Tool calls | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Without | With | Δ | Without | With | Δ | Without | With | Δ | Without | With | Δ | ||
case-01 | fail→fail | 69,924 | 14,513 | -79% | 1 | 1 | 0% | 10,335 | 1,561 | -85% | 0 | 0 | — |
case-02 | fail→fail | 51,614 | 14,271 | -72% | 1 | 1 | 0% | 8,307 | 1,632 | -80% | 0 | 0 | — |
case-03 | fail→fail | 74,078 | 14,248 | -81% | 1 | 1 | 0% | 8,298 | 1,581 | -81% | 0 | 0 | — |
case-04 | fail→fail | 13,954 | 18,995 | +36% | 1 | 1 | 0% | 1,478 | 1,996 | +35% | 0 | 0 | — |
case-05 | pass→pass | 12,551 | 14,163 | +13% | 1 | 1 | 0% | 1,412 | 3,094 | +119% | 0 | 0 | — |
case-06 | pass→pass | 21,559 | 20,987 | -3% | 1 | 1 | 0% | 2,342 | 3,735 | +59% | 0 | 0 | — |
case-07 | fail→pass | 20,336 | 23,693 | +17% | 1 | 1 | 0% | 2,295 | 4,217 | +84% | 0 | 0 | — |
case-08 | fail→pass | 22,956 | 20,539 | -11% | 1 | 1 | 0% | 3,063 | 3,905 | +27% | 0 | 0 | — |
case-09 | fail→pass | 28,389 | 40,150 | +41% | 1 | 1 | 0% | 3,719 | 7,543 | +103% | 0 | 0 | — |
case-10 | fail→fail | 14,625 | 15,150 | +4% | 1 | 1 | 0% | 300 | 1,571 | +424% | 0 | 0 | — |
case-11 | fail→pass | 18,443 | 9,013 | -51% | 1 | 1 | 0% | 1,902 | 1,925 | +1% | 0 | 0 | — |
case-12 | fail→pass | 55,064 | 53,654 | -3% | 1 | 1 | 0% | 1,306 | 9,542 | +631% | 0 | 0 | — |
case-13 | pass→pass | 23,002 | 17,903 | -22% | 1 | 1 | 0% | 2,948 | 3,541 | +20% | 0 | 0 | — |
case-14 | pass→fail | 16,434 | 14,315 | -13% | 1 | 1 | 0% | 1,803 | 2,554 | +42% | 0 | 0 | — |
case-15 | fail→pass | 25,478 | 11,793 | -54% | 1 | 1 | 0% | 2,971 | 2,637 | -11% | 0 | 0 | — |
case-16 | pass→pass | 20,911 | 44,692 | +114% | 1 | 1 | 0% | 2,627 | 6,582 | +151% | 0 | 0 | — |
case-17 | pass→pass | 16,370 | 15,215 | -7% | 1 | 1 | 0% | 1,620 | 3,101 | +91% | 0 | 0 | — |
case-18 | pass→pass | 15,469 | 11,898 | -23% | 1 | 1 | 0% | 1,520 | 2,467 | +62% | 0 | 0 | — |
case-19 | pass→pass | 30,982 | 34,516 | +11% | 1 | 1 | 0% | 5,034 | 7,106 | +41% | 0 | 0 | — |
case-20 | pass→pass | 16,873 | 20,896 | +24% | 1 | 1 | 0% | 2,146 | 4,117 | +92% | 0 | 0 | — |
case-21 | pass→pass | 19,812 | 23,094 | +17% | 1 | 1 | 0% | 3,116 | 5,361 | +72% | 0 | 0 | — |
case-22 | pass→pass | 20,807 | 26,753 | +29% | 1 | 1 | 0% | 2,281 | 4,767 | +109% | 0 | 0 | — |
case-23 | fail→fail | 8,210 | 6,749 | -18% | 1 | 1 | 0% | 519 | 1,650 | +218% | 0 | 0 | — |
DecimalAI ran this skill against gemini-3.6-flash twice over the same eval suite — once with the skill loaded and once without — and compared the two runs case by case. 23 cases were attempted, and 17 counted toward the lift figure. The other 6 produced results that are not comparable between the two arms, so they are excluded from the headline rather than averaged into it. The headline lift of +22 percentage points is the difference between those two pass rates over the 17 comparable cases. 1 case got worse with the skill loaded, and it is included in that figure.
Without the skill loaded, the model failed this case. With it loaded, the same prompt on the same model passed. This is one improved case from the latest verified run; every case, including any that regressed, is in the table above.
| Model | Method | Date | Lift |
|---|---|---|---|
| gemini-3.6-flash | verified | 8/11/2026 | -5% |
Other measured skills in the registry, with their headline benchmark lift.