← ClaudeAtlas

study-accepted-paperslisted

Mine a target venue's ACCEPTED-paper corpus to learn what makes papers STRONG there, then turn that into concrete strengthening levers for your own draft — the move from a plain "Accept" toward "Strong Accept". Fetch 8-12 real recently-accepted papers at the venue (ACM DL / IEEE Xplore / venue program pages / arXiv), prioritizing the same paper-type and topic as yours (measurement/benchmark/SoK/security-critique), and for each extract WHAT MADE IT STRONG (adaptive evaluation, explicit threat model, reusable released artifact, real-world grounding, a memorable framing/coined handle, a released dataset, honest limitations). Cross-read the venue CFP + PC-chair research tastes + any best-paper criteria. Then diff your draft against those patterns and emit ranked levers split into CHEAP (framing/prose/citation, safe before a deadline) vs EXPENSIVE (new experiments/data). Use when a paper is drafted and you want venue-specific polish grounded in what actually lands there — NOT generic writing advice. Distinct from
zernie/paperlint · ★ 7 · Data & Documents · score 74
Install: claude install-skill zernie/paperlint
<!-- vigiles:sha256:177ca8805990361e compiled from skills/study-accepted-papers/SKILL.md.spec.ts --> # study-accepted-papers — learn the venue's bar from its own accepted corpus, then lever your draft up ## Run me 🔴 FIRST, before any other step: ``` node .claude/skills/paper-pipeline/scripts/announce.mjs study-accepted-papers <paper-dir> ``` An advisory pass cannot be observed failing — silence is both its error state and its normal state — so starting is an event, and events get written down. Reviewers don't score in a vacuum — they score against the papers that got in last cycle. This skill makes that reference standard explicit: pull the venue's **actually-accepted** papers of your type, extract the concrete properties that separated the strong ones from the weak-accepts, and diff your draft against them to produce **specific, sourced levers** — not "add more rigor" but "AISec strong accepts in this lane all carry an adaptive-attacker evaluation; yours has static mutation only — here's the cheap version you can add and the expensive version you can't." It answers a different question than the neighboring skills: - `find-venue` → *where* should this go? (ranks venues) - `research-ideate` → is the *idea* worth doing? (go/no-go on the contribution) - `pc-panel-review` / `paper-adversarial-review` → what's wrong with *my draft*? (red-team your text) - **`study-accepted-papers` → what does it take to be *strong* at THIS venue, judged by its own accepted papers?** Groun