Paper Audit
brycewang-stanford/Auto-Empirical-Research-Skills
Deep-review-first audit for Chinese and English academic papers across LaTeX, Typst, and PDF formats.
A skill your agent uses when auditing an ACM CHI Papers submission for PCS readiness, covering the September full-paper deadline, the anonymized single-column template, word-count norms instead of…
MITAuto-check passed
Install Chi Submission
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill chi-submission -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills chi-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/CHI-Skills/skills/chi-submission .claude/skills/chi-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 "chi-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CHI-Skills/skills/chi-submission into .claude/skills/chi-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "chi-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/CHI-Skills/skills/chi-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 chi-submission -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills chi-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/CHI-Skills/skills/chi-submission .agents/skills/chi-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 "chi-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CHI-Skills/skills/chi-submission into .agents/skills/chi-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "chi-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 chi-submission -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills chi-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/CHI-Skills/skills/chi-submission .cursor/skills/chi-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 "chi-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CHI-Skills/skills/chi-submission into .cursor/skills/chi-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "chi-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 CHI-Skills/skills/chi-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 chi-submission -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills chi-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/CHI-Skills/skills/chi-submission .gemini/skills/chi-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 "chi-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CHI-Skills/skills/chi-submission into .gemini/skills/chi-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "chi-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 chi-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 chi-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/CHI-Skills/skills/chi-submission .github/skills/chi-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 "chi-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CHI-Skills/skills/chi-submission into .github/skills/chi-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "chi-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 chi-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 chi-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/CHI-Skills/skills/chi-submission .opencode/skills/chi-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 "chi-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CHI-Skills/skills/chi-submission into .opencode/skills/chi-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "chi-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
chi-submission- GitHub stars
- 1.2k
- Token cost
- ~1.5k tokens
- SKILL.md length
- 705 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 ACM CHI Papers submission for PCS readiness, covering the September full-paper deadline, the anonymized single-column template, word-count norms instead of…
- Works in 6 steps: Lock the subcommittee pair first; it… → Freeze the manuscript at a defensible… → Render and caption the video figure… → …
- Auditing an ACM CHI Papers submission for PCS readiness
- SKILL.md covers What the CHI 2027 cycle posted, The anonymization trap…, Desk-reject triage, CHI edition and Deadline-week order of…, plus 3 more sections
- Calls pdftotext and ffprobe
What it does
Chi Submission is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when auditing an ACM CHI Papers submission for PCS readiness, covering the September full-paper deadline, the anonymized single-column template, word-count norms instead of page limits, subcommittee designation, supplementary and video upload, anonymization of external links, and CHI's desk-reject triage before upload.
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.
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 ACM CHI Papers submission for PCS readiness
- Covering the September full-paper deadline
- The anonymized single-column template
- Word-count norms instead of page limits
Example prompts
- “/chi-submission”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Lock the subcommittee pair first; it determines who reads everything else.
- Freeze the manuscript at a defensible word count and record the texcount output.
- Render and caption the video figure early — encoding and captioning always take
- Assemble supplements from a clean export, then run the mechanical sweep above on the
- Fill every PCS field (title, abstract, authors, subcommittees, contribution
- Re-download the submitted package and open it cold, the way a 1AC will.
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:
pdftotextffprobe
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
Chi Submission loads about 1.5k tokens when it runs. Until then it costs about 85 tokens; SKILL.md has 705 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). 705 words, ~1,524 tokens.
Download SKILL.mdSave it as
.claude/skills/chi-submission/SKILL.md (or your agent's skills folder).- name
- chi-submission
- description
- Use when auditing an ACM CHI Papers submission for PCS readiness, covering the September full-paper deadline, the anonymized single-column template, word-count norms instead of page limits, subcommittee designation, supplementary and video upload, anonymization of external links, and CHI's desk-reject triage before upload.
CHI Submission
Run this audit before uploading to PCS (Precision Conference Solutions) — CHI does not
use OpenReview or CMT. Every date and cap below was read from the CHI 2027 Papers pages
on 2026-07-08 through search-engine renderings (direct fetches of chi2027.acm.org
were blocked in the verification environment); reopen the live pages before acting on
any number.
What the CHI 2027 cycle posted
- Full Papers deadline: Thursday, September 10, 2026, on PCS, including videos and supplementary materials — CHI collects everything on one date, unlike venues with a later supplement window. No separate abstract-registration deadline was found for 2027; confirm on the live page rather than assuming (待核实).
- Review format: the single-column ACM submission template (CHI has used single-column reviewing since 2021). The two-column look happens later, in TAPS.
- Length is governed by words, not pages. The posted norm: roughly 5,000–8,000 words for a typical paper (excluding references), submissions at or above 12,000 words face extra scrutiny and desk rejection when the length is not justified, and papers of about 5,000 words or fewer are welcomed as short papers reviewed with expectations commensurate with their size. CHI's standing phrase is that a paper should be the length appropriate to its contribution.
- The submission form requires you to designate a reviewing subcommittee (up to two
choices) — a strategic decision, not paperwork; see
chi-topic-selection. - Anonymization is mandatory and extends beyond the PDF: supplemental materials and external links to datasets or code repositories that reveal identity are posted desk-reject grounds.
The anonymization trap specific to CHI
CHI's policy is anonymized review of an HCI paper, which creates leak channels that ML venues rarely have: consent-form headers naming the lab, screenshots of a deployed system showing a university logo, video figures with a narrator saying "at our institution," OSF or GitHub links registered to a named account, and app-store pages for the studied prototype. Cite your own prior studies in the third person and keep the citation; scrub everything else.
# Mechanical pre-upload sweep on the PCS package
pdfinfo paper.pdf | grep -Ei 'author|creator|producer' # PDF metadata identity
pdftotext paper.pdf - | grep -nEi 'github|osf\.io|our (lab|university|institution)' | head
texcount -inc -sum main.tex | tail -3 # word count vs the norms
ffprobe -v error -show_entries format=duration,size video-figure.mp4 # video sanity
unzip -l supplement.zip | grep -Ei 'consent|irb|ethics|\.git/' | head # named formsTreat consent forms and ethics-approval letters as the highest-risk files: they carry institution names by design, so upload templated, de-identified versions.
Desk-reject triage, CHI edition
CHI 2026 formalized an assisted desk reject step run jointly by subcommittee chairs and ACs, with expanded criteria — desk screening is now a real stage, not a formality.
| Finding at audit time | CHI severity | Realistic fix |
|---|---|---|
| Wrong template or altered format | Desk reject | Recompile on the current ACM single-column class |
| Identity leak in PDF, supplement, or link | Desk reject | De-identify; replace links with anonymized archives |
| ~12,000+ words without justification | Desk reject risk | Cut or explicitly justify length in the submission |
| No plausible HCI contribution for any subcommittee | Desk reject at SC/PC screening | Re-frame or re-route before the deadline |
| Video figure missing captions | Review-stage damage | Add a .srt/.sbv file (see chi-supplementary) |
| Weak subcommittee match | Quiet mis-review | Change the designation, not the paper, if the work is sound |
Show full SKILL.md (230 more words)Show less
Deadline-week order of operations
- Lock the subcommittee pair first; it determines who reads everything else.
- Freeze the manuscript at a defensible word count and record the
texcountoutput. - Render and caption the video figure early — encoding and captioning always take longer than the writing team budgets.
- Assemble supplements from a clean export, then run the mechanical sweep above on the exact files going into PCS.
- Fill every PCS field (title, abstract, authors, subcommittees, contribution statement fields if asked) a day before; PCS has no post-deadline mercy.
- Re-download the submitted package and open it cold, the way a 1AC will.
Length is an argument, not a quota
Because CHI reviews words against contribution, padding is a visible defect: a 9,500 word paper whose study supports 7,000 words of claims reads as inflated, and reviewers say so. Cut the third restatement of the findings, move instrument details to the supplement, and keep the method section exactly as long as replication requires — no longer.
Cycle-volatile items — reverify every year
- The September date, the no-abstract-deadline reading, and all word-count wording.
- Subcommittee list and count for the live cycle (the 2026 list is posted on chi2026.acm.org; the 2027 list was not yet published at check time — 待核实).
- Desk-reject criteria wording, which changed as recently as August 2025.
- Whether PCS asks new form questions (AI-use disclosure, data-availability fields).
Output format
[CHI submission status] ready / blocked / needs work
[Word count] <n> words vs posted norms; justification needed? yes/no
[Subcommittees] first: <name> / second: <name or none>
[Anonymity sweep] clean / leaks: <pdf | supplement | links | video | forms>
[Desk-reject exposure] <highest-risk item>
[Fix queue] <ordered actions before September upload>© 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 CHI-Skills/skills/chi-submission of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Chi 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 |
|---|---|---|---|---|---|---|
| Chi Submission this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.5k | Automated safety check: Pass | MIT | |
| Paper Auditbrycewang-stanford/Auto-Empirical-Research-Skills | 4.6k | — | ~3.6k | Automated safety check: Pass | Custom licence | |
| Paper Claim Auditwanshuiyin/Auto-claude-code-research-in-sleep | 17k | 1 repos | ~3.5k | Automated safety check: Notes | MIT | |
| Iso27001 Audit Prepalirezarezvani/claude-skills | 28k | — | ~1.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 |
Similar skills
Paper Claim Audit
wanshuiyin/Auto-claude-code-research-in-sleep
Zero-context verification that every number, comparison, and scope claim in the paper matches raw result files.
Iso27001 Audit Prep
alirezarezvani/claude-skills
/cs:iso27001-audit-prep <scope — ISO 27001 ISMS audit readiness 6-question forcing interrogation.
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.
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 Chi Submission
What does Chi Submission do?
A skill your agent uses when auditing an ACM CHI Papers submission for PCS readiness, covering the September full-paper deadline, the anonymized single-column template, word-count norms instead of…. Chi Submission is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when auditing an ACM CHI Papers submission for PCS readiness, covering the September full-paper deadline, the anonymized single-column template, word-count norms instead of page limits, subcommittee designation, supplementary and video upload, anonymization of external links, and CHI's desk-reject triage before upload.
When should I use Chi Submission?
Chi Submission fits situations like: auditing an ACM CHI Papers submission for PCS readiness; covering the September full-paper deadline; the anonymized single-column template; word-count norms instead of page limits.
How do I install Chi Submission in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill chi-submission -a claude-code`. Or copy the skill folder (CHI-Skills/skills/chi-submission in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/chi-submission in your project. Claude Code loads it when a task matches its description.
How do I install Chi Submission in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill chi-submission -a codex`. Or copy the skill folder (CHI-Skills/skills/chi-submission in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/chi-submission in your project. Codex loads it when a task matches its description.
Can I use Chi 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 chi-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/chi-submission, .gemini/skills/chi-submission, .github/skills/chi-submission and .opencode/skills/chi-submission in your project.
What does Chi Submission need to run?
Going by SKILL.md and its folder, Chi Submission needs the command-line tools its instructions call (pdftotext and ffprobe).
Does Chi 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 Chi 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 Chi Submission use?
Chi 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 Chi Submission use?
About 1.5k tokens (SKILL.md is roughly 6.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 Chi Submission?
Skills that share tags, products or a category with Chi Submission: Paper Audit (brycewang-stanford/Auto-Empirical-Research-Skills, 4.6k stars), Paper Claim Audit (wanshuiyin/Auto-claude-code-research-in-sleep, 17k stars), Iso27001 Audit Prep (alirezarezvani/claude-skills, 28k stars) and Production Audit (affaan-m/ECC, 277k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Chi 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.