Paper Interpretation
digoal/blog
从论文 PDF 文件或论文 PDF URL 生成通俗易懂、图文并茂、带批判性评估的中文 Markdown 解读，并保存到当前项目的 markdown 目录。Use when the user asks to interpret,精读,解读,summarize,explain,analyze, or write an article from an academic paper PDF…
A skill your agent uses when running the final pre-upload audit of a FOCS (IEEE Symposium on Foundations of Computer Science) submission — the April HotCRP deadline clock, the…
Install Focs Submission
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill focs-submission -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills focs-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/FOCS-Skills/skills/focs-submission .claude/skills/focs-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 "focs-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/FOCS-Skills/skills/focs-submission into .claude/skills/focs-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "focs-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/FOCS-Skills/skills/focs-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 focs-submission -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills focs-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/FOCS-Skills/skills/focs-submission .agents/skills/focs-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 "focs-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/FOCS-Skills/skills/focs-submission into .agents/skills/focs-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "focs-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 focs-submission -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills focs-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/FOCS-Skills/skills/focs-submission .cursor/skills/focs-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 "focs-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/FOCS-Skills/skills/focs-submission into .cursor/skills/focs-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "focs-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 FOCS-Skills/skills/focs-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 focs-submission -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills focs-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/FOCS-Skills/skills/focs-submission .gemini/skills/focs-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 "focs-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/FOCS-Skills/skills/focs-submission into .gemini/skills/focs-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "focs-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 focs-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 focs-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/FOCS-Skills/skills/focs-submission .github/skills/focs-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 "focs-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/FOCS-Skills/skills/focs-submission into .github/skills/focs-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "focs-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 focs-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 focs-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/FOCS-Skills/skills/focs-submission .opencode/skills/focs-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 "focs-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/FOCS-Skills/skills/focs-submission into .opencode/skills/focs-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "focs-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
focs-submission- GitHub stars
- 1.2k
- Token cost
- ~1.5k tokens
- SKILL.md length
- 628 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when running the final pre-upload audit of a FOCS (IEEE Symposium on Foundations of Computer Science) submission — the April HotCRP deadline clock, the…
- Works in 5 steps: T-7 days — content freeze. No new… → T-5 days — window audit. Confirm every… → T-3 days — first upload. HotCRP allows… → …
- The abstract-references-plus-ten-pages attention rule
- SKILL.md covers What the 2026 CFP actually…, Mechanical pre-flight, Deadline-week sequence and HotCRP metadata is part of the…, plus 2 more sections
- Calls qpdf
What it does
Focs Submission is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when running the final pre-upload audit of a FOCS (IEEE Symposium on Foundations of Computer Science) submission — the April HotCRP deadline clock, the abstract-references-plus-ten-pages attention rule, the 11-point single-column format floor, PDF security restrictions, double-blind checks, and SIGACT publication-policy compliance.
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 Documents & Office, covering PDF. 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 abstract-references-plus-ten-pages attention rule
- The 11-point single-column format floor
- PDF security restrictions
- Double-blind checks
Example prompts
- “/focs-submission”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- T-7 days — content freeze. No new theorems. Anything proved this week
- T-5 days — window audit. Confirm every result is stated by page ten and
- T-3 days — first upload. HotCRP allows re-uploads until the deadline;
- T-1 day — blind and format pass using the commands above, on the
- Deadline day — clock arithmetic. 5 PM EDT is late evening in Europe and
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:
qpdf
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 Submission loads about 1.5k tokens when it runs. Until then it costs about 88 tokens; SKILL.md has 628 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). 628 words, ~1,462 tokens.
Download SKILL.mdSave it as
.claude/skills/focs-submission/SKILL.md (or your agent's skills folder).- name
- focs-submission
- description
- Use when running the final pre-upload audit of a FOCS (IEEE Symposium on Foundations of Computer Science) submission — the April HotCRP deadline clock, the abstract-references-plus-ten-pages attention rule, the 11-point single-column format floor, PDF security restrictions, double-blind checks, and SIGACT publication-policy compliance.
FOCS Submission
Anchor cycle: FOCS 2026 (67th edition), submissions due Wednesday, April 1,
2026, 5:00 PM EDT — a US-Eastern wall clock equal to 21:00 UTC, not an
anywhere-on-earth deadline — via focs26.hotcrp.com (CFP checked 2026-07-08;
that deadline has passed, so this audit now serves the next cycle: reopen the
live CFP before trusting any number here).
What the 2026 CFP actually required
| Requirement | 2026 wording (verify per cycle) |
|---|---|
| Length | No bound; full version encouraged as the submission |
| Attention rule | Abstract + references + first ten pages guaranteed; the rest at the committee's discretion |
| Typography | 11-point or larger font, single column, single-spaced with ample spacing, ≥1-inch margins, letter-size paper |
| File | PDF without security restrictions on copying or printing |
| Anonymity | Double-blind: no names/affiliations/emails, third-person self-references, acknowledgements omitted |
| Publication policy | SIGACT rules: nothing published or scheduled before the conference month elsewhere; no simultaneous proceedings/journal submission |
| Exceptions | Prior appearance in a venue with significantly different format/content/audience: contact the program chair before submitting |
Note the guaranteed-read set: FOCS names the references as always-read
material alongside the ten pages. Your bibliography is a reviewed object —
stale, sloppy, or misattributed citations are visible even to the laziest
reading (see focs-related-work).
Mechanical pre-flight
Run these on the exact PDF you will upload, not on a draft:
# Page geometry and count of the guaranteed window
pdfinfo submission.pdf | grep -E 'Pages|Page size' # letter = 612 x 792 pts
# FOCS-specific: the CFP forbids copy/print security restrictions
qpdf --show-encryption submission.pdf # want: "File is not encrypted"
# Identity leakage in embedded metadata
exiftool submission.pdf | grep -iE 'author|creator|company'
# Self-reference sweep in the source
grep -rn --include='*.tex' -iE '\b(we|our) (recent|previous|earlier|prior)\b|acknowledg|thank' .The encryption check is easy to fail accidentally: some institutional PDF tooling and some print-to-PDF drivers stamp permission flags by default, and a restricted PDF violates the letter of the CFP.
Deadline-week sequence
- T-7 days — content freeze. No new theorems. Anything proved this week goes to the arXiv version later, not into the submission.
- T-5 days — window audit. Confirm every result is stated by page ten and the technical overview reflects the proofs as they now exist.
- T-3 days — first upload. HotCRP allows re-uploads until the deadline; an early upload converts a hard cliff into a soft one. Fill conflicts, topics, and co-author records now — PC conflict data affects assignment quality directly.
- T-1 day — blind and format pass using the commands above, on the compiled final PDF.
- Deadline day — clock arithmetic. 5 PM EDT is late evening in Europe and early morning in Asia; compute your local equivalent once, write it down, and stop trusting mental arithmetic under stress.
Show full SKILL.md (259 more words)Show less
HotCRP metadata is part of the submission
Theory authors treat the web form as an afterthought; the committee's machinery does not. Three fields shape your paper's fate before anyone reads a word:
- Topics. Assignment starts from your topic selections. Choosing only your micro-area starves the paper of breadth readers; choosing everything looks unserious. Pick the two or three areas whose reviewers you would actually want in the room.
- Conflicts. Declare advisors, recent co-authors, and current-institution colleagues per the form's definitions. Under-declared conflicts discovered later can void a review cycle; over-declared conflicts (tagging everyone senior in the area) can be read as reviewer-shopping.
- Author records. Complete them accurately even though the PDF is blind — the system uses them for conflict resolution, and errors are painful to repair after decisions.
Policy traps specific to this venue
- The IEEE/SIGACT seam. FOCS is an IEEE Computer Society (TCMF) event that enforces ACM SIGACT's publication policy. Authors who read only IEEE's generic submission rules miss the simultaneous-submission bar entirely.
- arXiv is safe, proceedings are not. Posting the full version to arXiv or ECCC before submitting is normal community practice and does not violate the prior-publication rule; a workshop with published proceedings does.
- The invited-journal overlap. If a journal version of a companion result is already in press with overlapping material, disclose to the chair before the deadline rather than hoping the overlap goes unnoticed.
Readiness verdict
[FOCS submission audit]
Window : all theorems stated by p.10 PASS/FAIL
Format : 11pt+/single-column/1in/letter PASS/FAIL
PDF : unencrypted, metadata clean PASS/FAIL
Blind : third-person self-refs, no acks PASS/FAIL
Policy : no simultaneous/prior publication PASS/FAIL
HotCRP : conflicts, topics, authors complete PASS/FAIL
Verdict : UPLOAD / FIX(ordered list) / CONSULT CHAIRAny FAIL in the first three rows is fixable in hours; a policy FAIL is not fixable at all after upload — resolve those with the program chair first.
© 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-submission of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Focs 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 |
|---|---|---|---|---|---|---|
| Focs Submission this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.5k | Automated safety check: Pass | MIT | |
| Paper Interpretationdigoal/blog | 8.6k | — | ~1.5k | Automated safety check: Pass | GPL-2.0 | |
| Paper LensYSQ-boop/paper-lens | 101 | — | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| Paper ReviewRapidAI/MaClaw | 148 | — | ~1k | Automated safety check: Pass | MIT | |
| Ma Fulltext Managementhtlin222/meta-pipe | 139 | — | ~1.7k | Automated safety check: Notes | Custom licence | |
| Paper Interpreterchujianyun/skills | 742 | — | ~810 | Automated safety check: Pass | Custom licence |
Similar skills
Paper Lens
YSQ-boop/paper-lens
Read and critically analyze one academic paper from an arXiv URL/ID or a local PDF, producing a source-grounded Markdown report that can grow from a quick read into a reviewer-level deep review.
Paper Review
RapidAI/MaClaw
论文深度解读 Skill — 下载论文PDF → LLM深度解读（问题/创新点/方法原理/实验分析）→ PDF图片提取 → 生成组会PPT → 生成解读音频MP3。端到端学术论文解读工具。
Ma Fulltext Management
htlin222/meta-pipe
Collect and manage full-text PDFs for included studies, track provenance, and prepare documents for extraction.
Paper Interpreter
chujianyun/skills
论文解读助手。适用于用户发送 arXiv 论文链接，并希望下载论文、解读论文、生成读书笔记、做论文拆解或输出详细报告时使用。会在工作目录创建论文文件夹、下载 PDF 与 TeX Source（如有）、生成中文 Markdown 报告。默认先交付初稿，不自动复查；如果用户明确同意，再安排后续复查。不适用于只要简短推荐语的情况。
Mindmap Render
ai4s-research/ai4s-skills
Generate beautiful, high-resolution mindmaps from Markdown unordered lists.
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 Focs Submission
What does Focs Submission do?
A skill your agent uses when running the final pre-upload audit of a FOCS (IEEE Symposium on Foundations of Computer Science) submission — the April HotCRP deadline clock, the…. Focs Submission is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when running the final pre-upload audit of a FOCS (IEEE Symposium on Foundations of Computer Science) submission — the April HotCRP deadline clock, the abstract-references-plus-ten-pages attention rule, the 11-point single-column format floor, PDF security restrictions, double-blind checks, and SIGACT publication-policy compliance.
When should I use Focs Submission?
Focs Submission fits situations like: the abstract-references-plus-ten-pages attention rule; the 11-point single-column format floor; PDF security restrictions; double-blind checks.
How do I install Focs Submission in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill focs-submission -a claude-code`. Or copy the skill folder (FOCS-Skills/skills/focs-submission in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/focs-submission in your project. Claude Code loads it when a task matches its description.
How do I install Focs Submission in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill focs-submission -a codex`. Or copy the skill folder (FOCS-Skills/skills/focs-submission in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/focs-submission in your project. Codex loads it when a task matches its description.
Can I use Focs 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 focs-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/focs-submission, .gemini/skills/focs-submission, .github/skills/focs-submission and .opencode/skills/focs-submission in your project.
What does Focs Submission need to run?
Going by SKILL.md and its folder, Focs Submission needs the command-line tools its instructions call (qpdf).
Does Focs 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 Focs 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 Focs Submission use?
Focs 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 Focs Submission use?
About 1.5k tokens (SKILL.md is roughly 5.8k 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 Submission?
Skills that share tags, products or a category with Focs Submission: Paper Interpretation (digoal/blog, 8.6k stars), Paper Lens (YSQ-boop/paper-lens, 101 stars), Paper Review (RapidAI/MaClaw, 148 stars) and Ma Fulltext Management (htlin222/meta-pipe, 139 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Focs 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.