sensys-author-response
Use when writing a SenSys Response to Reviewers for a resubmission — treating the reviews as a required-changes contract, mapping each blocking concern to a specific change and the new measurement that closes it, staging the energy and testbed experiments a systems revision demands, and keeping the response anonymous and in the CFP's form.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sensys-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.
# SenSys Author Response The SenSys resubmission is a **contract**, not a rebuttal debate. Because the two-deadline model lets a rejected paper return at the next deadline **only with a substantive revision and a Response to Reviewers**, the response's job is to prove that each concern the reviewers raised has been *closed in the revised paper* — most often with a new measurement, not an argument.
What does the sensys-author-response skill do?
Use when writing a SenSys Response to Reviewers for a resubmission — treating the reviews as a required-changes contract, mapping each blocking concern to a specific change and the new measurement that closes it, staging the energy and testbed experiments a systems revision demands, and keeping the response anonymous and in the CFP's form.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sensys-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 909 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.