Agent skill

novelty-check

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.

brycew6m4,252★ · +31/wk · 3 repos on radarProfile →
claude-coderead-onlyNOASSERTION
Install
npx skills add brycewang-stanford/Auto-Empirical-Research-Skills --skill novelty-check --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 8 KB
Bundled scripts: none
Allowed tools: WebSearchWebFetchGrepReadGlobmcp__codex__codex
Path: skills/67-econfin-workflow-toolkit/novelty-check/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 3,244
Language: Stata
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Novelty Check Skill Check whether a proposed method/idea has already been done in the literature: **$ARGUMENTS** ## Constants - **External cross-model verifier (Codex / `mcp__codex__codex`) is UNAVAILABLE** in this environment — persistent `401 Unauthorized` (no OpenAI bearer). Do **not** block on it and do **not** silently skip verification when it fails. - **EVALUATOR = Claude itself**, acting as an impartial, adversarial referee (Phase C). If Codex ever comes back, it may serve as an optional *second* opinion only. - Scoring is anchored to the **calibration rubric in Phase D.0** to prevent the score inflation observed when the Codex backend was down (2026-05: several econfin ideas were rated "9" but on rigorous re-check were 5–7.5). ## Instructions Given a method description, systematically verify its novelty: ### Phase A: Extract Key Claims 1. Read the user's method description 2. 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 with ALL relevant sources — **adapt t

What's inside
Steps it walks through
  1. Constants
  2. Instructions
  3. Phase A: Extract Key Claims
  4. Phase B: Multi-Source Literature Search
  5. Phase C: Adversarial Self-Verification (impartial referee)
  6. Phase D.0: Score Calibration (anchor EVERY score here — prevents inflation)
  7. Phase D: Novelty Report
  8. Important Rules
More from Auto-Empirical-Research-Skills
All skills →
About this skill
What does the novelty-check skill do?

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.

How do I install it?

Run `npx skills add brycewang-stanford/Auto-Empirical-Research-Skills --skill novelty-check --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From brycewang-stanford/Auto-Empirical-Research-Skills, a repository with 3,244 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going