Avoid AI Writing
conorbronsdon/avoid-ai-writing
Audit and rewrite content to remove AI writing patterns ("AI-isms").
A skill your agent uses when drafting or revising ASPLOS prose — engineering the first two pages that rapid review actually reads, stating the cross-layer insight as one quotable sentence…
Install Asplos Writing Style
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill asplos-writing-style -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills asplos-writing-style --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/ASPLOS-Skills/skills/asplos-writing-style .claude/skills/asplos-writing-style && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "asplos-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ASPLOS-Skills/skills/asplos-writing-style into .claude/skills/asplos-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "asplos-writing-style", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ASPLOS-Skills/skills/asplos-writing-styleType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill asplos-writing-style -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills asplos-writing-style --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/ASPLOS-Skills/skills/asplos-writing-style .agents/skills/asplos-writing-style && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "asplos-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ASPLOS-Skills/skills/asplos-writing-style into .agents/skills/asplos-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "asplos-writing-style", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill asplos-writing-style -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills asplos-writing-style --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/ASPLOS-Skills/skills/asplos-writing-style .cursor/skills/asplos-writing-style && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "asplos-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ASPLOS-Skills/skills/asplos-writing-style into .cursor/skills/asplos-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "asplos-writing-style", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/brycewang-stanford/Awesome-Journal-Skills.git --path ASPLOS-Skills/skills/asplos-writing-style--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill asplos-writing-style -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills asplos-writing-style --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/ASPLOS-Skills/skills/asplos-writing-style .gemini/skills/asplos-writing-style && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "asplos-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ASPLOS-Skills/skills/asplos-writing-style into .gemini/skills/asplos-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "asplos-writing-style", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills asplos-writing-styleInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill asplos-writing-style -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/ASPLOS-Skills/skills/asplos-writing-style .github/skills/asplos-writing-style && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "asplos-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ASPLOS-Skills/skills/asplos-writing-style into .github/skills/asplos-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "asplos-writing-style", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill asplos-writing-style -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills asplos-writing-style --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/ASPLOS-Skills/skills/asplos-writing-style .opencode/skills/asplos-writing-style && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "asplos-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ASPLOS-Skills/skills/asplos-writing-style into .opencode/skills/asplos-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "asplos-writing-style", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
asplos-writing-style- GitHub stars
- 1.2k
- Token cost
- ~1.7k tokens
- SKILL.md length
- 758 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when drafting or revising ASPLOS prose — engineering the first two pages that rapid review actually reads, stating the cross-layer insight as one quotable sentence…
- Revising ASPLOS prose — engineering the first two pages that rapid review actually reads
- SKILL.md covers Engineering pages 1-2 as a…, The insight sentence, Structuring the mechanism… and Claim calibration, systems…, plus 6 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Stating the cross-layer insight as one quotable sentence
What it does
Asplos Writing Style is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when drafting or revising ASPLOS prose — engineering the first two pages that rapid review actually reads, stating the cross-layer insight as one quotable sentence, structuring per-layer mechanism sections, writing bounded claims, and fitting everything into 11 self-contained pages that include figures and footnotes.
Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Writing & Content, covering Brand voice and tone. The repository describes itself as: Journal-specific Claude Code/Codex skill packs covering mainstream journals — AER, QJE, Nature, Cell, 管理世界, 经济研究 & 200+ more — your fast track to getting published. ｜ 覆盖主流期刊的… The licence is MIT.
When your agent uses it
- Revising ASPLOS prose — engineering the first two pages that rapid review actually reads
- Stating the cross-layer insight as one quotable sentence
- Structuring per-layer mechanism sections
- Writing bounded claims
Example prompts
- “/asplos-writing-style”
What it can do on your machine
Read from SKILL.md and the folder at commit 932eb23. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Asplos Writing Style loads about 1.7k tokens when it runs. Until then it costs about 86 tokens; SKILL.md has 758 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from brycewang-stanford/Awesome-Journal-Skills at commit 932eb23, republished under its MIT licence (© brycewang-stanford). 758 words, ~1,668 tokens.
Download SKILL.mdSave it as
.claude/skills/asplos-writing-style/SKILL.md (or your agent's skills folder).- name
- asplos-writing-style
- description
- Use when drafting or revising ASPLOS prose — engineering the first two pages that rapid review actually reads, stating the cross-layer insight as one quotable sentence, structuring per-layer mechanism sections, writing bounded claims, and fitting everything into 11 self-contained pages that include figures and footnotes.
ASPLOS Writing Style
Two 2027 mechanics dictate ASPLOS prose (CFP, checked 2026-07-08): the rapid review reads only the first two pages, and the 11-page limit counts all text, figures, tables, and footnotes — references excluded. The first makes pages 1-2 a survival organ; the second makes every figure a budget decision. Style here is mostly resource allocation.
Engineering pages 1-2 as a standalone document
By the bottom of page 2, a screener must hold four things. Audit for them mechanically, in order:
| Element | Test | Common failure |
|---|---|---|
| Cross-layer problem | Can a reader from any of the three communities restate it? | A single-community problem with "co-design" sprinkled on |
| One-sentence insight | Is there a sentence a screener could quote in their note? | Insight diffused across three paragraphs, or a category ("we co-design X and Y") instead of an idea |
| Mechanism sketch | Does the reader know what each layer does? | Architecture described, software hand-waved (or vice versa) |
| Headline evidence | Result + platform class (silicon/FPGA/simulator) + baseline named? | "Significant improvements on a variety of workloads" |
Corollary: background sections, notation, and roadmaps do not belong on pages 1-2.
The worked example (../../resources/worked-examples/01-introduction.md) shows a
full before → after against exactly this table.
The insight sentence
The load-bearing sentence in an ASPLOS paper names information or capability that crosses a layer boundary: what the hardware knows that the OS needs, what the compiler can prove that the microarchitecture can exploit. Drafting discipline:
Weak: "We propose a hardware/software co-designed approach to memory tiering."
(names a category and a topic; contains no idea)
Strong: "The contention data the OS needs already passes through the memory
controller on every access; the fix is a narrow architectural channel,
not a smarter kernel heuristic."
(names the information, its current location, and the boundary moved)If this sentence cannot be written, the problem is usually fit, not prose — return
to asplos-topic-selection.
Structuring the mechanism across layers
Give each layer its own subsection with its own contribution statement, then a section for the interface between them — the interface is the paper's actual thesis and deserves first-class treatment (encoding, semantics, virtualization behavior, failure modes). Reviewers from different communities will each read "their" subsection closely; the interface section is where they meet.
Claim calibration, systems dialect
- Bound claims by construction: "never regresses more than 2% on our non-tiered suite" is a stronger sentence than "negligible overhead."
- Attach the instrument to the number in the same sentence: "1.18× gmean on real hardware (14 workloads)" vs "up to 3.4× in simulation" are different epistemic objects and must not blend.
- Write the losing case in the same register as the winning ones. One honestly analyzed regression buys more reviewer trust than a page of wins.
The 11-page budget with figures inside it
Because figures count against the limit, they compete with prose on equal terms:
- Every figure must either carry a claim or explain the mechanism; delete gallery plots and merge panels that make one point.
- Prefer one annotated diagram of the boundary/interface over three block diagrams of components — reviewers cite the diagram that explains the idea.
- Compression order when over budget: cut duplicate-message plots → collapse per-workload bars into summary + appendix grid → tighten mechanism prose → never touch template geometry (mandatory template; violations risk rejection unread).
Show full SKILL.md (283 more words)Show less
House-rule details that mark a native submission
- References carry every author's full first and last name — no "et al." — with hyperlinked in-text numbers and DOIs per entry; a hygiene-signaling detail reviewers notice early.
- Third-person self-citation throughout; no "removed for blind review" text.
- GenAI assistance, if any, disclosed per ACM policy (Acknowledgments, immediately before References).
A load-order for the abstract
Six sentences, in this order, cover what both the rapid screener and the eventual citer need: (1) the friction two layers create today; (2) the insight sentence; (3) the mechanism, one clause per layer; (4) the headline number with instrument and baseline; (5) the bound on the downside; (6) what the interface enables beyond this paper. Most first drafts invert 1 and a background sentence — delete the background sentence; ASPLOS readers do not need to be told memory matters.
Section skeleton that serves three readerships
A cross-layer paper defaults well to: motivation-with-evidence (measured, not
asserted — a characterization figure beats three citations); design overview
around one boundary diagram; per-layer mechanism sections; the interface
section; evaluation ordered by the claim matrix; related work by lanes
(asplos-related-work); then discussion of what the boundary change costs.
Each community's reviewer should be able to find "their" section from the table
of contents alone — a paper organized by implementation chronology instead
forces reviewers to reconstruct the design, and annoyed reconstruction reads as
"unclear writing" in reviews.
Revision-aware prose
Because Major Revision is a standing outcome, write sentences that can absorb revision without rewiring: quantitative claims phrased with their scope ("across the 14-workload suite") extend gracefully when workloads are added; hard-coded superlatives ("the first", "the fastest") require re-litigation at every resubmission and are the first phrases a shepherd strikes.
Output format
[Two-page audit] problem / insight-sentence / mechanism / evidence — each Y/N + fix
[Insight sentence] <quoted verbatim>
[Layer structure] per-layer subsections + interface section present: Y/N
[Claim calibration] unbounded adjectives found: N · instrument attached per number: Y/N
[Figure budget] figures: N · pages consumed: N · deletions/merges proposed
[House rules] citations format / self-cite person / GenAI disclosure — pass/fail© brycewang-stanford, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in ASPLOS-Skills/skills/asplos-writing-style of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Asplos Writing Style next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Asplos Writing Style this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.7k | Automated safety check: Pass | MIT | |
| Avoid AI Writingconorbronsdon/avoid-ai-writing | 4.9k | 3 repos | ~8.1k | Automated safety check: Pass | MIT | |
| BrandOhh-889/skyroc | 795 | 13 repos | ~733 | Automated safety check: Pass | MIT | |
| Khazix WeChat Article WriterKKKKhazix/khazix-skills | 21k | 1 repos | ~2.9k | Automated safety check: Pass | MIT | |
| Writing Guidelinesvercel-labs/agent-skills | 32k | 7 repos | ~309 | Automated safety check: Pass | None | |
| Unslop AI Writing Cleanuptheclaymethod/unslop | 518 | — | ~1.7k | Automated safety check: Pass | MIT |
Similar skills
Brand
Ohh-889/skyroc
Brand voice, visual identity, messaging frameworks, asset management, brand consistency.
Khazix WeChat Article Writer
KKKKhazix/khazix-skills
Writes long-form WeChat official account articles in the personal style of the Khazix account, from briefs, links, PDFs or rough notes, with a topic quality check.
- Official
Writing Guidelines
vercel-labs/agent-skills
Review docs/prose for Writing Guidelines compliance. An agent skill from vercel-labs/agent-skills.
Unslop AI Writing Cleanup
theclaymethod/unslop
Removes AI writing tells from prose through an audit-first flow, routing to a two-pass rewrite, a report-only cleanup, voice teaching or mimicry depending on the sub-command used.
UX Writing
content-designer/ux-writing-skill
Applies UX writing practice to interface copy such as buttons, errors, forms and onboarding, using four quality standards and accessibility guidance.
More from brycewang-stanford/Awesome-Journal-Skills
All 2,387 skills in this repoAaag Data Analysis
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running and reporting the analysis for an Annals of the American Association of Geographers manuscript — spatial statistics and modeling, remote-sensing accuracy, or…
Aaag Literature Positioning
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when positioning an Annals of the American Association of Geographers manuscript in the literature — engaging geographic scholarship across the relevant area and the…
Aaag Rebuttal
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when responding to an Annals of the American Association of Geographers decision letter (major/minor revision) — building a point-by-point response to the subject editor and…
Aaag Research Design
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when defending the research design of an Annals of the American Association of Geographers manuscript — spatial/quantitative analysis and GIScience, remote-sensing and…
Aaag Review Process
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when you need to understand how the Annals of the American Association of Geographers evaluates a manuscript — double-anonymous review routed through a subject editor by…
Aaag Submission
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running the final pre-submission preflight for the Annals of the American Association of Geographers via ScholarOne Manuscripts — area/article-type selection…
Related
Categories
Questions about Asplos Writing Style
What does Asplos Writing Style do?
A skill your agent uses when drafting or revising ASPLOS prose — engineering the first two pages that rapid review actually reads, stating the cross-layer insight as one quotable sentence…. Asplos Writing Style is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when drafting or revising ASPLOS prose — engineering the first two pages that rapid review actually reads, stating the cross-layer insight as one quotable sentence, structuring per-layer mechanism sections, writing bounded claims, and fitting everything into 11 self-contained pages that include figures and footnotes.
When should I use Asplos Writing Style?
Asplos Writing Style fits situations like: revising ASPLOS prose — engineering the first two pages that rapid review actually reads; stating the cross-layer insight as one quotable sentence; structuring per-layer mechanism sections; writing bounded claims.
How do I install Asplos Writing Style in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill asplos-writing-style -a claude-code`. Or copy the skill folder (ASPLOS-Skills/skills/asplos-writing-style in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/asplos-writing-style in your project. Claude Code loads it when a task matches its description.
How do I install Asplos Writing Style in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill asplos-writing-style -a codex`. Or copy the skill folder (ASPLOS-Skills/skills/asplos-writing-style in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/asplos-writing-style in your project. Codex loads it when a task matches its description.
Can I use Asplos Writing Style in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill asplos-writing-style -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/asplos-writing-style, .gemini/skills/asplos-writing-style, .github/skills/asplos-writing-style and .opencode/skills/asplos-writing-style in your project.
What does Asplos Writing Style need to run?
SKILL.md names no scripts, command-line tools or credentials: Asplos Writing Style is instructions for the agent only.
Does Asplos Writing Style access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Asplos Writing Style safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Asplos Writing Style use?
Asplos Writing Style is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Asplos Writing Style use?
About 1.7k tokens (SKILL.md is roughly 6.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Asplos Writing Style?
Skills that share tags, products or a category with Asplos Writing Style: Avoid AI Writing (conorbronsdon/avoid-ai-writing, 4.9k stars), Brand (Ohh-889/skyroc, 795 stars), Khazix WeChat Article Writer (KKKKhazix/khazix-skills, 21k stars) and Writing Guidelines (vercel-labs/agent-skills, 32k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Asplos Writing Style?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,231 GitHub stars. The repository holds 2,387 skills in this directory. The repository was last updated on September 27, 2026.
Source: brycewang-stanford/Awesome-Journal-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.