novelty-check
Skill9 starsChanged 3 months agoMITView on GitHub
Prompt-only by default in the lightweight pack; Claude/Gemini reviewer transport is explicit opt-in. Verify research idea novelty against recent literature. Use when user says \"查新\", \"novelty check\", \"有没有人做过\", \"check novelty\", or wants to verify a research idea is novel before implementing.
13 other projects use a version of this, 10 of them edited.
Adopted by
Most recently taken up by
- AfonsoZhang/auto-research-systemtheir own version, first seen Nov 15, 2026
- lhg-plugs/lhg-patenttheir own version, first seen Oct 11, 2026
- yvesory/academic-research-suiteedited, first seen Oct 9, 2026
- talhaMah56/claude_skillsedited, first seen Sep 12, 2026
- wanshuiyin/Auto-claude-code-research-in-sleepedited, first seen Jul 15, 2026
- zjunlp/Mechanistedited, first seen Jul 11, 2026
Used with
Projects with it also use research-refine-pipeline, formula-derivation and 1 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
raja21068Skillresearch-refine-pipeline
Run an end-to-end workflow that chains `research-refine` and `experiment-plan`. Use when the user wants a one-shot pipeline from vague research direction to focused final proposal plus detailed experiment roadmap, or asks to "串起来", build a pipeline, do it end-to-end, or generate both the method and experiment plan together.
Also in 3 projects that use this
raja21068Skillformula-derivation
Structures and derives research formulas when the user wants to 推导公式, build a theory line, organize assumptions, turn scattered equations into a coherent derivation, or rewrite theory notes into a paper-ready formula document. Use when the derivation target is not yet fully fixed, the main object still needs to be chosen, or the user needs a coherent derivation package rather than a finished theorem proof.
Also in 3 projects that use this
YuchengZhang256Skillresearch-wiki
In an existing research wiki, ingest papers, answer wiki queries, or lint compiled Markdown pages.
Also in 3 projects that use this
Other versions13 projects use a version of this.
Word for word · 0
None found.
Edited · 10
- wanshuiyin/Auto-claude-code-research-in-sleep★ 19k22% same
- zjunlp/Mechanist★ 7561% same
- AutoResearch-Factory/Agon★ 5438% same
- Immortalqx/my_codex_skills★ 5472% same
- Chanw-research/claude-code-paper-writing★ 4276% same
- catalsqlb-cmd/Prism-H★ 1676% same
- yvesory/academic-research-suite★ 954% same
- Yusong-Enceladus/claude-skills★ 884% same
- raja21068/AutoResearch★ 276% same
- talhaMah56/claude_skills★ 045% same
Wrote their own version · 3
- sunnnybala/Rstack★ 69same name
- AfonsoZhang/auto-research-system★ 1same name
- lhg-plugs/lhg-patent★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository47 other files it gives its agents.
- autodl-hpcSkill
- experiment-bridgeSkill
- experiment-planSkill
- human-toneSkill
- idea-discoverySkill
- paper-visualizationSkill
- paper-writingSkill
- rebuttalSkill
- research-blueprintSkill
- research-pipelineSkill
- research-repo-architectSkill
- research-reviewSkill
- resubmit-pipelineSkill
- autodl-hpcSkill
- auto-paper-improvement-loopSkill
- auto-review-loopSkill
- novelty-checkSkill
- paper-figureSkill
- paper-planSkill
- paper-writeSkill
- research-refineSkill
- research-reviewSkill
- experiment-bridgeSkill
- experiment-planSkill
- auto-paper-improvement-loopSkill
- auto-review-loopSkill
- grant-proposalSkill
- idea-creatorSkill
- idea-discoverySkill
- paper-figureSkill
- paper-planSkill
- paper-posterSkill
- paper-slidesSkill
- paper-writeSkill
- paper-writingSkill
- research-refineSkill
- research-reviewSkill
- human-toneSkill
- idea-discoverySkill
- paper-visualizationSkill
- paper-writingSkill
- rebuttalSkill
- research-blueprintSkill
- research-pipelineSkill
- research-repo-architectSkill
- research-reviewSkill
- resubmit-pipelineSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
16 rules. 8 are common, 4 are distinctive, and 4 are very specific to this project.
8
Common
Most of the 12 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
Write the review prompt under review-prompts/ and ask the user to run it in a separate conversation with the relevant skills enabled.
- Distinctive: line 16
Do not call Claude/Gemini reviewer MCP bridges, APIs, or follow-up status tools by default.
- Very specific: line 18
Use pasted review text as the external verdict, then write compact summaries such as REVIEW_SUMMARY.md, NEXT_ACTIONS.md, or the …
- Distinctive: line 20
Keep heavy experiments AutoDL/HPC-gated and user-approved.
- Common: line 25
Check whether a proposed method/idea has already been done in the literature: $ARGUMENTS
- Common: line 36
Read the user's method description
- Common: line 47
Search arXiv, Google Scholar, Semantic Scholar
- Common: line 48
Use specific technical terms from the claim
- Common: line 52
Known paper databases: Check against:
- Very specific: line 59
Call REVIEWER_MODEL via mcp__gemini-review__review_start with high-rigor review:
- Very specific: line 66
After this start call, immediately save the returned jobId and poll mcp__gemini-review__review_status with a bounded waitSeconds until …
- Distinctive: line 69
All papers found in Phase B
- Distinctive: line 70
Ask: "Is this method novel?
- Common: line 103
Check both the method AND the experimental setting for novelty
- Common: line 104
If the method is not novel but the FINDING would be, say so explicitly
- Common: line 105
Always check the most recent 6 months of arXiv — the field moves fast
“Common” is measured: kept by at least 6 in 10 of the 12 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Override for Codex users who want Gemini, not a second Codex agent, to act as the reviewer. Install this package after
skills/skills-codex/*.
Customized Pack Defaults
This reviewer overlay is opt-in transport only. In the customized lightweight pack, default to prompt-only review unless the user explicitly asks to use this overlay reviewer backend:
- Write the review prompt under
review-prompts/and ask the user to run it in a separate conversation with the relevant skills enabled. - Do not call Claude/Gemini reviewer MCP bridges, APIs, or follow-up status tools by default.
- Use pasted review text as the external verdict, then write compact summaries
such as
REVIEW_SUMMARY.md,NEXT_ACTIONS.md, or the skill-specific log. - Keep heavy experiments AutoDL/HPC-gated and user-approved; local work stays at edits, tests, lint, dry-runs, and tiny smoke checks.
Novelty Check Skill
Check whether a proposed method/idea has already been done in the literature: $ARGUMENTS
Constants
- REVIEWER_MODEL =
gemini-review— Gemini reviewer invoked through the localgemini-reviewMCP bridge. SetGEMINI_REVIEW_MODELif you need a specific Gemini model override.
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 mcp__gemini-review__review_start with high-rigor review:
mcp__gemini-review__review_start:
prompt: |
[Full novelty briefing + prior work list + specific novelty questions]After this start call, immediately save the returned jobId and poll mcp__gemini-review__review_status with a bounded waitSeconds until done=true. Treat the completed status payload's response as the reviewer output, and save the completed threadId for any follow-up round.
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
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

