SkillAgentSearch skills...

aaai-writing-style

Use when revising an AAAI manuscript for broad-AI-audience fit, a first-page contribution statement legible to non-specialist Phase-1 reviewers, two-column readability, concise novelty claims, reproducibility-checklist alignment, hedged limitations and ethics, and policy-aware framing of AI-system a…

Install / Use

npx skills add brycewang-stanford/Awesome-Journal-Skills --skill aaai-writing-style

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

83/100

Supported Platforms

Universal

Our assessment of aaai-writing-style

aaai-writing-style scores 83/100 on our quality scale, 893rd of 1,179 Content & Media skills we index.

Its SKILL.md is 3.3 KB long, split into 7 sections with 1 code example: a solid amount of guidance for an agent.

With 1,158 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
15/20
Description
15/15
Adoption
13/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated 18 days ago, so aaai-writing-style is actively maintained.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

aaai-writing-style compared with similar skills

All 4 of these similar skills score higher than aaai-writing-style; compare them before choosing.

SkillScoreStarsUpdatedFormat
aaai-writing-style (this skill)by brycewang-stanford831.2k18d agoSKILL.md
siyuanby siyuan-note10046.6ktodayMCP Server
algorithmic-artby anthropics100177.9k10d agoSKILL.md
pptxby anthropics100177.9k10d agoSKILL.md
designby nextlevelbuilder100130.2k12d agoSKILL.md

Frequently asked questions

How do I install aaai-writing-style?
Run npx skills add brycewang-stanford/Awesome-Journal-Skills --skill aaai-writing-style. The install tabs above show the steps for each supported agent.
Which AI agents does aaai-writing-style work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is aaai-writing-style safe to use?
It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is aaai-writing-style still maintained?
The repository was last updated 18 days ago, so aaai-writing-style is actively maintained.

name: aaai-writing-style description: Use when revising an AAAI manuscript for broad-AI-audience fit, a first-page contribution statement legible to non-specialist Phase-1 reviewers, two-column readability, concise novelty claims, reproducibility-checklist alignment, hedged limitations and ethics, and policy-aware framing of AI-system and capability claims.

AAAI Writing Style

Use this to make a technically sound draft readable to a broad AI program committee. AAAI rewards clear AI contribution, not only subfield-specific benchmark wins.

AAAI framing

  • State the AI problem, the new capability or insight, and the evidence in the first page.
  • Make clear whether the contribution is method, theory, system, benchmark, dataset, evaluation, human-AI interaction, social impact, or alignment.
  • Explain why the result matters outside a single dataset or implementation.
  • Keep claims aligned with the reproducibility checklist and supplementary evidence.
  • Discuss limitations and ethical considerations when the method affects people, safety, privacy, fairness, security, or social impact.

Two-column readability

  • Use figures and tables as decision aids, not decoration.
  • Keep notation lightweight and define it near first use.
  • Use compact related-work contrasts instead of long literature catalogues.
  • Make the Phase 1 summary easy: problem, method, evidence, limitation, checklist compliance.
  • Avoid unsupported "general intelligence", "human-level", or "safe" claims.

Reading the paper as a Phase-1 reviewer

A non-specialist on AAAI's broad committee gives the first page a few minutes and decides whether the paper is worth deeper reading. Write so that a planning or KR reviewer can summarize your learning contribution, and vice versa. Audit the opening against what that reader needs to extract fast.

| First-page question | Reviewer extracts | Failure symptom | | --- | --- | --- | | What is the problem | one AI task statement | jargon with no anchor | | What is new | the single contribution | a list, no headline | | Why believe it | evidence in one line | "see Section 6" only | | What are the limits | scope and caveat | silence or overclaim |

Phrasing fixes that survive AAAI review

  • Replace "we achieve state of the art" with the specific delta and the setting it holds in.
  • Replace bare "safe" or "human-level" with a measured, scoped statement the evidence supports.
  • Replace a long related-work catalogue with two or three sharp contrasts a non-specialist can follow.
  • Tie every strong claim back to a checklist answer so rigor and prose agree.

Worked vignette

A multi-agent paper opens with three paragraphs of game-theory notation before naming its contribution. A vision reviewer cannot find the AI claim and is likely to stop. The fix rewrites sentence one as the problem, sentence two as the new coordination mechanism, sentence three as the one-line evidence, and a final clause scoping the result to the studied setting, all on page one.

Output format

[AAAI fit sentence] <one sentence>
[Contribution type] method / theory / system / benchmark / dataset / evaluation / social impact
[First-page fixes] <problem, method, evidence, limitation>
[Checklist alignment] pass / needs revision
[Overclaim risks] <claims to narrow or evidence to add>

Related Skills

View on GitHub
GitHub Stars1.2k
CategoryContent
Updated18d ago
Forks153

Languages

Stata

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions