Use when drafting or polishing the prose of an Environmental Science & Technology (ES&T) manuscript so it reads for a multidisciplinary audience in ACS style and fits the article-type word limit. ES&T values clear environmental significance stated early, ACS citation style, and tight prose. It guides writing and structure; it does not invent content.
Scanned 6/5/2026
Install to Claude Code
npx -y skills add brycewang-stanford/Awesome-Journal-Skills --skill est-writing-style --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Est Writing Style?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/brycewang-stanford-est-writing-style)More formats (shields.io, HTML) on the badges page.
---
name: est-writing-style
description: Use when drafting or polishing the prose of an Environmental Science & Technology (ES&T) manuscript so it reads for a multidisciplinary audience in ACS style and fits the article-type word limit. ES&T values clear environmental significance stated early, ACS citation style, and tight prose. It guides writing and structure; it does not invent content.
---
# Writing Style (est-writing-style)
ES&T is read across environmental chemistry, engineering, toxicology, and policy, so the writing must
land the **environmental significance** quickly and stay legible to non-specialists — within a firm
word budget. House style is **ACS** (numbered citations).
## When to trigger
- Drafting the abstract, introduction, or conclusions
- Cutting a manuscript down to the article-type word limit
- Converting jargon-heavy prose into multidisciplinary-readable text
- Formatting citations and headings to ACS style
## Structure & style ES&T expects
1. **Significance up front.** The abstract and the end of the introduction must answer "why does this
matter for the environment?" — concretely (system, process, magnitude), not generically.
2. **Standard structure.** Abstract → Introduction → Materials and Methods → Results and Discussion →
(Conclusions/Implications) → Associated Content (SI) → references; adapt for Reviews/Perspectives/
Features.
3. **Write for the broad audience.** Define specialist terms on first use; avoid undefined acronyms;
lead paragraphs with the point, then the evidence.
4. **Word discipline.** Respect the per-type cap (Research Article ~7,000; Feature ~5,000; Review
~10,000; Perspective ~4,000; Policy Analysis ~7,000 — all 待核实) and remember exhibits may count
as word-equivalents. Move detail to the SI.
5. **ACS style.** Numbered citations in order of appearance; SI units; chemical names/formulae per
ACS conventions; an "Environmental Implications" framing where the genre fits.
6. **Features** are journalistic in tone; **Policy Analysis** speaks to the science–policy interface.
## Anti-patterns
- An abstract full of methods but no significance or headline result
- Generic significance ("important for the environment") with no mechanism, system, or magnitude
- Jargon and undefined acronyms that lock out non-specialist readers
- Blowing the word cap because robustness detail lives in the main text instead of the SI
- Mixed or non-ACS citation styles
- A discussion that restates results without interpreting environmental implications
## Output format
```
【Significance stated early】abstract + intro answer "why for the environment"? [Y/N]
【Structure】sections present and in order? [Y/N]
【Audience】jargon defined, readable across sub-fields? [Y/N]
【Word count】within type cap (note word-equivalents)? [count / cap]
【ACS style】numbered citations + SI units + conventions? [Y/N]
【Next】est-cover-letter
```
## Supplementary resources
- [`../../resources/external_tools.md`](../../resources/external_tools.md) — reference managers and ACS style resources
- [`../../resources/official-source-map.md`](../../resources/official-source-map.md) — article types, word limits, ACS style guide
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!