Weekly Audit Patterns
amd/gaia
The non-obvious invariants of the proactive nightly Claude audit workflow (.github/workflows/claude-nightly-audit.yml): the day-of-week mode selector, the two-key dedup scheme (clusterkey per…
A skill your agent uses when auditing an ICCV submission in the weeks before the early-March deadline, covering OpenReview registration and profile completeness, the single same-day…
MITAuto-check passed
Install Iccv Submission
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill iccv-submission -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills iccv-submission --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/ICCV-Skills/skills/iccv-submission .claude/skills/iccv-submission && 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 "iccv-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICCV-Skills/skills/iccv-submission into .claude/skills/iccv-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iccv-submission", 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/ICCV-Skills/skills/iccv-submissionType 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 iccv-submission -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills iccv-submission --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/ICCV-Skills/skills/iccv-submission .agents/skills/iccv-submission && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "iccv-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICCV-Skills/skills/iccv-submission into .agents/skills/iccv-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iccv-submission", 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 iccv-submission -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills iccv-submission --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/ICCV-Skills/skills/iccv-submission .cursor/skills/iccv-submission && 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 "iccv-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICCV-Skills/skills/iccv-submission into .cursor/skills/iccv-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iccv-submission", 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 ICCV-Skills/skills/iccv-submission--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 iccv-submission -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills iccv-submission --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/ICCV-Skills/skills/iccv-submission .gemini/skills/iccv-submission && 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 "iccv-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICCV-Skills/skills/iccv-submission into .gemini/skills/iccv-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iccv-submission", 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 iccv-submissionInstalls 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 iccv-submission -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/ICCV-Skills/skills/iccv-submission .github/skills/iccv-submission && 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 "iccv-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICCV-Skills/skills/iccv-submission into .github/skills/iccv-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iccv-submission", 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 iccv-submission -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 iccv-submission --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/ICCV-Skills/skills/iccv-submission .opencode/skills/iccv-submission && 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 "iccv-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICCV-Skills/skills/iccv-submission into .opencode/skills/iccv-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iccv-submission", 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
iccv-submission- GitHub stars
- 1.2k
- Token cost
- ~1.8k tokens
- SKILL.md length
- 854 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when auditing an ICCV submission in the weeks before the early-March deadline, covering OpenReview registration and profile completeness, the single same-day…
- Auditing an ICCV submission in the weeks before the early-March deadline
- SKILL.md covers One upload event, not two, The three caps to check…, Reviewer enrollment is part of… and Anonymity, ICCV wording, plus 6 more sections
- Calls pdftotext
- Covering OpenReview registration and profile completeness
What it does
Iccv Submission is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when auditing an ICCV submission in the weeks before the early-March deadline, covering OpenReview registration and profile completeness, the single same-day paper-plus-supplement upload, the 8-page inclusive format, the 25-submissions-per-author cap, every-author reviewer enrollment, anonymity and media-embargo rules, and desk-reject triage.
Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
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
- Auditing an ICCV submission in the weeks before the early-March deadline
- Covering OpenReview registration and profile completeness
- The single same-day paper-plus-supplement upload
- The 8-page inclusive format
Example prompts
- “/iccv-submission”
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
Shell commands in SKILL.md call:
pdftotext
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
Iccv Submission loads about 1.8k tokens when it runs. Until then it costs about 91 tokens; SKILL.md has 854 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). 854 words, ~1,776 tokens.
Download SKILL.mdSave it as
.claude/skills/iccv-submission/SKILL.md (or your agent's skills folder).- name
- iccv-submission
- description
- Use when auditing an ICCV submission in the weeks before the early-March deadline, covering OpenReview registration and profile completeness, the single same-day paper-plus-supplement upload, the 8-page inclusive format, the 25-submissions-per-author cap, every-author reviewer enrollment, anonymity and media-embargo rules, and desk-reject triage.
ICCV Submission
This is the pre-flight audit for an ICCV upload. Anchors are the ICCV 2025 cycle (registration March 3; paper and supplementary material March 7, 2025, 11:59pm HST; verified via official-page renderings on 2026-07-08). The 2027 cycle had published no instructions at check time — re-read the live Author Guidelines, Dates, and Submission Checklist pages before acting on any number below.
One upload event, not two
ICCV 2025 deliberately merged what its CVF siblings stagger: the main paper and the supplementary archive were due together. The consequences for your audit:
- The supplement must pass the same review-readiness bar as the paper on the same night — schedule its freeze for the same internal deadline.
- There is no post-deadline week to render videos, scrub code, or fix a corrupt zip. A supplement that fails to upload is simply absent from review.
- Registration (title, abstract, author list, complete OpenReview profiles for everyone) closes days earlier. After it, you cannot add authors casually — the list you register is the list you defend.
The three caps to check mechanically
| Cap | 2025 value | Consequence of violation |
|---|---|---|
| Page budget | 8 pages including figures and tables; extra pages for cited references only | Rejected without review |
| Per-author submissions | 25 registered papers per author | Excess submissions desk-rejected by the PCs |
| Rebuttal (later) | One page, official template | Longer responses not read — plan evidence density now |
The 25-paper cap sounds unreachable until a big-lab PI's name is on thirty submissions; confirm every senior coauthor's count before registration day.
Reviewer enrollment is part of this form
Submitting to ICCV 2025 enrolled every author as a reviewer unless they held another conference role or were exempted as new to / outside the vision community. Enforcement was real: the 2025 PCs desk-rejected 29 papers because 25 of their authors reviewed irresponsibly (one-sentence reviews, LLM-generated reviews, reviews ignoring most of the paper), including 12 papers that would otherwise have been accepted. Your submission audit therefore includes a people audit: which coauthors will carry review load in March–May, and who checks their drafts.
Anonymity, ICCV wording
- Double-blind throughout paper and supplement: no author names, affiliations, acknowledgements, grant numbers, or identifying dataset paths.
- arXiv is explicitly tolerated: posting a preprint is not an anonymity violation on the authors' part, and reviewers are instructed accordingly.
- Your public codebase is different: the 2025 guidance says do not cite it — write "code will be made publicly available" instead of linking a repo whose owner field is your lab.
- Media embargo: papers under review may not be pitched to or discussed with media until acceptance; a violation removes the paper from the conference and proceedings.
- GitHub documents are not publications under the dual-submission policy — a public repo does not make your work "previously published," and equally does not license a substantially similar manuscript under review elsewhere.
Mechanical sweep, deadline week
# Run against the final PDF and the supplement archive together
pdftotext iccv_final.pdf - | grep -niE 'acknowledg|grant no|our (code|repo) at|github\.com/[a-z]' | head
pdfinfo iccv_final.pdf | grep -iE 'author|creator|title' # metadata identity
unzip -l supplement.zip | grep -iE '\.git|DS_Store|home/|users/' # path leaks in the archive
grep -rn 'setlength\|newgeometry\|baselinestretch' *.tex # style tampering tells
pdftotext iccv_final.pdf - | grep -c '' # >0 lines: text layer intactEvery hit is a blocker, not a judgment call: formatting violations and identity leaks are rejected without review at CVF venues, and no discussion phase exists to appeal a desk reject.
Show full SKILL.md (356 more words)Show less
Form fields that bite at midnight
OpenReview fields deserve a dry run a full day early. The abstract you registered on registration day drives reviewer bidding — if the paper's framing shifted since, update the field to match the PDF exactly. Subject areas route the paper to its reviewer pool: pick the areas whose reviewers you want, not every area the paper touches. Conflicts must be complete for all authors; a missing conflict discovered in May cannot be fixed. And the HST timezone (2025) is a gift only to teams who noticed it — put the converted local time in the calendar, with a two-hour pad.
Triage table for the final 48 hours
| Finding | Action | Deadline sensitivity |
|---|---|---|
| A coauthor's OpenReview profile incomplete | That author completes it now; profiles were required at registration | Hard stop at registration day |
| Page 9 has a caption tail or appendix line | Recut; only references may overflow | Hard stop at paper deadline |
| Supplement references "Sec. F" that does not exist | Fix pointer or add section | Same night — no supplement week |
| Repo link in a footnote | Replace with availability statement | Same night |
| Senior coauthor at 26 registered papers | Withdraw one before the PCs choose for you | Registration day |
| Abstract field ≠ PDF abstract | Paste PDF version into form | Same night |
Withdrawal is also a form action
If the paper must come out of the pool — a fatal bug found in April, a
dual-submission conflict discovered late — withdraw through OpenReview rather
than silently abandoning it: an unwithdrawn broken paper still consumes three
reviewers' labor at a venue that measures reviewer load in the tens of
thousands, and it stays attached to your OpenReview identity. Withdrawn ICCV
2025 papers with at least one completed review round also fed the Findings
pipeline (iccv-review-process), so withdrawal timing can affect that option.
Cycle-volatility ledger
Reopen the current pages for: both deadline dates and their timezone; whether the unified paper+supplement deadline persists; the exemption wording for reviewer enrollment; the per-author cap; supplement size/format limits (unverified even for 2025 — 待核实); and the Submission Checklist page the 2025 cycle published, which is the closest thing to an official version of this skill.
Output format
[Submission verdict] go / go-with-fixes / no-go
[Registration] profiles+authors+abstract locked by: <date>
[Caps] pages OK / author-counts OK / template untouched
[Anonymity] sweep hits: <none or list>
[Supplement] frozen same-night: yes/no; pointers resolve: n/m
[Duty exposure] reviewing coauthors identified: yes/no
[Fix order] <blockers first, then risks>© 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 ICCV-Skills/skills/iccv-submission of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Iccv Submission 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 |
|---|---|---|---|---|---|---|
| Iccv Submission this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.8k | Automated safety check: Pass | MIT | |
| Weekly Audit Patternsamd/gaia | 1.6k | — | ~4.4k | Automated safety check: Pass | MIT | |
| Production Auditaffaan-m/ECC | 277k | 1 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Aims Auditalirezarezvani/claude-skills | 28k | — | ~1.3k | Automated safety check: Pass | MIT | |
| Geo Auditsickn33/agentic-awesome-skills | 47k | 1 repos | ~3.4k | Automated safety check: Notes | MIT | |
| Skills Auditlobehub/lobehub | 83k | — | ~1.7k | Automated safety check: Pass | Custom licence |
Similar skills
Production Audit
affaan-m/ECC
Local-evidence production readiness audit for shipped apps, pre-launch reviews, post-merge checks, and "what breaks in prod?" questions without sending repo data to an external audit service.
Aims Audit
alirezarezvani/claude-skills
/cs:aims-audit <scope — ISO/IEC 42001 AIMS internal-audit 6-question forcing interrogation.
Geo Audit
sickn33/agentic-awesome-skills
Full website GEO+SEO audit with parallel subagent delegation.
Skills Audit
lobehub/lobehub
Audits a project's .agents/skills folder for duplicate, overlapping, stale or broken skills and suggests merge or delete candidates, weekly or after skill changes.
OmniRoute Audit and Policy CLI
diegosouzapw/OmniRoute
Command reference for omniroute's audit, logs, policy and telemetry commands: search and export audit trails, manage access policies and review request history for compliance work.
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…
Questions about Iccv Submission
What does Iccv Submission do?
A skill your agent uses when auditing an ICCV submission in the weeks before the early-March deadline, covering OpenReview registration and profile completeness, the single same-day…. Iccv Submission is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when auditing an ICCV submission in the weeks before the early-March deadline, covering OpenReview registration and profile completeness, the single same-day paper-plus-supplement upload, the 8-page inclusive format, the 25-submissions-per-author cap, every-author reviewer enrollment, anonymity and media-embargo rules, and desk-reject triage.
When should I use Iccv Submission?
Iccv Submission fits situations like: auditing an ICCV submission in the weeks before the early-March deadline; covering OpenReview registration and profile completeness; the single same-day paper-plus-supplement upload; the 8-page inclusive format.
How do I install Iccv Submission in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill iccv-submission -a claude-code`. Or copy the skill folder (ICCV-Skills/skills/iccv-submission in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/iccv-submission in your project. Claude Code loads it when a task matches its description.
How do I install Iccv Submission in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill iccv-submission -a codex`. Or copy the skill folder (ICCV-Skills/skills/iccv-submission in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/iccv-submission in your project. Codex loads it when a task matches its description.
Can I use Iccv Submission 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 iccv-submission -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/iccv-submission, .gemini/skills/iccv-submission, .github/skills/iccv-submission and .opencode/skills/iccv-submission in your project.
What does Iccv Submission need to run?
Going by SKILL.md and its folder, Iccv Submission needs the command-line tools its instructions call (pdftotext).
Does Iccv Submission 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 Iccv Submission 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 Iccv Submission use?
Iccv Submission 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 Iccv Submission use?
About 1.8k tokens (SKILL.md is roughly 7.1k 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 Iccv Submission?
Skills that share tags, products or a category with Iccv Submission: Weekly Audit Patterns (amd/gaia, 1.6k stars), Production Audit (affaan-m/ECC, 277k stars), Aims Audit (alirezarezvani/claude-skills, 28k stars) and Geo Audit (sickn33/agentic-awesome-skills, 47k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Iccv Submission?
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.