Markitdown
ImCa0/just-laws
Convert files and office documents to Markdown. An agent skill from ImCa0/just-laws.
A skill your agent uses when an ACM CHI paper receives a revise-and-resubmit invitation and the five-week window opens — planning the revision triage, making tracked changes reviewers can audit, and…
Install Chi Author Response
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill chi-author-response -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills chi-author-response --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-author-response .claude/skills/chi-author-response && 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-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CHI-Skills/skills/chi-author-response into .claude/skills/chi-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "chi-author-response", 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-author-responseType 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-author-response -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills chi-author-response --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-author-response .agents/skills/chi-author-response && 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-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CHI-Skills/skills/chi-author-response into .agents/skills/chi-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "chi-author-response", 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-author-response -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills chi-author-response --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-author-response .cursor/skills/chi-author-response && 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-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CHI-Skills/skills/chi-author-response into .cursor/skills/chi-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "chi-author-response", 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-author-response--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-author-response -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills chi-author-response --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-author-response .gemini/skills/chi-author-response && 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-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CHI-Skills/skills/chi-author-response into .gemini/skills/chi-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "chi-author-response", 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-author-responseInstalls 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-author-response -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-author-response .github/skills/chi-author-response && 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-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CHI-Skills/skills/chi-author-response into .github/skills/chi-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "chi-author-response", 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-author-response -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-author-response --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-author-response .opencode/skills/chi-author-response && 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-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CHI-Skills/skills/chi-author-response into .opencode/skills/chi-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "chi-author-response", 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-author-response- GitHub stars
- 1.2k
- Token cost
- ~1.4k tokens
- SKILL.md length
- 614 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when an ACM CHI paper receives a revise-and-resubmit invitation and the five-week window opens — planning the revision triage, making tracked changes reviewers can audit, and…
- An ACM CHI paper receives a revise-and-resubmit invitation and the five-week window opens — planning the revision triage
- SKILL.md covers The first 48 hours: triage,…, Revising so the diff does the…, The response letter and What you may and may not change, plus 2 more sections
- Calls pdftotext
- Making tracked changes reviewers can audit
What it does
Chi Author Response is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when an ACM CHI paper receives a revise-and-resubmit invitation and the five-week window opens — planning the revision triage, making tracked changes reviewers can audit, and writing the response letter that carries the paper through round 2 and the PC meeting.
Its SKILL.md is about 1.4k 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 Word documents. 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
- An ACM CHI paper receives a revise-and-resubmit invitation and the five-week window opens — planning the revision triage
- Making tracked changes reviewers can audit
- Writing the response letter that carries the paper through round 2 and the PC meeting
Example prompts
- “/chi-author-response”
What it can do on your machine
Read from SKILL.md and the folder at commit 932eb23. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
pdftotext
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Chi Author Response loads about 1.4k tokens when it runs. Until then it costs about 71 tokens; SKILL.md has 614 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). 614 words, ~1,378 tokens.
Download SKILL.mdSave it as
.claude/skills/chi-author-response/SKILL.md (or your agent's skills folder).- name
- chi-author-response
- description
- Use when an ACM CHI paper receives a revise-and-resubmit invitation and the five-week window opens — planning the revision triage, making tracked changes reviewers can audit, and writing the response letter that carries the paper through round 2 and the PC meeting.
CHI Author Response
CHI does not run a short rebuttal where you argue in a text box. An invited paper gets roughly five weeks to deliver two artifacts: a genuinely revised manuscript with changes visibly tracked, and a response letter mapping every reviewer concern to what changed. For CHI 2027 the resubmission deadline is December 3, 2026 (posted on chi2027.acm.org, read 2026-07-08). The stakes are real: the posted process warns up to 50% of revised papers may still be rejected; CHI 2026 accepted 65.5% of resubmissions.
The first 48 hours: triage, not writing
Read all reviews twice, write nothing outward, then sort every distinct criticism:
| Triage class | Test | Response strategy |
|---|---|---|
| Must-fix | Named by the 1AC meta-review or ≥2 reviewers | Change the paper substantively; show the diff |
| Cheap win | Clarity, missing citation, terminology, figure | Fix all of them, every single one |
| Analysis request | Wants a new analysis of existing data | Run it if the pipeline is alive; report honestly either way |
| New-study request | Wants data you cannot collect in five weeks | Do not fake it; scope the claim down instead and say so |
| Misreading | Reviewer misunderstood something actually present | Treat as your writing defect: fix the text, then point to it |
| Genuine disagreement | Legitimate difference of research values | Push back once, respectfully, with evidence and citations |
The meta-review is the priority list. Reviewers at CHI re-read revisions against their own round-1 comments, and the PC meeting discusses the 1AC's summary of how well you responded — not the eloquence of your prose.
Revising so the diff does the arguing
The instructions ask for a revision with tracked changes — highlighted, conventionally in color — plus the response letter. Make the audit trail mechanical:
# LaTeX: generate the tracked-changes PDF from the submitted vs revised source
latexdiff --type=CULINECHASE submitted/main.tex revised/main.tex > diff.tex \
&& latexmk -pdf diff.tex
# Sanity: confirm the revision still respects CHI length norms after additions
texcount -inc -sum revised/main.tex | tail -3
# Keep anonymization intact through round 2 — new text leaks too
pdftotext revised/main.pdf - | grep -nEi 'our (lab|university)|github\.com/[a-z]' | headFive weeks invites over-revision. Do not restructure sections no reviewer questioned, and do not let the word count balloon past what the contribution justifies — length norms still apply at resubmission, and a bloated revision reads as panic.
Show full SKILL.md (298 more words)Show less
The response letter
Structure it per reviewer, with numbered items quoting or precisely paraphrasing each concern, in the reviewers' own order. For each item: what changed, where (section and page in the revised PDF), and — where relevant — one sentence of substance. A workable skeleton:
Response to Reviews — Submission #1234
Summary of changes: <5-8 bullets, the big moves only>
R1.1 "<concern>" → Revised §4.2 (p.7): we now report <what>. <One sentence of
substance or evidence.>
R1.2 "<concern>" → We respectfully keep <choice> because <evidence/citation>,
and now state this rationale explicitly in §3.1.
2AC.1 ...Tone rules that decide borderline cases at the PC meeting:
- Thank reviewers once, globally; do not lard every item with gratitude.
- Never write "the reviewer is wrong." Write what the paper now says and where.
- Concede real limitations plainly and move them into the limitations section — reviewers reward honesty at CHI more reliably than at most venues, because study limitations are expected in human-subjects work.
- If two reviewers conflict, name the conflict neutrally and state which path you took and why, so the 1AC can resolve it rather than rediscover it.
What you may and may not change
The revision is expected to respond to the reviews; it is not a fresh submission. Safe: new analyses of existing data, reframed claims, restructured argument, improved figures, expanded related work, fixed statistics. Risky without flagging: changing the core claims, swapping the method story, adding an entirely new study — if the paper needed those, discuss withdrawing and resubmitting next cycle instead, because the same review team will judge whether the new material was reviewed properly. Author lists and anonymization rules stay as they were (待核实 for edge cases: check the current cycle's instructions before touching authorship).
If you decide not to resubmit
Withdrawing is legitimate — 27 of 2,603 invited CHI 2026 papers did not return. Do it formally in PCS, keep the reviews, and fold them into the next venue's draft while they are fresh. An RR invitation you decline is still market information: the paper was in the top ~39% of a 6,700-paper pool.
Output format
[Window] opens <date> → due 2026-12-03; days remaining: <n>
[Triage] must-fix: <n> / cheap: <n> / analysis: <n> / out-of-scope: <n>
[Meta-review demand] <the 1AC's central ask, one line>
[Riskiest item] <the concern you cannot fully satisfy + chosen strategy>
[Deliverables] tracked-changes PDF ✓/✗ · response letter ✓/✗ · length re-check ✓/✗© 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-author-response of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Chi Author Response 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 Author Response this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.4k | Automated safety check: Pass | MIT | |
| MarkitdownImCa0/just-laws | 781 | 14 repos | ~3.2k | Automated safety check: Notes | MIT | |
| DOCXrvdbreemen/OTGW-firmware | 207 | 33 repos | ~4.3k | Automated safety check: Pass | Proprietary | |
| Word Document Reader and WriterHKUDS/DeepTutor | 41k | — | ~2.5k | Automated safety check: Pass | Apache-2.0 | |
| Gzh Designisjiamu/gzh-design-skill | 4k | — | ~2.2k | Automated safety check: Pass | AGPL-3.0 | |
| GenOffice Document CLIgenspark-ai/genoffice | 9.2k | — | ~19k | Automated safety check: Pass | Apache-2.0 |
Similar skills
DOCX
rvdbreemen/OTGW-firmware
A skill your agent uses whenever the user wants to create, read, edit, or manipulate Word documents (.docx files).
Word Document Reader and Writer
HKUDS/DeepTutor
Reads, creates and edits Word .docx files with python-docx, and drops to raw OOXML for tracked changes, comments and byte-exact edits.
Gzh Design
isjiamu/gzh-design-skill
微信公众号文章排版引擎，将 Markdown 转换为可直接粘贴到公众号编辑器的 HTML。主题风格从 references/theme-index.md 注册的自定义主题库中选取，自动章节编号、关键词下划线标记、引言卡片、目录导航、代码块、图片/GIF、作者签名。支持 Markdown / Word(.docx) / PDF / 纯文本输入（非 Markdown…
GenOffice Document CLI
genspark-ai/genoffice
Creates, converts, reads and edits real pptx, xlsx, docx and PDF files locally through the genoffice command line.
BiSheng DOCX Builder
dataelement/bisheng
Builds or edits Word .docx documents inside BiSheng's code executor with python-docx, handling Chinese fonts, tables of contents, page numbers and official-document layout.
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 Chi Author Response
What does Chi Author Response do?
A skill your agent uses when an ACM CHI paper receives a revise-and-resubmit invitation and the five-week window opens — planning the revision triage, making tracked changes reviewers can audit, and…. Chi Author Response is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when an ACM CHI paper receives a revise-and-resubmit invitation and the five-week window opens — planning the revision triage, making tracked changes reviewers can audit, and writing the response letter that carries the paper through round 2 and the PC meeting.
When should I use Chi Author Response?
Chi Author Response fits situations like: an ACM CHI paper receives a revise-and-resubmit invitation and the five-week window opens — planning the revision triage; making tracked changes reviewers can audit; writing the response letter that carries the paper through round 2 and the PC meeting.
How do I install Chi Author Response in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill chi-author-response -a claude-code`. Or copy the skill folder (CHI-Skills/skills/chi-author-response in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/chi-author-response in your project. Claude Code loads it when a task matches its description.
How do I install Chi Author Response in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill chi-author-response -a codex`. Or copy the skill folder (CHI-Skills/skills/chi-author-response in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/chi-author-response in your project. Codex loads it when a task matches its description.
Can I use Chi Author Response 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-author-response -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-author-response, .gemini/skills/chi-author-response, .github/skills/chi-author-response and .opencode/skills/chi-author-response in your project.
What does Chi Author Response need to run?
Going by SKILL.md and its folder, Chi Author Response needs the command-line tools its instructions call (pdftotext).
Does Chi Author Response 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 Author Response 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 Author Response use?
Chi Author Response 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 Author Response use?
About 1.4k tokens (SKILL.md is roughly 5.5k 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 Author Response?
Skills that share tags, products or a category with Chi Author Response: Markitdown (ImCa0/just-laws, 781 stars), DOCX (rvdbreemen/OTGW-firmware, 207 stars), Word Document Reader and Writer (HKUDS/DeepTutor, 41k stars) and Gzh Design (isjiamu/gzh-design-skill, 4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Chi Author Response?
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.