ablation-planner
Use when main results pass result-to-claim (claim_supported=yes or partial) and ablation studies are needed for paper submission.
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.
$ npx -y skills add wanshuiyin/Auto-claude-code-research-in-sleep --skill patent-novelty-check --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/patent-novelty-checkContext preview
The summary Claude sees to decide when to auto-load this skill.
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.
name: 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
Assess patentability of: **$ARGUMENTS**
Adapted from `/novelty-check` for patent legal standards. Research novelty is NOT the same as patent novelty.
1. Invention description from `$ARGUMENTS` 2. `patent/PRIOR_ART_REPORT.md` (output of `/prior-art-search`) 3. `patent/INVENTION_BRIEF.md` if exists
Load `../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: 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)
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: 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?
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 `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.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] ### 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?]
· · · · · · -orange?style=flat) · · 💬 Join Community · 💡 Use ARIS as a skill-based workflow in Claude Code / Codex CLI / Cursor / Trae / Antigravity / GitHub Copilot CLI / OpenClaw / DeepSeek Harness, or get the full experience with the standalone ARIS-Code
Use when main results pass result-to-claim (claim_supported=yes or partial) and ablation studies are needed for paper submission.
Quick single-paper lookup via AlphaXiv LLM-optimized summaries with tiered source fallback. Use when user says "explain this paper", "summarize paper", pastes…
Analyze ML experiment results, compute statistics, generate comparison tables and insights. Use when user says "analyze results", "compare", or needs to…
Search, download, and summarize academic papers from arXiv. Use when user says "search arxiv", "download paper", "fetch arxiv", "arxiv search", "get paper…
Autonomously improve a generated paper via GPT-6-Astra xhigh review → implement fixes → recompile, for 2 rounds. Use when user says \"改论文\", \"improve paper\",…
Autonomous research review loop using any OpenAI-compatible LLM API. Configure via llm-chat MCP server or environment variables. Trigger with "auto review loop…