Individual skill
novelty-duplication-advisory
MEMO-ONLY prior-work overlap advisory: surfaces the two ADVISORY taxonomy signals neither a tool nor a model can decide from the paper alone — ADV-TRIVIAL-COMBINATION (standard A+B+C / 缝合 stapling) and ADV-DUPLICATE-PUBLICATION (repackaged / duplicate submission). The executor RETRIEVES candidate prior work (DBLP fuzzy-title + boolean · WebSearch · WebFetch) from the paper's own title + contribution spans in the evidence ledger; TWO fresh cross-model codex reviewers (one per axis) LAY OUT the overlap side-by-side against each anchored contribution claim. It NEVER rules 'trivial' or 'duplicate' (that is a human judgment) and absence of a match is NOT evidence of originality. Emits novelty-duplication-advisory.memo.md + an info-only findings mirror; carries NO verdict weight — tools/adjudicate_findings.py lists it in ZERO_WEIGHT_SKILLS and caps it at info. Detect-only. Adapted from ARIS novelty-check, reframed from 'is MY idea novel' to 'here is the overlap a reviewer should weigh'. Triggers: "novelty advisory", "duplication check", "prior-work overlap", "is this stapling", "缝合", "查重", "重复发表", "duplicate submission".
skills/novelty-duplication-advisory/SKILL.md
Source commit 014a1e7cd63f1656603daaeeadb856aed1df6869
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 11, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 180
- Repository last updated
- Nov 6, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai-generated-content Repository topic
- ai-scientist Repository topic
- autoresearch Repository topic
- forensics Repository topic
- llm-agents Repository topic
- peer-review Repository topic
- research-integrity Repository topic
- ai-research Repository topic
- aris Repository topic
- claude Repository topic
- research Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 70,850 bytesSKILL.mdcore · 70,850 bytesSKILL.mdcore · 70,850 bytesSKILL.mdcore · 70,850 bytesSKILL.mdcore · 70,850 bytesSKILL.mdcore · 70,850 bytesSKILL.mdcore · 70,850 bytesSKILL.mdcore · 70,850 bytesSKILL.mdcore · 70,850 bytesSKILL.mdcore · 70,850 bytesSKILL.mdcore · 70,850 bytesSKILL.mdcore · 70,850 bytesSKILL.mdcore · 70,850 bytesSKILL.mdcore · 70,850 bytesSKILL.mdcore · 70,850 bytesSKILL.mdcore · 70,850 bytes
Read excerpt
# Novelty & Duplication Advisory — the overlap a reviewer should weigh
Lay out, for **$ARGUMENTS** (a paper-dir or a `claims.json` from `/evidence-ledger`), the
candidate prior-work overlap a human reviewer should weigh for two reviewer-judgment signals
— **trivial combination** ("standard A+B+C") and **duplicate publication** ("repackaged prior
work"). Retrieve candidates, map them side-by-side against the paper's ledger-anchored
contribution, and emit `novelty-duplication-advisory.memo.md`. Run AFTER `/evidence-ledger`
(so `claims.json` exists). This skill **decides nothing** — it never rules "trivial" or
"duplicate", and the deterministic adjudicator caps it at `info`.
> 🔒 **Do not wrap this skill in `/loop`, `/schedule`, or `CronCreate`.** It retrieves
> external prior work once and synthesizes it into one advisory memo. Even though it is
> **memo-only** (the adjudicator caps it at `info`, so it adds no verdict weight), the
> no-new-signal cadence rule still applies: its output changes only when the **ledger / the