Review Hog Authoring
PostHog/posthog
How to author custom PostHog Review skills: the review perspectives, blind-spot checks, validation criteria, and resolution criteria that drive PostHog Review's automated PR reviews.
A skill your agent uses when answering NSDI reviewers through the channel the venue actually provides — executing a one-shot revision against the required-issues list, writing the change memo and…
MITAuto-check passed
Install Nsdi Author Response
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill nsdi-author-response -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills nsdi-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/NSDI-Skills/skills/nsdi-author-response .claude/skills/nsdi-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 "nsdi-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/NSDI-Skills/skills/nsdi-author-response into .claude/skills/nsdi-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nsdi-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/NSDI-Skills/skills/nsdi-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 nsdi-author-response -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills nsdi-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/NSDI-Skills/skills/nsdi-author-response .agents/skills/nsdi-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 "nsdi-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/NSDI-Skills/skills/nsdi-author-response into .agents/skills/nsdi-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nsdi-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 nsdi-author-response -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills nsdi-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/NSDI-Skills/skills/nsdi-author-response .cursor/skills/nsdi-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 "nsdi-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/NSDI-Skills/skills/nsdi-author-response into .cursor/skills/nsdi-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nsdi-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 NSDI-Skills/skills/nsdi-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 nsdi-author-response -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills nsdi-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/NSDI-Skills/skills/nsdi-author-response .gemini/skills/nsdi-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 "nsdi-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/NSDI-Skills/skills/nsdi-author-response into .gemini/skills/nsdi-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nsdi-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 nsdi-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 nsdi-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/NSDI-Skills/skills/nsdi-author-response .github/skills/nsdi-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 "nsdi-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/NSDI-Skills/skills/nsdi-author-response into .github/skills/nsdi-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nsdi-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 nsdi-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 nsdi-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/NSDI-Skills/skills/nsdi-author-response .opencode/skills/nsdi-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 "nsdi-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/NSDI-Skills/skills/nsdi-author-response into .opencode/skills/nsdi-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nsdi-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
nsdi-author-response- GitHub stars
- 1.2k
- Token cost
- ~1.5k tokens
- SKILL.md length
- 672 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when answering NSDI reviewers through the channel the venue actually provides — executing a one-shot revision against the required-issues list, writing the change memo and…
- Works in 3 steps: Address every listed issue, visibly.… → Do not renovate beyond the list. The… → **If an experiment's result contradicts…
- Answering NSDI reviewers through the channel the venue actually provides — executing a one-shot revision against the required-issues list
- SKILL.md covers Moment one: the response you…, Moment two: the one-shot…, The packet: memo + highlighted… and Timeline for a typical…, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Nsdi Author Response is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when answering NSDI reviewers through the channel the venue actually provides — executing a one-shot revision against the required-issues list, writing the change memo and highlighted diff for the same reviewers, and pre-empting objections inside the submission when no response phase exists.
Its SKILL.md is about 1.5k 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.
When your agent uses it
- Answering NSDI reviewers through the channel the venue actually provides — executing a one-shot revision against the required-issues list
- Writing the change memo and highlighted diff for the same reviewers
- Pre-empting objections inside the submission when no response phase exists
Example prompts
- “/nsdi-author-response”
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Address every listed issue, visibly. Coverage is binary at NSDI: revisions
- Do not renovate beyond the list. The same reviewers approved everything they
- **If an experiment's result contradicts the reviewer's expectation, report it
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
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.
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
Nsdi Author Response loads about 1.5k tokens when it runs. Until then it costs about 79 tokens; SKILL.md has 672 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). 672 words, ~1,500 tokens.
Download SKILL.mdSave it as
.claude/skills/nsdi-author-response/SKILL.md (or your agent's skills folder).- name
- nsdi-author-response
- description
- Use when answering NSDI reviewers through the channel the venue actually provides — executing a one-shot revision against the required-issues list, writing the change memo and highlighted diff for the same reviewers, and pre-empting objections inside the submission when no response phase exists.
NSDI Author Response
At NSDI the author's voice reaches reviewers at two moments only: inside the original submission, and — if granted — inside a one-shot revision packet read by the same people who wrote the demands. There is no rendered rebuttal phase in the '27 CFP (absence 待核实; verify each cycle). This skill covers both moments; the second is the venue's signature mechanism and the reason this skill is not a rebuttal-writing guide.
Moment one: the response you embed in advance
Without a mid-review channel, anticipated objections must be answered in the PDF:
- Run the objection drill: each coauthor writes the three most likely reviewer
complaints; any complaint appearing twice gets a paragraph in the paper —
typically a "why not X?" design-alternatives note or a limits paragraph
(
nsdi-writing-style). - Pre-empt the baseline attack by documenting baseline tuning in-body
(
nsdi-experiments). - Pre-empt the scope attack with an explicit sentence locating the contribution in
the networking stack or distributed design (
nsdi-topic-selection).
Moment two: the one-shot revision, treated as a contract
The decision letter's required-issues list is an offer with exact terms: fix these, same reviewers check, one attempt. Respond like a contractor, not a debater.
Triage the issues within days of notification:
| Issue type | Typical cost | Response posture |
|---|---|---|
| New experiment / baseline | machine-weeks + testbed access | reserve infrastructure immediately (nsdi-workflow) |
| Analysis or clarity | days | do fully; these are free credibility |
| Claim recalibration | hours, plus ego | almost always concede — narrow the claim to the evidence |
| Genuinely infeasible demand | — | contact the program co-chairs early; silence then surprise is the worst path |
Execution rules:
- Address every listed issue, visibly. Coverage is binary at NSDI: revisions that fail to address the required issues are rejected with no further revision option. Partial credit does not exist.
- Do not renovate beyond the list. The same reviewers approved everything they did not flag; gratuitous rewrites reopen settled sections and can introduce new objections that the one-shot format gives you no chance to answer.
- If an experiment's result contradicts the reviewer's expectation, report it straight. The issue said "evaluate under churn," not "show churn is fine." An honest unfavorable result plus a scoped claim is a fulfilled requirement; a massaged favorable one is a rejection when the reviewer probes.
Show full SKILL.md (305 more words)Show less
The packet: memo + highlighted diff
Both components are mandatory auxiliary material (nsdi-supplementary). Their shared
purpose: let a reviewer verify their own issue in under a minute.
Change memo skeleton (one block per required issue, in the letter's order):
R-1 Compare against <deployed system>.
DONE — §6.2 now includes tuned <system> (config: App. C).
Result: our gains drop from 3.4x to 2.6x at p99.9; text and
abstract recalibrated. [diff pages 8-9, 1]
R-2 Clarify lease-expiry semantics.
DONE — new §4.3 (state machine, Fig. 5); two corner cases we
had not specified are now explicit. [diff pages 5-6]
Also changed (minimal): fixed two typos flagged in reviews; updated
citation [31] to its published version. No other content changes.The "Also changed" section builds the trust the format depends on — it certifies the diff is complete. Generate the highlighted version mechanically (latexdiff or equivalent) from the true submitted baseline, not from a reconstructed one.
Tone: the readers already invested in this paper — a one-shot revision means they voted to see it again. Write as a colleague closing out a punch list: no re-argument of the original decision, no flattery, no hedging about what was and wasn't done.
Timeline for a typical revision window
A spring '27 one-shot revision (notified July 23, 2026) targeting the fall gate (September 17, 2026) has roughly eight weeks:
- Week 1: issue ledger built; infeasibility flags raised with co-chairs if any; testbed time reserved.
- Weeks 2-5: demanded experiments run with full provenance
(
nsdi-reproducibility); text changes drafted in parallel. - Week 6: memo and diff assembled from the running drafts; internal reviewer plays the original R2 against the packet.
- Week 7: freeze; verify the resubmission enters the correct HotCRP site with
the packet attached (
nsdi-submission). - Week 8: buffer — the revision that arrives calm beats the one that arrives complete-but-chaotic at 11:58 pm.
A fall-issued revision aiming at the next edition's spring gate has more calendar but the same structure; do not let the longer runway defer the testbed reservation.
When the letter says plain reject
There is no response channel and no appeal-by-email; the ban clock runs
(nsdi-review-process). The productive move is extraction: convert each review
point into either a fix, a re-route signal, or a documented disagreement to handle
in the next version's pre-emption layer. The reviews were written by this
community; the next PC will resemble them.
Output format
[Channel] pre-emption (drafting) / one-shot revision (letter in hand)
[Issue ledger] R-# -> action -> cost -> owner -> status
[Feasibility] any issue needing co-chair contact? deadline realistic?
[Packet status] memo issue-complete? diff from true baseline? extras declared?
[Risk] unfavorable-result handling; renovation creep check
[Ship date] resubmission gate targeted, freeze date set© 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 NSDI-Skills/skills/nsdi-author-response of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Nsdi 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 |
|---|---|---|---|---|---|---|
| Nsdi Author Response this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.5k | Automated safety check: Pass | MIT | |
| Review Hog AuthoringPostHog/posthog | 40k | — | ~2k | Automated safety check: Pass | Custom licence | |
| Review ResponseGalaxy-Dawn/claude-scholar | 5.7k | 2 repos | ~1.4k | Automated safety check: Pass | MIT | |
| Nature Reviewer ResponseYuan1z0825/nature-skills | 47k | — | ~1.5k | Automated safety check: Pass | Apache-2.0 | |
| Review Pending PR Reviewsnrwl/nx | 29k | — | ~3.9k | Automated safety check: Pass | MIT | |
| Responsive Unitsthedaviddias/Front-End-Checklist | 74k | — | ~472 | Automated safety check: Pass | MIT |
Similar skills
- Official
Review Response
Galaxy-Dawn/claude-scholar
Systematic review response workflow from comment analysis to professional rebuttal writing.
Nature Reviewer Response
Yuan1z0825/nature-skills
Drafts, audits and revises responses to peer review: point-by-point replies, revision cover letters and marked-manuscript or LaTeX revision packages.
Review Pending PR Reviews
nrwl/nx
Review, grill, edit, and post pending PR review drafts saved by /review-pr (or its batch/cron runners).
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.
Review
thedaviddias/Front-End-Checklist
A skill your agent uses when applies to product pages, local business pages, recipes, apps, books, and any page that aggregates user reviews.
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…
Questions about Nsdi Author Response
What does Nsdi Author Response do?
A skill your agent uses when answering NSDI reviewers through the channel the venue actually provides — executing a one-shot revision against the required-issues list, writing the change memo and…. Nsdi Author Response is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when answering NSDI reviewers through the channel the venue actually provides — executing a one-shot revision against the required-issues list, writing the change memo and highlighted diff for the same reviewers, and pre-empting objections inside the submission when no response phase exists.
When should I use Nsdi Author Response?
Nsdi Author Response fits situations like: answering NSDI reviewers through the channel the venue actually provides — executing a one-shot revision against the required-issues list; writing the change memo and highlighted diff for the same reviewers; pre-empting objections inside the submission when no response phase exists.
How do I install Nsdi Author Response in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill nsdi-author-response -a claude-code`. Or copy the skill folder (NSDI-Skills/skills/nsdi-author-response in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/nsdi-author-response in your project. Claude Code loads it when a task matches its description.
How do I install Nsdi Author Response in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill nsdi-author-response -a codex`. Or copy the skill folder (NSDI-Skills/skills/nsdi-author-response in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/nsdi-author-response in your project. Codex loads it when a task matches its description.
Can I use Nsdi 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 nsdi-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/nsdi-author-response, .gemini/skills/nsdi-author-response, .github/skills/nsdi-author-response and .opencode/skills/nsdi-author-response in your project.
What does Nsdi Author Response need to run?
SKILL.md names no scripts, command-line tools or credentials: Nsdi Author Response is instructions for the agent only.
Does Nsdi 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 Nsdi 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 Nsdi Author Response use?
Nsdi 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 Nsdi Author Response use?
About 1.5k tokens (SKILL.md is roughly 6k 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 Nsdi Author Response?
Skills that share tags, products or a category with Nsdi Author Response: Review Hog Authoring (PostHog/posthog, 40k stars), Review Response (Galaxy-Dawn/claude-scholar, 5.7k stars), Nature Reviewer Response (Yuan1z0825/nature-skills, 47k stars) and Review Pending PR Reviews (nrwl/nx, 29k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Nsdi 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.