Skip to content
Content
Skill

/aaai-related-work

Use when positioning an AAAI paper's novelty against archival work, contemporaneous arXiv or workshop papers, and AAAI/IJCAI/NeurIPS/ICML/ICLR neighbors across the broad AI scope, while staying inside AAAI's dual-submission and AI-as-source policy constraints and writing a

From plugin
awesome-journal-skills
1.3k200 skills

Claude Code

$ npx -y skills add brycewang-stanford/Awesome-Journal-Skills --skill aaai-related-work --agent claude-code

SKILL.md

aaai-related-work.SKILL.md
name: aaai-related-work
description: Use when positioning an AAAI paper's novelty against archival work, contemporaneous arXiv or workshop papers, and AAAI/IJCAI/NeurIPS/ICML/ICLR neighbors across the broad AI scope, while staying inside AAAI's dual-submission and AI-as-source policy constraints and writing a related-work section legible to non-specialist reviewers.

AAAI Related Work

Use this to make the novelty claim robust under AAAI's broad AI review. The related-work section must help reviewers distinguish the paper from both archival work and contemporaneous non-archival work.

Positioning checks

  • Identify the closest archival AI papers and current arXiv/workshop work.
  • Separate method novelty, task novelty, evaluation novelty, and system integration novelty.
  • Cite contemporaneous non-archival work carefully when it affects priority or reviewer

expectations.

  • Do not submit substantially similar work to multiple archival venues at the same time.
  • Explain how the paper differs from AAAI/IJCAI/NeurIPS/ICML/ICLR neighbors in assumptions,

evidence, scope, and contribution.

  • Avoid using AI systems as citable scientific sources under AAAI policy.

Novelty paragraph

Use this structure:

Closest prior work solves <problem> under <assumptions>.
It does not address <specific missing setting/mechanism/evidence>.
This paper contributes <new item> and verifies it through <evidence>.
The claim is limited to <scope>.

Positioning across AAAI's breadth

AAAI spans search, planning, knowledge representation, constraint satisfaction, multi-agent systems, learning, NLP, vision, and robotics, so the closest prior work may live in a subfield your reviewer does not. Make the contrast explicit for a non-specialist instead of assuming shared background.

| Neighbor venue | Reviewer expectation | Differentiation to spell out | | --- | --- | --- | | IJCAI | broad-AI overlap | what your result adds beyond their framing | | NeurIPS/ICML | ML method or theory depth | why AAAI breadth, not just a benchmark gain | | ICLR | representation-learning lens | non-learning mechanism or guarantee you contribute | | AAAI prior years | incremental-track suspicion | the new assumption, evidence, or scope |

Reviewer-pushback patterns

  • "This looks concurrent with arXiv paper Y." Fix: cite Y, state it is non-archival and contemporaneous,

and name the specific setting or evidence you add; do not bury or ignore it.

  • "Isn't this the same as your workshop paper?" Fix: clarify the archival delta and confirm no

substantially similar work is under review elsewhere, satisfying the dual-submission rule.

  • "Citation looks AI-generated." Fix: verify every reference against a real source; AAAI policy bars

AI systems as citable scientific sources and hallucinated citations are a credibility risk.

Worked vignette

A reasoning-over-knowledge-graphs paper sits near both a KR archival line and a recent NeurIPS embedding paper. Using the axes: against KR work the difference is *evidence* (learned vs. hand-built rules); against the NeurIPS neighbor it is *scope* (logical soundness, not just link prediction). One contemporaneous arXiv preprint is cited as non-archival with a one-line delta, and the dual-submission box is checked clean.

Output format

[Closest work] <paper/system/benchmark>
[Difference axis] problem / method / theory / data / evaluation / system / impact
[Must-cite items] <archival and contemporaneous work>
[Multiple-submission risk] none / clarify / withdraw / reroute
[Revision text] <AAAI-ready related-work paragraph>
Read more
@brycewang-stanford
Ships withawesome-journal-skills

Stanford REAP × CoPaper.AI · 由斯坦福实证方法论团队精选与维护 访问 copaper.ai 微信:CoPaper.AI 按 11 个主流学科板块覆盖 经管与商科 社会科学 人文学科 数学与物理科学 生命科学 医学与健康 工程与技术 计算机科学与 AI 体育科学 点击任一学科名可跳转到对应说明;每类下的代表子领域在正文总览中完整列出。下方封面墙按 venue 导航,完整分类见覆盖一览。 🧭 布局指南 · 📚 Skill Pack 一览 · ⚡ 如何使用 · 🧪 自动实证

1.3k200 skills
Get the whole plugin

Stars on GitHub

Momentum

stars in total
1.3k
Star history of brycewang-stanford/Awesome-Journal-Skills on GitHub, a chart by star-history.com

Other skills on awesome-journal-skills.

More skills from other plugins.

prompt-lookup

prompt-lookup

Activates when the user asks about AI prompts, needs prompt templates, wants to search for prompts, or mentions prompts.chat. Use…

@gh-f@gh-fInstall Skill
ppt-master

ppt-master

AI-driven presentation workflow for generating editable PPTX decks and slides, reconstructing page visuals, creating reusable…

@hugohe3@hugohe3Install Skill
morph-ppt

morph-ppt

Use this skill when the user wants a .pptx with smooth cross-slide animation — PowerPoint Morph transitions, Keynote-style…

officecli11d33k
@iofficeai@iofficeaiInstall Skill

Questions about aaai-related-work.

Which coding agents can use aaai-related-work?
aaai-related-work installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.