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 handling author-side dialogue in an OSDI cycle — which in 2026 means no rebuttal at all: pre-empting objections inside the submission, then treating the…
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill osdi-author-response -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills osdi-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/OSDI-Skills/skills/osdi-author-response .claude/skills/osdi-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 "osdi-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/OSDI-Skills/skills/osdi-author-response into .claude/skills/osdi-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "osdi-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/OSDI-Skills/skills/osdi-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 osdi-author-response -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills osdi-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/OSDI-Skills/skills/osdi-author-response .agents/skills/osdi-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 "osdi-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/OSDI-Skills/skills/osdi-author-response into .agents/skills/osdi-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "osdi-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 osdi-author-response -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills osdi-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/OSDI-Skills/skills/osdi-author-response .cursor/skills/osdi-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 "osdi-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/OSDI-Skills/skills/osdi-author-response into .cursor/skills/osdi-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "osdi-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 OSDI-Skills/skills/osdi-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 osdi-author-response -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills osdi-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/OSDI-Skills/skills/osdi-author-response .gemini/skills/osdi-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 "osdi-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/OSDI-Skills/skills/osdi-author-response into .gemini/skills/osdi-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "osdi-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 osdi-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 osdi-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/OSDI-Skills/skills/osdi-author-response .github/skills/osdi-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 "osdi-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/OSDI-Skills/skills/osdi-author-response into .github/skills/osdi-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "osdi-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 osdi-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 osdi-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/OSDI-Skills/skills/osdi-author-response .opencode/skills/osdi-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 "osdi-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/OSDI-Skills/skills/osdi-author-response into .opencode/skills/osdi-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "osdi-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.
osdi-author-responseA skill your agent uses when handling author-side dialogue in an OSDI cycle — which in 2026 means no rebuttal at all: pre-empting objections inside the submission, then treating the…
Osdi Author Response is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when handling author-side dialogue in an OSDI cycle — which in 2026 means no rebuttal at all: pre-empting objections inside the submission, then treating the conditional-accept shepherd exchange as the real author response, with a protocol for mandated revisions and for cycles that reinstate a response phase.
Its SKILL.md is about 1.7k 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.
3 steps, taken from the step headings in SKILL.md.
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.
Osdi Author Response loads about 1.7k tokens when it runs. Until then it costs about 84 tokens; SKILL.md has 846 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). 846 words, ~1,701 tokens.
.claude/skills/osdi-author-response/SKILL.md (or your agent's skills folder).At most venues this skill would draft a rebuttal. At OSDI '26 there was no author-response period (verified 2026-07-08) — a deliberate removal, since earlier OSDI cycles had one. The author's voice therefore appears at exactly two points: before submission, inside the paper, and after a conditional accept, in the shepherding exchange. This skill covers both, plus the fallback if a future cycle reinstates a response phase (待核实 each year — check the current CFP's process section first, always).
Since no clarification channel will exist between December and March, run a pre-mortem rebuttal on the draft two to three weeks before the deadline:
osdi-writing-style).The test of the fix: a sympathetic PC member should be able to answer the objection in discussion by quoting your paper. You will not be in the room; your text is.
A conditional accept arrives with a PC-mandated change list and a shepherd who must approve the final paper by June 9 — otherwise the paper is rejected from the program. This is a response process with enforcement, and it rewards the same discipline a rebuttal would:
| Rebuttal instinct | Shepherding translation |
|---|---|
| Answer every point | Build a change matrix: mandate → action → paper location → status |
| Be concise and factual | Short status notes to the shepherd; diffs and section pointers over essays |
| Don't relitigate scores | Don't relitigate the reviews — the decision is made; only the changes matter |
| New results need care | Mandated experiments get full osdi-experiments rigor on the frozen testbed |
| Deadline discipline | Front-load: first full revision to the shepherd weeks before June 9, not on it |
change-matrix.md (shared with coauthors; mirrored in notes to the shepherd)
M1 "compare against X under skewed load" -> new fig 9 -> §5.3 -> DONE
M2 "state the consistency model precisely"-> new §3.1 defs -> §3.1 -> DRAFT
M3 "temper claims about portability" -> rewrote claims -> §1,§7 -> DONE
open question -> shepherd (2026-04-14): does M1 require both skew levels?Two rules of tone: the shepherd is the paper's ally and its gate simultaneously — give them evidence to approve, never pressure to concede; and where a mandate seems infeasible (hardware gone, trace unlicensable), raise it immediately with an alternative, not in June with an apology.
The '26 cycle allowed roughly ten weeks from notification (March 26) to the final paper (June 9), and the artifact deadline (May 8) lands in the middle of it. A workable split for a conditional accept:
osdi-artifact-evaluation) — the same person cannot do both in the same week, so
split ownership explicitly.OSDI has had responses before and could again. If the current CFP announces one, apply the compressed classic form — and OSDI-specific emphases:
Mandated runs are the highest-risk shepherding item because they can fail:
[Cycle process] response period this year? none / exists (source: current CFP; else 待核实)
[Phase] pre-submission pre-mortem / shepherding / reinstated-response
[If pre-mortem] top objections + class (misreading/gap/disagreement) + in-text fix
[If shepherding] change matrix status <done/total>; open questions to shepherd; June risk
[Tone check] anything that relitigates instead of resolves? <flag it>© 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 OSDI-Skills/skills/osdi-author-response of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Osdi 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 |
|---|---|---|---|---|---|---|
| Osdi Author Response this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.7k | Automated safety check: Pass | MIT | |
| Responsive Unitsthedaviddias/Front-End-Checklist | 74k | — | ~472 | Automated safety check: Pass | MIT | |
| Abp Authorizationabpframework/abp | 14k | — | ~1.3k | Automated safety check: Pass | LGPL-3.0 | |
| Hermes Agent Skill AuthoringNousResearch/hermes-agent | 252k | — | ~3.6k | Automated safety check: Pass | MIT | |
| Edbt Author Responsebrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.2k | Automated safety check: Pass | MIT | |
| Cikm Author Responsebrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.6k | 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.
abpframework/abp
ABP permission system - PermissionDefinitionProvider, [Authorize] attribute, CheckPolicyAsync, IsGrantedAsync, ICurrentUser, IPermissionManager, multi-tenancy side.
NousResearch/hermes-agent
Author in-repo SKILL.md files: frontmatter and structure. An agent skill from NousResearch/hermes-agent.
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when drafting EDBT author responses across the two turns of a cycle — the short author-feedback reply on the initial reviews, and the in-cycle revise-and-resubmit change…
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when preparing author-side communication around CIKM reviews — drafting for a response window if the cycle offers one (unconfirmed for 2026), writing camera-ready revision…
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when drafting an ACL author response inside an ACL Rolling Review cycle on OpenReview, covering the response window before meta-review, reviewer discussion dynamics…
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 handling author-side dialogue in an OSDI cycle — which in 2026 means no rebuttal at all: pre-empting objections inside the submission, then treating the…. Osdi Author Response is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when handling author-side dialogue in an OSDI cycle — which in 2026 means no rebuttal at all: pre-empting objections inside the submission, then treating the conditional-accept shepherd exchange as the real author response, with a protocol for mandated revisions and for cycles that reinstate a response phase.
Osdi Author Response fits situations like: handling author-side dialogue in an OSDI cycle — which in 2026 means no rebuttal at all: pre-empting objections inside the submission; then treating the conditional-accept shepherd exchange as the real author response; with a protocol for mandated revisions and for cycles that reinstate a response phase.
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill osdi-author-response -a claude-code`. Or copy the skill folder (OSDI-Skills/skills/osdi-author-response in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/osdi-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 osdi-author-response -a codex`. Or copy the skill folder (OSDI-Skills/skills/osdi-author-response in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/osdi-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 osdi-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/osdi-author-response, .gemini/skills/osdi-author-response, .github/skills/osdi-author-response and .opencode/skills/osdi-author-response in your project.
SKILL.md names no scripts, command-line tools or credentials: Osdi 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.
Osdi 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.7k tokens (SKILL.md is roughly 6.8k 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 Osdi Author Response: Responsive Units (thedaviddias/Front-End-Checklist, 74k stars), Abp Authorization (abpframework/abp, 14k stars), Hermes Agent Skill Authoring (NousResearch/hermes-agent, 252k stars) and Edbt 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,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.