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 converting a FOCS (IEEE Symposium on Foundations of Computer Science) acceptance into its deliverables — the IEEE proceedings version with copyright and de-anonymization…
Install Focs Camera Ready
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill focs-camera-ready -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills focs-camera-ready --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/FOCS-Skills/skills/focs-camera-ready .claude/skills/focs-camera-ready && 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 "focs-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/FOCS-Skills/skills/focs-camera-ready into .claude/skills/focs-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "focs-camera-ready", 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/FOCS-Skills/skills/focs-camera-readyType 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 focs-camera-ready -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills focs-camera-ready --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/FOCS-Skills/skills/focs-camera-ready .agents/skills/focs-camera-ready && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "focs-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/FOCS-Skills/skills/focs-camera-ready into .agents/skills/focs-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "focs-camera-ready", 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 focs-camera-ready -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills focs-camera-ready --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/FOCS-Skills/skills/focs-camera-ready .cursor/skills/focs-camera-ready && 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 "focs-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/FOCS-Skills/skills/focs-camera-ready into .cursor/skills/focs-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "focs-camera-ready", 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 FOCS-Skills/skills/focs-camera-ready--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 focs-camera-ready -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills focs-camera-ready --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/FOCS-Skills/skills/focs-camera-ready .gemini/skills/focs-camera-ready && 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 "focs-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/FOCS-Skills/skills/focs-camera-ready into .gemini/skills/focs-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "focs-camera-ready", 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 focs-camera-readyInstalls 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 focs-camera-ready -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/FOCS-Skills/skills/focs-camera-ready .github/skills/focs-camera-ready && 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 "focs-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/FOCS-Skills/skills/focs-camera-ready into .github/skills/focs-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "focs-camera-ready", 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 focs-camera-ready -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 focs-camera-ready --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/FOCS-Skills/skills/focs-camera-ready .opencode/skills/focs-camera-ready && 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 "focs-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/FOCS-Skills/skills/focs-camera-ready into .opencode/skills/focs-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "focs-camera-ready", 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
focs-camera-ready- GitHub stars
- 1.2k
- Token cost
- ~1.5k tokens
- SKILL.md length
- 733 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when converting a FOCS (IEEE Symposium on Foundations of Computer Science) acceptance into its deliverables — the IEEE proceedings version with copyright and de-anonymization…
- Works in 5 steps: Acceptance week: read the packet twice;… → Week 1: apply reviewer-prompted fixes to… → Week 2: de-anonymization pass;… → …
- The public arXiv/ECCC full version the CFP expects
- SKILL.md covers The two deliverables, De-anonymization, done…, Consistency audit before the… and The November talk and the…, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Focs Camera Ready is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when converting a FOCS (IEEE Symposium on Foundations of Computer Science) acceptance into its deliverables — the IEEE proceedings version with copyright and de-anonymization steps, the public arXiv/ECCC full version the CFP expects, the New York talk, and award-eligibility hygiene.
Its SKILL.md is about 1.5k 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 public arXiv/ECCC full version the CFP expects
- The New York talk
- Award-eligibility hygiene
Example prompts
- “/focs-camera-ready”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Acceptance week: read the packet twice; diary the camera-ready date;
- Week 1: apply reviewer-prompted fixes to the canonical source; regenerate
- Week 2: de-anonymization pass; funder-compliance check; consistency audit
- Submission: upload proceedings files; post/refresh the full version so
- Before travel: talk rehearsed against a mixed-TCS audience; slides carry
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 bash).
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
Focs Camera Ready loads about 1.5k tokens when it runs. Until then it costs about 76 tokens; SKILL.md has 733 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). 733 words, ~1,491 tokens.
Download SKILL.mdSave it as
.claude/skills/focs-camera-ready/SKILL.md (or your agent's skills folder).- name
- focs-camera-ready
- description
- Use when converting a FOCS (IEEE Symposium on Foundations of Computer Science) acceptance into its deliverables — the IEEE proceedings version with copyright and de-anonymization steps, the public arXiv/ECCC full version the CFP expects, the New York talk, and award-eligibility hygiene.
FOCS Camera-Ready
Acceptance at FOCS creates two publication duties with different owners of truth: a proceedings version, produced to IEEE specifications and published via IEEE Xplore and the IEEE Computer Society Digital Library, and a public full version with complete proofs that the CFP expects on arXiv, ECCC, or an equivalent open host by the camera-ready deadline (2026 CFP, checked 2026-07-08; the 2026 camera-ready date and format instructions were not public at check time — the acceptance packet is the controlling source, 待核实). This skill sequences both.
The two deliverables
| Proceedings version | Public full version | |
|---|---|---|
| Publisher | IEEE (Xplore + CS Digital Library) | You (arXiv / ECCC) |
| Role | Citable record of the FOCS acceptance | Record of correctness — the document experts actually read |
| Length | Per acceptance packet (待核实) | Unlimited; all proofs |
| Rights | IEEE copyright/publication form (electronic; exact form 待核实) | You retain arXiv license choice |
| Deadline | Camera-ready date (待核实) | CFP expectation: same date |
| Failure cost | Paper dropped from proceedings | Community reads a proofless announcement; reputational, and real |
Treat the full version as the primary deliverable and the proceedings file as its formatted excerpt — that ordering produces consistent documents; the reverse ordering produces a proofless PDF and an orphaned preprint.
De-anonymization, done completely
Reversing double-blind is more than restoring the author block:
- Author names, affiliations, emails, ORCIDs in the packet's required format and order (author-order changes after acceptance need chair approval).
- Acknowledgements and grant numbers restored — check funder mandates now, since some require specific contract-number phrasing and open-access handling of the accepted version.
- Self-citations rewritten out of the third person where it now reads absurdly ("Chen et al. [7] — the present authors — showed…" becomes "In earlier work [7] we showed…").
- The "full version" pointer made concrete: replace "the full version" with the actual arXiv/ECCC identifier on the first page.
Consistency audit before the deadline
The one camera-ready failure that follows a theory paper forever is divergence between the proceedings version and the full version. Run the statement-freeze check across the two sources one last time:
# same extractor as focs-reproducibility; both sources, post-edits
./extract_statements.sh proceedings-src/ fullversion-src/
# hashes must match: no theorem statement may differ between the
# document people cite and the document people check
# then verify the cross-pointers resolve:
grep -o 'arXiv:[0-9v.]*' proceedings-src/*.tex # correct ID, correct versionIf reviewer comments prompted real changes (a repaired lemma, a weakened claim), apply them to both documents and record them in the full version's changelog ("v3, camera-ready: Lemma 6.2 hypothesis corrected following committee comments"). Improvements beyond reviewer comments are safe when they strengthen exposition; new results belong in the journal version, not in a camera-ready that no longer matches what was refereed.
Show full SKILL.md (343 more words)Show less
The November talk and the awards file
- Talk: every accepted FOCS paper gets a program slot in New York (November 8–11, 2026); whether the 2026 program runs single-track or parallel sessions was unannounced at check time (待核实). Build the talk from the ten-page window's narrative — problem, obstacle, one real idea — not from the section structure; twenty minutes fits one idea.
- Registration and attendance duties for accepted papers (who must register, in-person requirements): 待核实 in the acceptance packet; budget as if required.
- Awards: the PC designates Best Paper and the Machtey Award for best student paper from the accepted pool — recent Machtey citations (2024: the Ising-perceptron capacity paper; papers with all-student author teams) show the profile. If your author team's student status matters, confirm the packet's eligibility declaration is filled accurately; misdeclared status is unfixable after the program is printed.
Working with IEEE production
Expect the production pipeline of an IEEE Computer Society proceedings —
specific class files, a compliance-checking step, and an electronic
copyright form — with the 2026 specifics (template, page allowance, upload
system) defined only by the acceptance packet (待核实). Two habits that
prevent the classic failures: run the packet's compliance checks on day one
rather than deadline day, because font-embedding and figure-format errors
take iterations to clear; and keep the proceedings source a generated
projection of your canonical source (a documented set of cut points and
\iffull switches), never a hand-forked copy — hand forks are how the
proceedings version acquires the typo the full version already fixed.
Endgame sequence
- Acceptance week: read the packet twice; diary the camera-ready date; file the IEEE form early (copyright questions take days, not hours).
- Week 1: apply reviewer-prompted fixes to the canonical source; regenerate both documents from it.
- Week 2: de-anonymization pass; funder-compliance check; consistency audit above; co-author sign-off on the exact PDFs.
- Submission: upload proceedings files; post/refresh the full version so the identifier printed in the proceedings resolves today, not at the conference.
- Before travel: talk rehearsed against a mixed-TCS audience; slides carry the arXiv/ECCC ID on the final frame.
© 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 FOCS-Skills/skills/focs-camera-ready of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Focs Camera Ready 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 |
|---|---|---|---|---|---|---|
| Focs Camera Ready this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.5k | 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 Focs Camera Ready
What does Focs Camera Ready do?
A skill your agent uses when converting a FOCS (IEEE Symposium on Foundations of Computer Science) acceptance into its deliverables — the IEEE proceedings version with copyright and de-anonymization…. Focs Camera Ready is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when converting a FOCS (IEEE Symposium on Foundations of Computer Science) acceptance into its deliverables — the IEEE proceedings version with copyright and de-anonymization steps, the public arXiv/ECCC full version the CFP expects, the New York talk, and award-eligibility hygiene.
When should I use Focs Camera Ready?
Focs Camera Ready fits situations like: the public arXiv/ECCC full version the CFP expects; the New York talk; award-eligibility hygiene.
How do I install Focs Camera Ready in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill focs-camera-ready -a claude-code`. Or copy the skill folder (FOCS-Skills/skills/focs-camera-ready in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/focs-camera-ready in your project. Claude Code loads it when a task matches its description.
How do I install Focs Camera Ready in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill focs-camera-ready -a codex`. Or copy the skill folder (FOCS-Skills/skills/focs-camera-ready in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/focs-camera-ready in your project. Codex loads it when a task matches its description.
Can I use Focs Camera Ready 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 focs-camera-ready -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/focs-camera-ready, .gemini/skills/focs-camera-ready, .github/skills/focs-camera-ready and .opencode/skills/focs-camera-ready in your project.
What does Focs Camera Ready need to run?
SKILL.md names no scripts, command-line tools or credentials: Focs Camera Ready is instructions for the agent only.
Does Focs Camera Ready 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 Focs Camera Ready 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 Focs Camera Ready use?
Focs Camera Ready 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 Focs Camera Ready use?
About 1.5k tokens (SKILL.md is roughly 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 Focs Camera Ready?
Skills that share tags, products or a category with Focs Camera Ready: 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 Focs Camera Ready?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,228 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.