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 aistats-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/aistats-writing-style)<a href="https://agentmods.dev/skills/brycewang-stanford/awesome-journal-skills/aistats-writing-style"><img src="https://agentmods.dev/badge/skills/brycewang-stanford/awesome-journal-skills/aistats-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/aistats-writing-style"><img src="https://agentmods.dev/badge/skills/brycewang-stanford/awesome-journal-skills/aistats-writing-style.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00059 | $0.00731 |
| Opus 5.5 | $0.00024 | $0.00292 |
| Sonnet 5.5 | $0.00012 | $0.00146 |
| Haiku 4.5 | $0.00006 | $0.00073 |
Grade A, and why
aistats-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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AISTATS Writing Style
Use this when revising the main paper. AISTATS papers need compact statements of why a statistical or ML contribution matters and enough detail for technical validation.
Revision rules
- Put the AI/statistics contribution in the first page: problem, gap, method or theorem, evidence, and why existing methods are insufficient.
- Make assumptions explicit. AISTATS reviewers are sensitive to hidden distributional, asymptotic, optimization, or data-generating assumptions.
- Pair every major claim with either proof structure, simulation design, empirical table, or reproducibility detail.
- Use the 8-page body for core logic; move long derivations, extra simulations, and extended ablations to the appendix without making the main paper unintelligible.
- Avoid overclaiming empirical wins when differences are small or variance is unreported.
- Maintain double-blind style in self-citations, prior code references, acknowledgements, funding, and artifact descriptions.
Theorem-presentation discipline
- Number assumptions and cite them by label inside every theorem statement; AISTATS readers audit assumption flows the way software reviewers audit imports.
- Give each major theorem a proof sketch in the body; the appendix proof supports the sketch but never replaces it.
- Keep problem-dependent constants visible or explicitly deferred; silently absorbing dimension or condition numbers into O-notation is a standing statistician complaint.
- Define notation once in one location — two-column pages punish redundant redefinition.
- Phrase remarks after theorems as interpretation, not as extra unproved claims; AISTATS reviewers treat every declarative sentence near a theorem as something they may verify.
- When a result is conjectured or only empirically supported, label it so; mixing proved and observed statements in one paragraph is a credibility leak at this venue.
Sentence-level rewrites
| Draft pattern | AISTATS-safe rewrite |
|---|---|
| "Our method significantly outperforms..." | "reduces mean error by X (SE Y) over Z seeded runs" |
| "Under mild conditions..." | "Under Assumptions 1-3 (boundedness, ...)" |
| "It is easy to see that..." | "By Lemma 2 and the triangle inequality..." |
| "Achieves state-of-the-art..." | Claim scoped to the regimes actually tested |
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 · 65 lines · 59 tokens per session scan A c2e10426ed37
aistats-writing-style is a skill published in the GitHub repository brycewang-stanford/Awesome-Journal-Skills (1,259 stars, last pushed 19d ago), licensed MIT. It adds 59 tokens to every session and 731 once invoked, about $0.0002 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-09-15.
Other skills, from other repositories
alterlab-qiime2-amplicon
Runs 16S/ITS amplicon (microbiome) analysis with the QIIME 2 distribution (2026.7; the "amplicon" distribution was renamed "qiime2" in 2026.4) in the correct order: manifest import, cutadapt trim-paired primer removal BEFORE dada2 denoise-paired (trunc-len chosen from the demux quality .qzv), feature-classifier…
research-manager
Use this when starting a new research project or managing a complex, multi-step research workflow.
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-citation-verifier
Verifies that every bibliography entry actually exists by cross-checking Crossref, OpenAlex, Semantic Scholar, and arXiv (no API key required) plus doi.org DOI registration, fuzzy-matching title and authors (difflib ratio >= 0.70), flagging retractions recorded by Crossref (including Retraction Watch data) or…
alterlab-timesfm
Forecasts time series zero-shot with Google's TimesFM foundation models — TimesFM 2.5 (200M, Apache-2.0 weights; ForecastConfig API, XReg covariates) and TimesFM 3.0 (330M, multivariate with native past/future covariates; non-commercial weights) — producing point forecasts and quantile prediction intervals from…
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…