Prose Style
avelikiy/great_cto
Reusable writing-style contract for agent outputs (reports, ARCH docs, verdicts, threat models).
Agent skill
Usenixsec Writing Style
by brycewang-stanford in brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when drafting or revising prose for a USENIX Security Symposium paper — threat-model-first structure, calibrated security claims, disclosure narrative woven into the text…
Install Usenixsec Writing Style
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill usenixsec-writing-style -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills usenixsec-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/USENIX-Security-Skills/skills/usenixsec-writing-style .claude/skills/usenixsec-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 "usenixsec-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/USENIX-Security-Skills/skills/usenixsec-writing-style into .claude/skills/usenixsec-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "usenixsec-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/USENIX-Security-Skills/skills/usenixsec-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 usenixsec-writing-style -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills usenixsec-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/USENIX-Security-Skills/skills/usenixsec-writing-style .agents/skills/usenixsec-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 "usenixsec-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/USENIX-Security-Skills/skills/usenixsec-writing-style into .agents/skills/usenixsec-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "usenixsec-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 usenixsec-writing-style -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills usenixsec-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/USENIX-Security-Skills/skills/usenixsec-writing-style .cursor/skills/usenixsec-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 "usenixsec-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/USENIX-Security-Skills/skills/usenixsec-writing-style into .cursor/skills/usenixsec-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "usenixsec-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 USENIX-Security-Skills/skills/usenixsec-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 usenixsec-writing-style -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills usenixsec-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/USENIX-Security-Skills/skills/usenixsec-writing-style .gemini/skills/usenixsec-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 "usenixsec-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/USENIX-Security-Skills/skills/usenixsec-writing-style into .gemini/skills/usenixsec-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "usenixsec-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 usenixsec-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 usenixsec-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/USENIX-Security-Skills/skills/usenixsec-writing-style .github/skills/usenixsec-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 "usenixsec-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/USENIX-Security-Skills/skills/usenixsec-writing-style into .github/skills/usenixsec-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "usenixsec-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 usenixsec-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 usenixsec-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/USENIX-Security-Skills/skills/usenixsec-writing-style .opencode/skills/usenixsec-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 "usenixsec-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/USENIX-Security-Skills/skills/usenixsec-writing-style into .opencode/skills/usenixsec-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "usenixsec-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
usenixsec-writing-style- GitHub stars
- 1.2k
- Token cost
- ~1.3k tokens
- SKILL.md length
- 580 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 prose for a USENIX Security Symposium paper — threat-model-first structure, calibrated security claims, disclosure narrative woven into the text…
- Works in 4 steps: Adversary-consistency pass: every… → Calibration pass: hunt "completely /… → Cold-reader pass: someone outside the… → …
- Revising prose for a USENIX Security Symposium paper — threat-model-first structure
- SKILL.md covers Structure: the threat model is…, Claim calibration, the house…, The disclosure narrative… and Register and mechanics, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Usenixsec Writing Style is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when drafting or revising prose for a USENIX Security Symposium paper — threat-model-first structure, calibrated security claims, disclosure narrative woven into the text, 13-page discipline in the USENIX template, and the plain systems-security register this program committee rewards.
Its SKILL.md is about 1.3k 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 and Threat modeling. 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 prose for a USENIX Security Symposium paper — threat-model-first structure
- Calibrated security claims
- Disclosure narrative woven into the text
- 13-page discipline in the USENIX template
Example prompts
- “/usenixsec-writing-style”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Adversary-consistency pass: every evaluation claim re-checked against the
- Calibration pass: hunt "completely / trivially / negligible / guarantees"
- Cold-reader pass: someone outside the subfield reads intro + threat model
- Caption pass: figures/tables self-contained, units and populations stated.
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
Usenixsec Writing Style loads about 1.3k tokens when it runs. Until then it costs about 79 tokens; SKILL.md has 580 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). 580 words, ~1,342 tokens.
Download SKILL.mdSave it as
.claude/skills/usenixsec-writing-style/SKILL.md (or your agent's skills folder).- name
- usenixsec-writing-style
- description
- Use when drafting or revising prose for a USENIX Security Symposium paper — threat-model-first structure, calibrated security claims, disclosure narrative woven into the text, 13-page discipline in the USENIX template, and the plain systems-security register this program committee rewards.
USENIX Security Writing Style
A USENIX Security paper argues like an engineer under oath: state what the adversary can do, show what you built or broke, measure it honestly, and say plainly what does not follow. The style advice here is calibrated to the '26 CFP's format rules and to the venue's reviewing culture; format numbers are one cycle's snapshot.
Structure: the threat model is load-bearing
Readers at this venue locate every claim relative to an adversary. Put the threat model early (typically Section 2 or 3), make it precise, and never let the evaluation quietly assume a stronger or weaker attacker than the model granted:
- Name capabilities concretely: network position, code execution level, query budget, physical access, knowledge of the defense.
- Name non-goals just as concretely — "side channels are out of scope" is a legitimate sentence that prevents an entire review thread.
- For measurement papers, the analogue is the vantage and validity statement: where you measured from, when, and what the view cannot see.
A body plan that fits the 13 pages without heroics:
| Section | Budget | Job |
|---|---|---|
| Intro | 1–1.25 pp | Problem, adversary, contribution bullets with numbers |
| Background + threat model | 1.5–2 pp | Just enough context; precise adversary |
| Design / attack technique | 3–4 pp | The mechanism, end to end |
| Evaluation | 3.5–4.5 pp | Setup, headline results, adaptive/robustness analysis |
| Discussion + limitations | 0.75–1 pp | What breaks, what it costs, what's unknown |
| Related work | 0.75–1 pp | Positioning (see usenixsec-related-work) |
Then the two mandatory appendices, then references — geometry per
usenixsec-supplementary.
Claim calibration, the house dialect
Security prose fails in two symmetric ways: marketing ("we completely prevent...") and false modesty that buries a real result. The venue's fix is quantified hedging — every strong verb carries its measurement:
Weak: Our defense stops code-reuse attacks with negligible overhead.
Better: Against the 412 ROP chains in our corpus, the defense blocks all
chains that pivot through heap pointers (387/412; the remaining 25
use stack-only gadgets, Section 6.3) at a 2.1% median CPU overhead
(max 4.8%) on SPEC CPU 2017.
Weak: Attackers can trivially bypass existing scanners.
Better: Eight of the eleven scanners we tested miss payloads transformed by
our encoder; the three that detect it do so via rule R117, which
also flags 4% of benign traffic in our enterprise trace.Rules of thumb: numbers beat adverbs; populations beat anecdotes ("all 412" not "attacks"); every "first" gets a scope ("first automated analysis of X at ISP scale"); failure cases appear in the same paragraph as the success rate.
Show full SKILL.md (264 more words)Show less
The disclosure narrative belongs in the prose
Papers here often describe live harm potential. Beyond the mandatory Ethical
Considerations appendix, weave the responsible-conduct thread into the body where
the reader needs it: the scan methodology paragraph states the rate limits and
opt-out handling; the vulnerability section states "reported to the vendor on
<date>; patched in version Y" at the moment the flaw is introduced. Reviewers
should never wonder, mid-section, whether the experiment was run responsibly.
Register and mechanics
- Plain systems English. Define acronyms once; this community tolerates jargon density but punishes ambiguity about which TEE/DOM/EL2 you mean.
- Present tense for the system and its properties; past tense for experiments run.
- Figures carry the argument in evaluation sections — a reviewer flipping pages should reconstruct the results story from captions alone.
- Name the system early and use the name consistently; anonymize any name that is publicly attached to your group at submission time.
- Unaltered USENIX LaTeX template; compression comes from cutting re-narration of tables and consolidating examples, never from spacing tricks (forbidden by CFP).
Revision passes that pay at this venue
- Adversary-consistency pass: every evaluation claim re-checked against the stated threat model.
- Calibration pass: hunt "completely / trivially / negligible / guarantees" and attach numbers or delete.
- Cold-reader pass: someone outside the subfield reads intro + threat model only, then writes down what they think the paper claims — mismatch means the framing leaks.
- Caption pass: figures/tables self-contained, units and populations stated.
Reverify each cycle
- Page budget and template version in the current CFP ('27 values 待核实).
- Any new style-adjacent mandates (AI-writing disclosure, reporting checklists).
Output format
[Threat model] section, precision verdict, evaluation-consistency check
[Calibration] flagged claims + rewrites
[Disclosure thread] present at point-of-need in body: yes / gaps
[Budget] per-section page usage vs plan; overflow routing© 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 USENIX-Security-Skills/skills/usenixsec-writing-style of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Usenixsec 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 |
|---|---|---|---|---|---|---|
| Usenixsec Writing Style this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.3k | Automated safety check: Pass | MIT | |
| Prose Styleavelikiy/great_cto | 102 | — | ~1k | 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 |
Similar skills
Avoid AI Writing
conorbronsdon/avoid-ai-writing
Audit and rewrite content to remove AI writing patterns ("AI-isms").
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.
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 Usenixsec Writing Style
What does Usenixsec Writing Style do?
A skill your agent uses when drafting or revising prose for a USENIX Security Symposium paper — threat-model-first structure, calibrated security claims, disclosure narrative woven into the text…. Usenixsec Writing Style is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when drafting or revising prose for a USENIX Security Symposium paper — threat-model-first structure, calibrated security claims, disclosure narrative woven into the text, 13-page discipline in the USENIX template, and the plain systems-security register this program committee rewards.
When should I use Usenixsec Writing Style?
Usenixsec Writing Style fits situations like: revising prose for a USENIX Security Symposium paper — threat-model-first structure; calibrated security claims; disclosure narrative woven into the text; 13-page discipline in the USENIX template.
How do I install Usenixsec Writing Style in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill usenixsec-writing-style -a claude-code`. Or copy the skill folder (USENIX-Security-Skills/skills/usenixsec-writing-style in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/usenixsec-writing-style in your project. Claude Code loads it when a task matches its description.
How do I install Usenixsec Writing Style in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill usenixsec-writing-style -a codex`. Or copy the skill folder (USENIX-Security-Skills/skills/usenixsec-writing-style in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/usenixsec-writing-style in your project. Codex loads it when a task matches its description.
Can I use Usenixsec 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 usenixsec-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/usenixsec-writing-style, .gemini/skills/usenixsec-writing-style, .github/skills/usenixsec-writing-style and .opencode/skills/usenixsec-writing-style in your project.
What does Usenixsec Writing Style need to run?
SKILL.md names no scripts, command-line tools or credentials: Usenixsec Writing Style is instructions for the agent only.
Does Usenixsec 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 Usenixsec 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 Usenixsec Writing Style use?
Usenixsec 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 Usenixsec Writing Style use?
About 1.3k tokens (SKILL.md is roughly 5.4k 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 Usenixsec Writing Style?
Skills that share tags, products or a category with Usenixsec Writing Style: Prose Style (avelikiy/great_cto, 102 stars), Avoid AI Writing (conorbronsdon/avoid-ai-writing, 4.9k stars), Brand (Ohh-889/skyroc, 795 stars) and Khazix WeChat Article Writer (KKKKhazix/khazix-skills, 21k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Usenixsec 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.