Skip to content
cccskills
FreePublished on GitHub

patent-novelty-check

Compare an invention with prior art to assess novelty and inventive step, meaning whether its differences would be obvious. Produce claim comparison tables, suggested claim amendments, and a report identifying potential grounds for rejection.

OriginalShow the original description

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.

Run score Not tested

See how to install

Good for

  • Assessing an invention before filing a patent application
  • Comparing claim elements with prior art
  • Considering claim amendments to address rejection risks
  • Reviewing patentability across US, Chinese, and European standards

Files included (1)

  • SKILL.md6.8 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Patent Novelty and Non-Obviousness Check

Before each reviewer slot, follow Selectable Reviewers: resolve invocation → .aris/reviewer.json → Claude Code default (Codex MCP) with reviewer_route.py through the canonical helper resolver, preserving this slot's tier, fresh contexts, source/image inputs and deterministic gates. Codex examples/pins below apply only to backend=codex; other routes use their own first-call/reply contract. Save the route and actual returned identity; unavailable selections are REVIEW_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.

Constants

  • REVIEWER_MODEL = gpt-6-astra — Model used via Codex MCP for cross-model examiner verification
  • NOVELTY_STANDARD = patent — Always use legal patentability standard, not research contribution standard

Inputs

  1. Invention description from $ARGUMENTS
  2. patent/PRIOR_ART_REPORT.md (output of /prior-art-search)
  3. patent/INVENTION_BRIEF.md if exists

Shared References

Load ../shared-references/patent-writing-principles.md for novelty/non-obviousness standards. Load ../shared-references/patent-format-us.md for 102/103 analysis framework.

Workflow

Step 1: Define Claim Elements

From the invention description, extract the key claim elements that would define the invention's scope:

  1. List the technical features that make the invention novel
  2. Identify which features are known from prior art vs. inventive
  3. Draft preliminary claim language for 2-3 independent claims (method + system)

Step 2: Anticipation Analysis (Novelty)

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 ElementRef 1Ref 2Ref 3...
Feature AYes/No + evidence
Feature BYes/No + evidence
Feature CYes/No + evidence
Feature DYes/No + evidence

Verdict per reference:

  • ANTICIPATED: One reference discloses every element → claim is not novel
  • NOT ANTICIPATED: At least one element missing from every single reference → claim is novel

Step 3: Obviousness Analysis (Inventive Step)

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:

  1. Primary reference: Which reference is closest to the claimed invention?
  2. Secondary reference(s): Which reference(s) teach the missing element(s)?
  3. Motivation to combine: Would a POSITA have reason to combine these references?
    • Explicit suggestion in the references themselves?
    • Same field, same problem?
    • Common design incentive?
    • Known technique for improving similar devices?

Format as a matrix:

CombinationPrimarySecondaryMissing ElementsMotivation to CombineObvious?
Ref1 + Ref2Ref1Ref2Feature DSame field, similar problemYes/No

Step 4: Cross-Model Examiner Verification

Call REVIEWER_MODEL via mcp__codex__codex with xhigh reasoning:

Resolve this reviewer slot first; the following is the backend=codex example.

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 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.

Step 5: Jurisdiction-Specific Assessment

For each target jurisdiction, provide a patentability assessment:

Under 35 USC 102/103 (US):

  • Novelty: PASS / FAIL (cite specific reference if fail)
  • Non-obviousness: PASS / FAIL (cite combination if fail)

Under Article 22 CN Patent Law (CN):

  • 新颖性 (Novelty): 通过 / 未通过
  • 创造性 (Inventive Step): 通过 / 未通过

Under Article 54/56 EPC (EP):

  • Novelty: PASS / FAIL
  • Inventive step: PASS / FAIL (problem-solution approach)

Step 6: Output

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]

### Cross-Model Examiner Review
[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?]

Key Rules

  • Patent novelty is absolute: any public disclosure before the priority date counts as prior art, worldwide.
  • Research novelty ("has anyone published this?") is NOT the same as patent novelty ("does any single reference teach every claim element?").
  • Obviousness requires BOTH: (1) a combination of references AND (2) a motivation to combine them.
  • Never assume the invention is patentable just because no identical patent exists.
  • The assessment is advisory only -- actual prosecution may reveal different prior art.
  • If the selected reviewer is unavailable, record REVIEW_UNAVAILABLE; continue only as an explicitly unreviewed draft, without switching providers.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

ablation-planner

FreeSummary

Plan and run ablation studies, experiments that remove or replace parts of a method to test their contribution. Organize reviewer questions, priorities, expected outcomes, and compute costs, then record results and findings.

  • Test how much each component contributes
  • Plan experiments that address reviewer questions
  • Prioritize comparisons within a compute budget
wanshuiyin/Auto-claude-code-research-in-sleep18KUpdated Oct 22, 2026

ablation-planner

FreeSummary

Plan ablation studies, experiments that remove or replace parts of a machine learning method to test their contribution. Define reviewer questions, expected outcomes, priorities, execution order, and compute estimates, then implement experiments and record findings.

  • Testing the contribution of individual method components
  • Planning additional experiments before paper submission
  • Prioritizing experiments within a GPU budget
wanshuiyin/Auto-claude-code-research-in-sleep18KUpdated Oct 22, 2026

alphaxiv

FreeSummary

Understand a single arXiv paper through an AlphaXiv summary, with full text and LaTeX source available when needed. Use it to identify key findings or ask specific questions about methods, experiments, and equations.

  • Get a quick overview of a paper from its URL
  • Check a paper's methods and experimental results
  • Ask about equations, proofs, or appendix details
wanshuiyin/Auto-claude-code-research-in-sleep18KUpdated Oct 22, 2026

analyze-results

FreeSummary

Compare machine learning experiment results from JSON or CSV files. Calculate improvements over a baseline, summarize variation across repeated runs, identify trends and unusual results, and suggest experiments to test possible explanations.

  • Compare model performance across experimental conditions
  • Check variation across runs with different random seeds
  • Identify trends as a parameter changes
wanshuiyin/Auto-claude-code-research-in-sleep18KUpdated Oct 22, 2026

arxiv

FreeSummary

Search arXiv papers by topic or paper ID, review authors and abstracts, and summarize contributions stated in the abstracts. Download selected papers or all search results as PDFs to build a local paper library.

  • Find arXiv papers on a research topic
  • Retrieve details for a known arXiv paper ID
  • Download all PDFs from a set of search results
wanshuiyin/Auto-claude-code-research-in-sleep18KUpdated Oct 22, 2026

Improve an existing LaTeX paper through two rounds of Gemini review, targeted edits, and PDF rebuilding. Check whether claims match the evidence, resolve notation and presentation issues, and retain review logs and PDF versions.

  • Review and revise a completed paper draft
  • Align claims with supporting evidence
  • Resolve notation and explanation inconsistencies
wanshuiyin/Auto-claude-code-research-in-sleep18KUpdated Oct 22, 2026

See all skills by wanshuiyin

Report a problem with this skill