Read arXiv Paper
karpathy/nanochat
Fetches the TeX source of an arXiv paper from its URL, reads it and writes a markdown summary tied to the nanochat project.
A skill your agent uses when architecting everything beyond the first twelve pages of a STOC (ACM Symposium on Theory of Computing) submission — the discretionary-read appendix, the reviewed table…
Install Stoc Supplementary
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill stoc-supplementary -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills stoc-supplementary --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/STOC-Skills/skills/stoc-supplementary .claude/skills/stoc-supplementary && 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 "stoc-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/STOC-Skills/skills/stoc-supplementary into .claude/skills/stoc-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stoc-supplementary", 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/STOC-Skills/skills/stoc-supplementaryType 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 stoc-supplementary -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills stoc-supplementary --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/STOC-Skills/skills/stoc-supplementary .agents/skills/stoc-supplementary && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "stoc-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/STOC-Skills/skills/stoc-supplementary into .agents/skills/stoc-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stoc-supplementary", 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 stoc-supplementary -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills stoc-supplementary --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/STOC-Skills/skills/stoc-supplementary .cursor/skills/stoc-supplementary && 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 "stoc-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/STOC-Skills/skills/stoc-supplementary into .cursor/skills/stoc-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stoc-supplementary", 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 STOC-Skills/skills/stoc-supplementary--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 stoc-supplementary -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills stoc-supplementary --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/STOC-Skills/skills/stoc-supplementary .gemini/skills/stoc-supplementary && 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 "stoc-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/STOC-Skills/skills/stoc-supplementary into .gemini/skills/stoc-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stoc-supplementary", 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 stoc-supplementaryInstalls 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 stoc-supplementary -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/STOC-Skills/skills/stoc-supplementary .github/skills/stoc-supplementary && 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 "stoc-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/STOC-Skills/skills/stoc-supplementary into .github/skills/stoc-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stoc-supplementary", 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 stoc-supplementary -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 stoc-supplementary --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/STOC-Skills/skills/stoc-supplementary .opencode/skills/stoc-supplementary && 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 "stoc-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/STOC-Skills/skills/stoc-supplementary into .opencode/skills/stoc-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stoc-supplementary", 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
stoc-supplementary- GitHub stars
- 1.2k
- Token cost
- ~1.7k tokens
- SKILL.md length
- 779 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when architecting everything beyond the first twelve pages of a STOC (ACM Symposium on Theory of Computing) submission — the discretionary-read appendix, the reviewed table…
- The reviewed table of contents
- SKILL.md covers The table of contents is part…, Placement decision table, Pointer discipline and What the appendix is not for, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Theorem-to-proof pointer discipline
What it does
Stoc Supplementary is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when architecting everything beyond the first twelve pages of a STOC (ACM Symposium on Theory of Computing) submission — the discretionary-read appendix, the reviewed table of contents, theorem-to-proof pointer discipline, and the division of labor between the submission appendix and the arXiv/ECCC full version.
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 Research & Science, covering Academic paper search. It works with arXiv. 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
- The reviewed table of contents
- Theorem-to-proof pointer discipline
- The division of labor between the submission appendix and the arXiv/ECCC full version
Example prompts
- “/stoc-supplementary”
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 (its code samples are latex).
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
Stoc Supplementary loads about 1.7k tokens when it runs. Until then it costs about 84 tokens; SKILL.md has 779 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). 779 words, ~1,660 tokens.
Download SKILL.mdSave it as
.claude/skills/stoc-supplementary/SKILL.md (or your agent's skills folder).- name
- stoc-supplementary
- description
- Use when architecting everything beyond the first twelve pages of a STOC (ACM Symposium on Theory of Computing) submission — the discretionary-read appendix, the reviewed table of contents, theorem-to-proof pointer discipline, and the division of labor between the submission appendix and the arXiv/ECCC full version.
STOC Supplementary
STOC has no supplementary-upload channel, no ZIP, and no page cap. One PDF carries everything, and the 2026 CFP draws the line inside that PDF: the abstract, the table of contents, and the first twelve pages are read; material beyond that is read at the committee's discretion (checked 2026-07-08). So "supplementary material" at STOC means the discretionary region of your own submission — and designing it is a first-class writing task, because reviewers enter it selectively, through the pointers you leave.
The table of contents is part of the supplement's interface
Uniquely among major venues, STOC names the ToC as guaranteed-read material. Treat it as the map reviewers use to decide which discretionary pages to open:
\tableofcontents % after the abstract, before Section 1
% Section titles should narrate the argument, not label boilerplate:
% 4 Reducing multi-commodity routing to tree embeddings
% 5 The potential-function analysis (proof of Theorem 1.2)
% A Deferred proofs from Section 4
% B The lower-bound construction (proof of Theorem 1.4)
% C Extension to weighted instancesA ToC whose appendix entries name the theorem each section proves lets a reviewer verify exactly the claim they doubt. "Appendix A: Omitted proofs" is a map with no street names.
Placement decision table
| Content | First 12 pages | Discretionary appendix | Full version only |
|---|---|---|---|
| Every theorem/corollary statement | Required | Restated with proof | Mirror |
| Technical overview of the main proof | Required | — | Mirror |
| Complete proof of the main theorem | Idea + hardest step | Yes, in full | Yes |
| Routine lemma proofs | No | Yes | Yes |
| Secondary results and extensions | One-sentence pointers | Statements + proofs | Yes |
| Long definitions/preliminaries variants | Compressed | Full generality | Full generality |
| Illustration figures, search procedures | No | Brief procedure note | Complete detail |
| Anything the paper's acceptance depends on | Must be at least stated here | Cannot live only here | Cannot live only here |
The invariant behind every row: a committee member who stops at page twelve must still be able to state your contribution correctly and believe it is probably true; a reviewer who continues must find every belief redeemable.
Pointer discipline
Deferred proofs are only as good as their forward and backward links:
- At each in-body statement:
\emph{Proof in Appendix~\ref{app:lb}.}— one pointer, exact target, never "proofs appear in the appendix" globally. - At each appendix proof: restate the theorem before proving it (the
thmtools/\restatablemechanism keeps restatements literally identical), so the discretionary reader does not page-flip to reconstruct the claim. - Order appendix sections by the body's order of claims, not by proof dependency; a reviewer chasing Theorem 1.4 should not wade through the machinery of Theorem 1.2 to find it.
- Give the appendix its own two-or-three-sentence opening paragraph stating dependency structure ("Appendix B is self-contained; Appendix C uses Lemma A.3").
What the appendix is not for
- Not an overflow valve for a bloated body. Twelve pages that read like a compressed twenty signal that the writing pass never happened; cutting secondary material entirely (into the full version) usually beats squeezing everything in.
- Not a second paper. Extensions that would each need their own referee ("we also resolve the directed case") dilute the committee's confidence budget; state one, defer the rest to the full version, or split the work.
- Not a hiding place. Burying a known limitation on page 47 while the body implies generality is the kind of asymmetry that turns a positive review negative when discovered — and assigned theory reviewers do discover it.
Show full SKILL.md (276 more words)Show less
Appendix smells and their repairs
- The monolith: one 30-page "Appendix A: Proofs" with no internal structure. Repair: one appendix section per body section or per major theorem, each named for what it proves.
- The dependency maze: Appendix C's lemma silently requires Appendix B's notation established twenty pages earlier. Repair: per-section dependency sentences and local notation reminders at first reuse.
- The duplicate drift: the appendix restatement of Theorem 1.2 differs by
one quantifier from the body statement. Repair:
\restatableor shared statement files — never retype (stoc-reproducibility). - The dangling pointer: the body promises "Appendix D" and the appendix
ends at C. Repair: a pre-upload pass compiling with
\refcheckor grepping everyAppendix~\reftarget. - The kitchen sink: half-finished generalizations kept "for completeness." Repair: cut to the full version; the submission appendix is a verification surface, not a notebook.
Relationship to the full version
The submission appendix and the eventual arXiv/ECCC full version usually share
sources but serve different masters: the appendix is optimized for selective
verification during review; the full version for linear reading forever.
Before camera-ready, the full version typically re-expands what the appendix
compressed, restores the general statements, and becomes the canonical document
(stoc-camera-ready and stoc-reproducibility handle that transition and its
drift risks). During review, though, the single submitted PDF must stand alone:
STOC 2026 was double-blind, and a reviewer following an external link to your
named preprint is an anonymity event you caused.
Cycle-volatility warnings
- The guaranteed-read wording (abstract + ToC + 12 pages) is 2026 CFP text; earlier cycles used a 10-page window, so re-read the live CFP each fall before budgeting pages (待核实 per cycle).
- Font/margin specifics (11-point, 1-inch, letter) are also restated annually.
Output format
[Appendix architecture] navigable / needs restructuring
[ToC audit] narrates argument / boilerplate labels <- rewrite
[Placement violations] <decision-critical content outside guaranteed pages>
[Pointer check] statement->proof links complete? restatements identical?
[Deferral plan] <what moves to full version entirely>© 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 STOC-Skills/skills/stoc-supplementary of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Stoc Supplementary 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 |
|---|---|---|---|---|---|---|
| Stoc Supplementary this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.7k | Automated safety check: Pass | MIT | |
| Read arXiv Paperkarpathy/nanochat | 59k | 1 repos | ~494 | Automated safety check: Pass | MIT | |
| Literature Reviewneflibata-feng/MyArxiv-Agent | 126 | 20 repos | ~5.9k | Automated safety check: Notes | MIT | |
| Openalex Databaseneflibata-feng/MyArxiv-Agent | 126 | 12 repos | ~3k | Automated safety check: Pass | Custom licence | |
| Citation ManagementK-Dense-AI/claude-scientific-writer | 2.4k | 2 repos | ~3.9k | Automated safety check: Notes | MIT | |
| Citation Managementneflibata-feng/MyArxiv-Agent | 126 | 19 repos | ~8.1k | Automated safety check: Notes | MIT |
Similar skills
Literature Review
neflibata-feng/MyArxiv-Agent
Conduct comprehensive, systematic literature reviews using multiple academic databases (PubMed, arXiv, bioRxiv, Semantic Scholar, etc.).
Openalex Database
neflibata-feng/MyArxiv-Agent
Query and analyze scholarly literature using the OpenAlex database.
Citation Management
K-Dense-AI/claude-scientific-writer
Finds papers in OpenAlex, PubMed and Google Scholar, turns DOIs, PMIDs and arXiv IDs into clean BibTeX, and validates citations for a manuscript or thesis.
Citation Management
neflibata-feng/MyArxiv-Agent
Comprehensive citation management for academic research. An agent skill from neflibata-feng/MyArxiv-Agent.
Systematic Literature Review Builder
bytedance/deer-flow
Searches arXiv across many papers on one topic, extracts each paper's methodology and findings in parallel, and synthesizes a cited literature review.
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
Works with
Categories
Questions about Stoc Supplementary
What does Stoc Supplementary do?
A skill your agent uses when architecting everything beyond the first twelve pages of a STOC (ACM Symposium on Theory of Computing) submission — the discretionary-read appendix, the reviewed table…. Stoc Supplementary is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when architecting everything beyond the first twelve pages of a STOC (ACM Symposium on Theory of Computing) submission — the discretionary-read appendix, the reviewed table of contents, theorem-to-proof pointer discipline, and the division of labor between the submission appendix and the arXiv/ECCC full version.
When should I use Stoc Supplementary?
Stoc Supplementary fits situations like: the reviewed table of contents; theorem-to-proof pointer discipline; the division of labor between the submission appendix and the arXiv/ECCC full version.
How do I install Stoc Supplementary in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill stoc-supplementary -a claude-code`. Or copy the skill folder (STOC-Skills/skills/stoc-supplementary in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/stoc-supplementary in your project. Claude Code loads it when a task matches its description.
How do I install Stoc Supplementary in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill stoc-supplementary -a codex`. Or copy the skill folder (STOC-Skills/skills/stoc-supplementary in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/stoc-supplementary in your project. Codex loads it when a task matches its description.
Can I use Stoc Supplementary 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 stoc-supplementary -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/stoc-supplementary, .gemini/skills/stoc-supplementary, .github/skills/stoc-supplementary and .opencode/skills/stoc-supplementary in your project.
What does Stoc Supplementary need to run?
SKILL.md names no scripts, command-line tools or credentials: Stoc Supplementary is instructions for the agent only.
Does Stoc Supplementary 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 Stoc Supplementary 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 Stoc Supplementary use?
Stoc Supplementary 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 Stoc Supplementary use?
About 1.7k tokens (SKILL.md is roughly 6.6k 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 Stoc Supplementary?
Skills that share tags, products or a category with Stoc Supplementary: Read arXiv Paper (karpathy/nanochat, 59k stars), Literature Review (neflibata-feng/MyArxiv-Agent, 126 stars), Openalex Database (neflibata-feng/MyArxiv-Agent, 126 stars) and Citation Management (K-Dense-AI/claude-scientific-writer, 2.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Stoc Supplementary?
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.