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 amann-editor-strategygit 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/amann-editor-strategy)<a href="https://agentmods.dev/skills/brycewang-stanford/awesome-journal-skills/amann-editor-strategy"><img src="https://agentmods.dev/badge/skills/brycewang-stanford/awesome-journal-skills/amann-editor-strategy/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/amann-editor-strategy"><img src="https://agentmods.dev/badge/skills/brycewang-stanford/awesome-journal-skills/amann-editor-strategy.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.00077 | $0.01208 |
| Opus 5.5 | $0.00031 | $0.00483 |
| Sonnet 5.5 | $0.00015 | $0.00242 |
| Haiku 4.5 | $0.00008 | $0.00121 |
Grade A, and why
amann-editor-strategy 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Editor & Referee Strategy for a Review (amann-editor-strategy)
When to trigger
- A proposal was invited and you are aligning the full review's scope with the editor
- You want to anticipate what Annals referees of a review push on (different from a paper)
- The editor has asked you to expand, cut, sharpen the framework, or rebalance coverage
- You are calibrating revision depth and the twice-yearly cadence
The editor relationship at Annals is unusually direct
Annals' process makes the editor your central partner — more than at most journals. The proposal is reviewed double-blind by the Associate Editors, but once invited, the full review forgoes double-blind and is developed primarily with the Associate Editor and Editor (检索于 2026-06；以官网为准). You are effectively co-developing the review with an expert editor who already endorsed the idea. Use that:
- The proposal is the scope contract. The four headings you committed to (Focus / Related reviews / Review scope and process / New insights) define what was invited. Departing from them silently is the fastest way to lose editor confidence — renegotiate explicitly if the literature pushes you elsewhere.
- Lead with the framework in every editor exchange. The editor invited a new way of seeing the field. Decisions about coverage, length, and balance should be argued from whether they strengthen the framework and agenda.
- Surface conflicts of interest early. If a likely referee is a central author you must critique, tell the editor; it protects the process and you.
- Calibrate the cadence. Annals runs on a twice-yearly proposal cycle and publishes two issues a year; full-review development and revision can be substantial and multi-round. Plan for real revision effort, not cosmetic edits.
How review differs for a review article
Annals referees do not check an identification strategy or replicate results — there are none. They evaluate the review as a review:
| Referee question | What they are really checking |
|---|---|
| Is there a genuine integrative framework? | the spine vs. an annotated bibliography (amann-organizing-framework) — the acceptance bar |
| Does it have "attitude"? | a critical, agenda-setting position grounded in evidence, not a neutral tour (amann-writing-style) |
| Is the coverage complete and systematic? | saturation + transparent search; can they name an omitted stream? (amann-literature-synthesis) |
| Is it balanced and fair? | even-handedness across schools; no self-promotion (amann-evidence-standards) |
| Are the appraisals accurate? | does the author characterize each study and its limits correctly |
| Is it the right scope? | broad enough for general interest, but coverable in one ~50-page article |
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 · 71 lines · 77 tokens per session scan A 69e1a3063034
amann-editor-strategy is a skill published in the GitHub repository brycewang-stanford/Awesome-Journal-Skills (1,289 stars, last pushed 26d ago), licensed MIT. It adds 77 tokens to every session and 1,208 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-09-15.
Other skills, from other repositories
research-manager
Use this when starting a new research project or managing a complex, multi-step research workflow.
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…
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…