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 related-work section legible to non-specialist reviewers.
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill aaai-related-work --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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: ```text 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,
- Positioning checks
- Novelty paragraph
- Positioning across AAAI's breadth
- Reviewer-pushback patterns
- Worked vignette
- Output format
What does the aaai-related-work skill do?
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.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill aaai-related-work --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/Awesome-Journal-Skills, a repository with 909 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.