Check whether a proposed method/idea has already been done in the literature: $ARGUMENTS
Constants
REVIEWER_MODEL = gpt-5.4 — Model used via a secondary Codex agent. Must be an OpenAI model (e.g., gpt-5.4, o3, gpt-4o)
Instructions
Given a method description, systematically verify its novelty:
Phase A: Extract Key Claims
Read the user's method description
Identify 3-5 core technical claims that would need to be novel:
What is the method?
What problem does it solve?
What is the mechanism?
What makes it different from obvious baselines?
Phase B: Multi-Source Literature Search
For EACH core claim, search using ALL available sources:
Web Search (via WebSearch):
Search arXiv, Google Scholar, Semantic Scholar
Use specific technical terms from the claim
Try at least 3 different query formulations per claim
Include year filters for 2024-2026
Known paper databases: Check against:
ICLR 2025/2026, NeurIPS 2025, ICML 2025/2026
Recent arXiv preprints (2025-2026)
Read abstracts: For each potentially overlapping paper, WebFetch its abstract and related work section
Phase C: Cross-Model Verification
Call REVIEWER_MODEL via spawn_agent (spawn_agent) with xhigh reasoning:
reasoning_effort: xhigh
Prompt should include:
The proposed method description
All papers found in Phase B
Ask: "Is this method novel? What is the closest prior work? What is the delta?"
Phase D: Novelty Report
Output a structured report:
## Novelty Check Report
### Proposed Method
[1-2 sentence description]
### Core Claims
1. [Claim 1] — Novelty: HIGH/MEDIUM/LOW — Closest: [paper]
2. [Claim 2] — Novelty: HIGH/MEDIUM/LOW — Closest: [paper]
...
### Closest Prior Work
| Paper | Year | Venue | Overlap | Key Difference |
|-------|------|-------|---------|----------------|
### Overall Novelty Assessment
- Score: X/10
- Recommendation: PROCEED / PROCEED WITH CAUTION / ABANDON
- Key differentiator: [what makes this unique, if anything]
- Risk: [what a reviewer would cite as prior work]
### Suggested Positioning
[How to frame the contribution to maximize novelty perception]
Important Rules
Be BRUTALLY honest — false novelty claims waste months of research time
"Applying X to Y" is NOT novel unless the application reveals surprising insights
Check both the method AND the experimental setting for novelty
If the method is not novel but the FINDING would be, say so explicitly
Always check the most recent 6 months of arXiv — the field moves fast
1---2name: novelty-check3description: novelty check workflow.4---56# Novelty Check Skill78Check whether a proposed method/idea has already been done in the literature: **$ARGUMENTS**910## Constants1112- REVIEWER_MODEL = `gpt-5.4` — Model used via a secondary Codex agent. Must be an OpenAI model (e.g., `gpt-5.4`, `o3`, `gpt-4o`)1314## Instructions1516Given a method description, systematically verify its novelty:1718### Phase A: Extract Key Claims191. Read the user's method description202. Identify 3-5 core technical claims that would need to be novel:21 - What is the method?22 - What problem does it solve?23 - What is the mechanism?24 - What makes it different from obvious baselines?2526### Phase B: Multi-Source Literature Search27For EACH core claim, search using ALL available sources:28291. **Web Search** (via `WebSearch`):30 - Search arXiv, Google Scholar, Semantic Scholar31 - Use specific technical terms from the claim32 - Try at least 3 different query formulations per claim33 - Include year filters for 2024-202634352. **Known paper databases**: Check against:36 - ICLR 2025/2026, NeurIPS 2025, ICML 2025/202637 - Recent arXiv preprints (2025-2026)38393. **Read abstracts**: For each potentially overlapping paper, WebFetch its abstract and related work section4041### Phase C: Cross-Model Verification42Call REVIEWER_MODEL via `spawn_agent` (`spawn_agent`) with xhigh reasoning:43```44reasoning_effort: xhigh45```46Prompt should include:47- The proposed method description48- All papers found in Phase B49- Ask: "Is this method novel? What is the closest prior work? What is the delta?"5051### Phase D: Novelty Report52Output a structured report:5354```markdown55## Novelty Check Report5657### Proposed Method58[1-2 sentence description]5960### Core Claims611. [Claim 1] — Novelty: HIGH/MEDIUM/LOW — Closest: [paper]622. [Claim 2] — Novelty: HIGH/MEDIUM/LOW — Closest: [paper]63...6465### Closest Prior Work66| Paper | Year | Venue | Overlap | Key Difference |67|-------|------|-------|---------|----------------|6869### Overall Novelty Assessment70- Score: X/1071- Recommendation: PROCEED / PROCEED WITH CAUTION / ABANDON72- Key differentiator: [what makes this unique, if anything]73- Risk: [what a reviewer would cite as prior work]7475### Suggested Positioning76[How to frame the contribution to maximize novelty perception]77```7879### Important Rules80- Be BRUTALLY honest — false novelty claims waste months of research time81- "Applying X to Y" is NOT novel unless the application reveals surprising insights82- Check both the method AND the experimental setting for novelty83- If the method is not novel but the FINDING would be, say so explicitly84- Always check the most recent 6 months of arXiv — the field moves fast85
Run npx skillmds@latest add kyrie66nb/novelty-check in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.
novelty check workflow. It is listed under Productivity on SkillMD.
This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.
This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.
Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.
kyrie66nb (@kyrie66nb) published this skill. Their other Agent Skills are listed on their SkillMD profile.