Awesome Journal Skills is a collection of agent skill packs tailored to hundreds of academic journals across fields including economics, social science, medicine, science, and engineering. Researchers use the packs for tasks such as choosing topics, designing empirical strategies, preparing tables and figures, submitting papers, and responding to reviewers. The catalogue entries are the project's journal-specific skills and related plugins.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill aaai-writing-stylegit clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-SkillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/brycewang-stanford/awesome-journal-skills/aaai-writing-style)<a href="https://agentmods.dev/skills/brycewang-stanford/awesome-journal-skills/aaai-writing-style"><img src="https://agentmods.dev/badge/skills/brycewang-stanford/awesome-journal-skills/aaai-writing-style/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/brycewang-stanford/awesome-journal-skills/aaai-writing-style"><img src="https://agentmods.dev/badge/skills/brycewang-stanford/awesome-journal-skills/aaai-writing-style.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00068 | $0.00700 |
| Opus 5.5 | $0.00027 | $0.00280 |
| Sonnet 5.5 | $0.00014 | $0.00140 |
| Haiku 4.5 | $0.00007 | $0.00070 |
Grade A, and why
aaai-writing-style scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 66 lines · 68 tokens per session scan A 4b6231e905c9
aaai-writing-style is a skill published in the GitHub repository brycewang-stanford/Awesome-Journal-Skills (1,320 stars, last pushed 1mo ago), licensed MIT. It adds 68 tokens to every session and 700 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
alterlab-imaging-data-commons
Query and download public cancer imaging data from the NCI Imaging Data Commons (IDC) using the idc-index Python package, filtering by metadata, visualizing in-browser, and checking licenses, with no authentication required. Use when obtaining large-scale radiology (CT, MR, PET) or digital pathology DICOM datasets for…
alterlab-pyhealth
Develops, tests, and validates clinical machine learning models with the PyHealth 2.x healthcare AI toolkit. Use when working with electronic health records (EHR), clinical prediction tasks (mortality, readmission, length of stay, drug recommendation), medical coding systems (ICD, NDC, ATC, CCS), physiological signals…
alterlab-anndata
Build, slice, concatenate, read, and write AnnData annotated data matrices (obs, var, X, layers, obsm, uns) — the scverse data STRUCTURE, not an analysis pipeline. Use when creating or wrangling .h5ad/zarr files, managing cell and gene annotations, concatenating batches, or handling layers/obsm/backed-mode; for the…
alterlab-tiledbvcf
Store and query genomic variant data at scale with TileDB-VCF — ingest VCF/BCF into compressed TileDB arrays, add samples incrementally, run fast parallel region/sample queries, and export back to VCF. Use when managing population-genomics variant datasets that are too large for flat VCF, building joint variant…
alterlab-datamol
Wraps RDKit in a high-level, pandas-friendly datamol interface with sensible defaults for everyday drug discovery — SMILES/SDF loading into DataFrames, molecule standardization, descriptors, fingerprints, Butina clustering, 3D conformer generation, scaffold analysis, and parallel batch processing, returning native…
alterlab-eda
Exploratory data analysis (EDA) on a scientific data file — auto-detects the format, runs structure/quality/statistics checks, and writes a markdown EDA report with downstream recommendations. Use when asked to "explore", "analyze", "summarize", "profile", or "QC" a data file, or to understand its…