Skip to content
cccskills
FreePublished on GitHub

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.

The English summary is being prepared. Showing the original description.

Run score Not tested

See how to install

Files included (1)

  • SKILL.md3.5 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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 venueReviewer expectationDifferentiation to spell out
IJCAIbroad-AI overlapwhat your result adds beyond their framing
NeurIPS/ICMLML method or theory depthwhy AAAI breadth, not just a benchmark gain
ICLRrepresentation-learning lensnon-learning mechanism or guarantee you contribute
AAAI prior yearsincremental-track suspicionthe 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>

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Use when packaging AAAI code, data, multimedia appendices, technical appendices, reproducibility evidence, and post-acceptance artifact releases without violating double-blind or immutable-supplement rules.

The English summary is being prepared. Showing the original description.

brycewang-stanford/Awesome-Journal-Skills1.3KUpdated Sep 27, 2026

Use when drafting an AAAI author response (rebuttal) under the single short character-limited author-feedback window, the no-URL rule, no-new-results guidance, AI-generated-review handling, and the AAAI two-phase review process where Phase-2 papers receive one feedback round before SPC/AC discussion.

The English summary is being prepared. Showing the original description.

brycewang-stanford/Awesome-Journal-Skills1.3KUpdated Sep 27, 2026

Use when preparing an accepted AAAI paper for camera-ready source submission to AAAI Press, including proceedings page limits, two-column template compliance, copyright transfer, purchased extra technical pages, deanonymization, registration, oral or poster presentation, and final public artifact release.

The English summary is being prepared. Showing the original description.

brycewang-stanford/Awesome-Journal-Skills1.3KUpdated Sep 27, 2026

Use when designing or auditing AAAI experiments for the broad-AI program committee, including baselines, ablations, statistical significance, robustness, human evaluation, AI-for-Social-Impact and alignment/safety evidence, compute and cost reporting, and reproducibility-checklist alignment for Phase-1 survival.

The English summary is being prepared. Showing the original description.

brycewang-stanford/Awesome-Journal-Skills1.3KUpdated Sep 27, 2026

Use when strengthening an AAAI paper's reproducibility checklist (placed after references), experimental traceability, seed and hyperparameter reporting, compute and cost disclosure, dataset access and licensing, code/data ZIP readiness, and the claim-to-evidence map that Phase-1 reviewers use to judge rigor across AAAI's broad AI scope.

The English summary is being prepared. Showing the original description.

brycewang-stanford/Awesome-Journal-Skills1.3KUpdated Sep 27, 2026

Use when explaining or planning around AAAI's two-phase review process, Phase 1 rejection risk, Phase 2 additional reviews, AI-assisted review pilot, author feedback, SPC/AC discussion, and final decisions.

The English summary is being prepared. Showing the original description.

brycewang-stanford/Awesome-Journal-Skills1.3KUpdated Sep 27, 2026

See all skills by brycewang-stanford

Report a problem with this skill