patent-novelty-check
Assess patent novelty and non-obviousness against prior art
Install / Use
npx skills add wanshuiyin/Auto-claude-code-research-in-sleep --skill patent-novelty-checkInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Development & EngineeringSupported Platforms
Our assessment of patent-novelty-check
patent-novelty-check scores 85/100 on our quality scale, 2511th of 4,700 Development & Engineering skills we index.
Its SKILL.md is 5.6 KB long, well organised into 20 sections with 2 code examples: a solid amount of guidance for an agent.
With 19,197 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated 2 days ago, so patent-novelty-check is actively maintained.
- Our last check on 2026-11-04 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit β read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-09-27. Automated pattern scan on 2026-09-27. It catches known dangerous patterns, not every risk β read a skill before letting an agent act on it.
patent-novelty-check compared with similar skills
All 4 of these similar skills score higher than patent-novelty-check; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| patent-novelty-check (this skill)by wanshuiyin | 85 | 19.2k | 2d ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 116.8k | 8d ago | CLAUDE.md |
| Agent-Reachby Panniantong | 100 | 112.3k | 8d ago | CLAUDE.md |
| rufloby ruvnet | 100 | 81.9k | today | CLAUDE.md |
| headroomby headroomlabs-ai | 100 | 79.8k | today | CLAUDE.md |
Frequently asked questions
- How do I install patent-novelty-check?
- Run
npx skills add wanshuiyin/Auto-claude-code-research-in-sleep --skill patent-novelty-check. The install tabs above show the steps for each supported agent. - Which AI agents does patent-novelty-check work with?
- It is written for Claude Code and OpenAI Codex, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is patent-novelty-check safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is patent-novelty-check still maintained?
- The repository was last updated 2 days ago, so patent-novelty-check is actively maintained.
Skill content
View source on GitHubname: patent-novelty-check 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." argument-hint: "[invention-description-or-brief-path]" allowed-tools: Bash(*), Read, Write, Edit, Grep, Glob, WebSearch, WebFetch, mcp__codex__codex
Patent Novelty and Non-Obviousness Check
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 verificationNOVELTY_STANDARD = patentβ Always use legal patentability standard, not research contribution standard
Inputs
- Invention description from
$ARGUMENTS patent/PRIOR_ART_REPORT.md(output of/prior-art-search)patent/INVENTION_BRIEF.mdif 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:
- List the technical features that make the invention novel
- Identify which features are known from prior art vs. inventive
- 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 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:
- 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:
- Primary reference: Which reference is closest to the claimed invention?
- Secondary reference(s): Which reference(s) teach the missing element(s)?
- 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:
| Combination | Primary | Secondary | Missing Elements | Motivation to Combine | Obvious? | |-------------|---------|-----------|-----------------|----------------------|----------| | Ref1 + Ref2 | Ref1 | Ref2 | Feature D | Same field, similar problem | Yes/No |
Step 4: Cross-Model Examiner Verification
Call REVIEWER_MODEL via mcp__codex__codex with xhigh reasoning:
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
mcp__codex__codexis not available, skip cross-model examiner review and note it in the output.
Related Skills
taste-skill
116.8kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
Agent-Reach
112.3kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu β one CLI, zero API fees.
ruflo
81.9kπ The original agent harness. Deploy intelligent multi-player swarms, coordinate autonomous workflows, and build conversational AI systems. Features adaptive memory, self-learning intelligence, federation, vector RAG integration, and native Claude Code / Codex / Hermes and many more Integrated
headroom
79.8kCompress tool outputs, logs, files, and RAG chunks before they reach the LLM. 20% fewer tokens for coding agents, 60-95% fewer tokens for JSON, same answers. Library, proxy, MCP server.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit β see the Safety scan above for what the skill file itself contains.
