Responsive Units
thedaviddias/Front-End-Checklist
A skill your agent uses when reviewing stylesheets, component styles, and responsive behavior related to Use relative units for responsive layouts.
A skill your agent uses when drafting an IEEE PerCom rebuttal after being invited following the initial reviews, covering the bounded single-round reply that answers explicit reviewer questions…
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill percom-author-response -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills percom-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/PerCom-Skills/skills/percom-author-response .claude/skills/percom-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 "percom-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PerCom-Skills/skills/percom-author-response into .claude/skills/percom-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "percom-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/PerCom-Skills/skills/percom-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 percom-author-response -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills percom-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/PerCom-Skills/skills/percom-author-response .agents/skills/percom-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 "percom-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PerCom-Skills/skills/percom-author-response into .agents/skills/percom-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "percom-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 percom-author-response -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills percom-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/PerCom-Skills/skills/percom-author-response .cursor/skills/percom-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 "percom-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PerCom-Skills/skills/percom-author-response into .cursor/skills/percom-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "percom-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 PerCom-Skills/skills/percom-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 percom-author-response -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills percom-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/PerCom-Skills/skills/percom-author-response .gemini/skills/percom-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 "percom-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PerCom-Skills/skills/percom-author-response into .gemini/skills/percom-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "percom-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 percom-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 percom-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/PerCom-Skills/skills/percom-author-response .github/skills/percom-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 "percom-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PerCom-Skills/skills/percom-author-response into .github/skills/percom-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "percom-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 percom-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 percom-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/PerCom-Skills/skills/percom-author-response .opencode/skills/percom-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 "percom-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PerCom-Skills/skills/percom-author-response into .opencode/skills/percom-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "percom-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.
percom-author-responseA skill your agent uses when drafting an IEEE PerCom rebuttal after being invited following the initial reviews, covering the bounded single-round reply that answers explicit reviewer questions…
Percom Author Response is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when drafting an IEEE PerCom rebuttal after being invited following the initial reviews, covering the bounded single-round reply that answers explicit reviewer questions, corrects misreadings, points to evidence already in the paper without promising new experiments, and preserves double-blindness.
Its SKILL.md is about 1.3k 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.
Read from SKILL.md and the folder at commit 932eb23. It shows what the files ask for, not the result of running them.
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.
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Percom Author Response loads about 1.3k tokens when it runs. Until then it costs about 82 tokens; SKILL.md has 544 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.
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.
The full file from brycewang-stanford/Awesome-Journal-Skills at commit 932eb23, republished under its MIT licence (© brycewang-stanford). 544 words, ~1,300 tokens.
.claude/skills/percom-author-response/SKILL.md (or your agent's skills folder).Use this after PerCom reviews are released and you have been invited to submit a rebuttal. PerCom's rebuttal is a single, bounded turn: it answers the reviewers' explicit questions, resolves misunderstandings, and clarifies — and the call states that new experiments are not expected. There is no journal-style revision that follows, so the rebuttal must win with the paper you already submitted. It remains double-blind: reveal no author, institution, testbed, or dataset-owner identity.
Papers with no positive review are early-rejected before the rebuttal opens — there is no rebuttal to write for those. If you were invited, at least one reviewer sees a path to publication: your job is to give that advocate the answers they need for the TPC discussion, and to neutralize the specific doubts of the others.
Group by reviewer, lead each item with the reviewer's own question, and answer with a pointer into the existing paper:
[R1.Q1] "Is the eating-recognition result cross-subject or within-subject?"
-> Table 2 already reports leave-one-subject-out F1 (0.xx, 95% CI ...); the pooled number
in the abstract is secondary. We will make this ordering explicit in §4.1.
[R2.Q1] "The baseline seems untuned."
-> The baseline used the same feature budget and a grid search reported in Appendix A;
we point R2 to Table A1 and will surface it in the body.
[R3.Q1] "How does it behave under confounding non-eating activities?"
-> Table 4 already measures false positives against typing/brushing; we clarify the caption.The rule that wins a bounded rebuttal: every explicit question gets a direct, located answer. A question left unaddressed is what the discussion punishes, because there is no later round to fix it.
| Pushback | What it signals | PerCom-ready response |
|---|---|---|
| "Evaluation is within-subject" | The core ubicomp doubt | Point to your leave-one-subject-out table; if you truly lack it, this is likely fatal — do not fake it |
| "Accuracy is inflated by class imbalance" | Metric-choice doubt | Point to reported F1 / event-level metrics and the class balance; clarify which metric is headline |
| "The baseline is not fair/tuned" | Soundness doubt | Point to the equal-budget tuning already in the paper/appendix; clarify placement |
| "Does this generalize beyond your subjects?" | External-validity limit | Point to the diversity of subjects and the stated limitation; do not overclaim |
| "The dataset/system is not available" | Open-data gap | Point to the (anonymized) release plan; describe what will be public post-acceptance |
| "Contribution overlaps prior work X" | Novelty doubt | Sharpen the delta in words; point to the comparison already present |
[Gate] invited to rebuttal? yes/no (if no: reroute, do not draft)
[Priority question] <reviewer's explicit question>
[Decision dimension] significance / soundness / cross-subject evaluation / metrics / clarity
[Located answer] <question -> pointer to existing table/figure/appendix; clarification to add>
[No-new-experiment check] <every answer grounded in submitted material? yes/no>
[Anonymity check] <no identity leak in the reply: passed/issues>© 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
Just SKILL.md in PerCom-Skills/skills/percom-author-response of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Percom 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 |
|---|---|---|---|---|---|---|
| Percom Author Response this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.3k | Automated safety check: Pass | MIT | |
| Responsive Unitsthedaviddias/Front-End-Checklist | 74k | — | ~472 | Automated safety check: Pass | MIT | |
| Icsme Author Responsebrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.3k | Automated safety check: Pass | MIT | |
| Fast Author Responsebrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.5k | Automated safety check: Pass | MIT | |
| Icassp Author Responsebrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.2k | Automated safety check: Pass | MIT | |
| Ase Author Responsebrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.4k | Automated safety check: Pass | MIT |
thedaviddias/Front-End-Checklist
A skill your agent uses when reviewing stylesheets, component styles, and responsive behavior related to Use relative units for responsive layouts.
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when drafting an IEEE ICSME author response during the double-anonymous author-response period, covering the early-decision cut that decides whether you respond at all…
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when drafting USENIX FAST author responses, covering the short pre-notification rebuttal during the author-response period and — distinctively — the one-shot-revision change…
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when drafting an ICASSP rebuttal or author response to reviews, covering the recently added and short author-response window, the single-blind setting where reviewers already…
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when drafting ASE (IEEE/ACM Automated Software Engineering) author responses, covering the double-anonymous rebuttal that must first survive the early-rejection gate and —…
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when drafting an AAAI author response (rebuttal) under the single short character-limited author-feedback window, the no-URL rule, no-new-results guidance…
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…
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…
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…
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…
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…
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…
A skill your agent uses when drafting an IEEE PerCom rebuttal after being invited following the initial reviews, covering the bounded single-round reply that answers explicit reviewer questions…. Percom Author Response is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when drafting an IEEE PerCom rebuttal after being invited following the initial reviews, covering the bounded single-round reply that answers explicit reviewer questions, corrects misreadings, points to evidence already in the paper without promising new experiments, and preserves double-blindness.
Percom Author Response fits situations like: drafting an IEEE PerCom rebuttal after being invited following the initial reviews; covering the bounded single-round reply that answers explicit reviewer questions; corrects misreadings; points to evidence already in the paper without promising new experiments.
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill percom-author-response -a claude-code`. Or copy the skill folder (PerCom-Skills/skills/percom-author-response in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/percom-author-response in your project. Claude Code loads it when a task matches its description.
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill percom-author-response -a codex`. Or copy the skill folder (PerCom-Skills/skills/percom-author-response in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/percom-author-response in your project. Codex loads it when a task matches its description.
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 percom-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/percom-author-response, .gemini/skills/percom-author-response, .github/skills/percom-author-response and .opencode/skills/percom-author-response in your project.
SKILL.md names no scripts, command-line tools or credentials: Percom Author Response is instructions for the agent only.
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.
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.
Percom 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.
About 1.3k tokens (SKILL.md is roughly 5.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Percom Author Response: Responsive Units (thedaviddias/Front-End-Checklist, 74k stars), Icsme Author Response (brycewang-stanford/Awesome-Journal-Skills, 1.2k stars), Fast Author Response (brycewang-stanford/Awesome-Journal-Skills, 1.2k stars) and Icassp Author Response (brycewang-stanford/Awesome-Journal-Skills, 1.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,228 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.