focs-author-response
Use when managing author-side communication around a FOCS (IEEE Symposium on Foundations of Computer Science) submission, where no rebuttal round exists — discharging objections inside the paper before submission, handling rare chair-mediated queries, and converting a rejection into a disciplined autumn resubmission.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill focs-author-response --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# FOCS Author Response The FOCS 2026 CFP schedules no rebuttal, no discussion phase, and no author-visible reviews before decisions (checked 2026-07-08; any informal PC-initiated clarification in a given cycle: 待核实). At a venue with no second turn, "author response" is a set of practices displaced in time: persuasion happens *before* the deadline, correction happens *after* the decision, and almost nothing happens in between. This skill covers all three phases. ## Phase 1 — the pre-emptive rebuttal (before submission) Write the objections you would rebut, then edit the paper until each is answered where it would arise. Build the table with a co-author playing antagonist: | Anticipated objection | Where discharged | Device | |---|---|---| | "Isn't this implied by [强 result]?" | Intro, directly after the theorem | One paragraph: why the known result does not give yours (regime, model, quantifier order) | | "The improvement is small" | Obstacle paragraph | Show the barrier the small step crosses (`focs-writing-style`) | | "Lemma 5.3 looks fragile" | Overview §3 + full proof | Flag it yourself: "the delicate step is…", then prove it twice as carefully | | "Why isn't this just [techniqu
- Phase 1 — the pre-emptive rebuttal (before submission)
- Phase 2 — during review (April to notification)
- Phase 3 — after the decision
- A memo entry, worked
- Deciding between the autumn options
- Tone calibration for all phases
What does the focs-author-response skill do?
Use when managing author-side communication around a FOCS (IEEE Symposium on Foundations of Computer Science) submission, where no rebuttal round exists — discharging objections inside the paper before submission, handling rare chair-mediated queries, and converting a rejection into a disciplined autumn resubmission.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill focs-author-response --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From brycewang-stanford/Awesome-Journal-Skills, a repository with 984 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.