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 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…
MITAuto-check passed
Install Sensys Author Response
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sensys-author-response -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sensys-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/SenSys-Skills/skills/sensys-author-response .claude/skills/sensys-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 "sensys-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SenSys-Skills/skills/sensys-author-response into .claude/skills/sensys-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sensys-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/SenSys-Skills/skills/sensys-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 sensys-author-response -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sensys-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/SenSys-Skills/skills/sensys-author-response .agents/skills/sensys-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 "sensys-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SenSys-Skills/skills/sensys-author-response into .agents/skills/sensys-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sensys-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 sensys-author-response -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sensys-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/SenSys-Skills/skills/sensys-author-response .cursor/skills/sensys-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 "sensys-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SenSys-Skills/skills/sensys-author-response into .cursor/skills/sensys-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sensys-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 SenSys-Skills/skills/sensys-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 sensys-author-response -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sensys-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/SenSys-Skills/skills/sensys-author-response .gemini/skills/sensys-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 "sensys-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SenSys-Skills/skills/sensys-author-response into .gemini/skills/sensys-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sensys-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 sensys-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 sensys-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/SenSys-Skills/skills/sensys-author-response .github/skills/sensys-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 "sensys-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SenSys-Skills/skills/sensys-author-response into .github/skills/sensys-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sensys-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 sensys-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 sensys-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/SenSys-Skills/skills/sensys-author-response .opencode/skills/sensys-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 "sensys-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SenSys-Skills/skills/sensys-author-response into .opencode/skills/sensys-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sensys-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
sensys-author-response- GitHub stars
- 1.2k
- Token cost
- ~1.3k tokens
- SKILL.md length
- 466 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses 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…
- Writing a SenSys Response to Reviewers for a resubmission — treating the reviews as a required-changes contract
- SKILL.md covers The response is a change-map, Stage the experiments before…, Sort every point before you… and Rules of the response, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Mapping each blocking concern to a specific change and the new measurement that closes it
What it does
Sensys Author Response is an agent skill from brycewang-stanford/Awesome-Journal-Skills. 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.
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.
When your agent uses it
- 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
- Keeping the response anonymous and in the CFPs form
Example prompts
- “/sensys-author-response”
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
Sensys Author Response loads about 1.3k tokens when it runs. Until then it costs about 91 tokens; SKILL.md has 466 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). 466 words, ~1,271 tokens.
Download SKILL.mdSave it as
.claude/skills/sensys-author-response/SKILL.md (or your agent's skills folder).- name
- sensys-author-response
- description
- 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.
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. A response that argues instead of measures is the most common way a resubmission fails again.
The response is a change-map
For every reviewer point, produce a row: the concern, the change you made, and where in the revised paper it now lives. This is the artifact reviewers actually read.
R2-a "Energy claim not measured; datasheet current used."
→ Change: measured average draw with a shunt at 10 kHz across a full duty cycle.
→ Where: §4.2 rewritten; Fig. 4 new power trace; Table 2 updated with measured energy.
→ Status: CLOSED with new measurement.
R1-c "Ground truth for accuracy is unclear."
→ Change: documented the reference-instrument protocol and its own error.
→ Where: App. A new; §4.3 now cites it.
→ Status: CLOSED.
R3-b "Suggest testing at 100 nodes."
→ Change: added a 40-node run (largest testbed available); discussed scaling limit.
→ Where: §4.4; limitation stated in §6.
→ Status: PARTIALLY addressed — scope noted honestly.Stage the experiments before you write
A systems revision usually needs new data, and energy/testbed measurements have lead time. As
soon as the reviews land, sort the blocking points (sensys-review-process) and schedule the
runs against the next deadline (sensys-workflow): a new deployment or harvesting campaign may
need weeks of wall-clock time you cannot compress. Write the response around results you will
actually have, not results you hope to have.
Sort every point before you answer it
Not every reviewer comment earns the same response. Triage first, then spend the revision budget where it changes the verdict.
| Point type | What it needs | Response move |
|---|---|---|
| Blocking (disbelieved claim) | New measurement on real hardware | Run it; row marked CLOSED with the figure/table |
| Fixable gap | A bench run or clearer figure | Address and point to the location |
| Framing misread | Rewriting, no new data | Clarify in the paper; note the change |
| Wishlist (out of scope) | A brief, honest scoping reply | Acknowledge; do not spend the budget here |
Show full SKILL.md (190 more words)Show less
Rules of the response
- Close, do not argue. Prefer "we measured X and updated Table 2" over "we believe the reviewer is mistaken." When a reviewer is genuinely wrong, show the measurement that settles it rather than asserting.
- Be honest about partial closes. A concern you cannot fully address (a 100-node ask you can only meet at 40) is closed honestly by doing what you can and stating the limit — not by silence or overclaiming.
- Every promise appears in the paper. Reviewers read the response against the revised PDF; a change described but not present is worse than not promising it.
- Stay anonymous and in-form. The response is part of a double-blind resubmission; do not de-anonymize, and keep to the length/format the CFP specifies (待核实 for the exact form).
- Prioritize blocking over wishlist. Spend your revision budget on the points that made the reviewers not believe the paper, not on cosmetic wishlist items.
Tone
Professional and specific. Thank reviewers once, briefly, then get to the change-map. Avoid defensiveness and avoid flattery; a SenSys committee is persuaded by measurements and honest scoping, not by rhetoric.
Before submitting the resubmission
[ ] Every blocking concern has a row: concern → change → location → status.
[ ] Each "CLOSED" row's change is actually present in the revised PDF.
[ ] New measurements were run on real hardware, not asserted.
[ ] Partial closes are stated honestly with the scope limit named.
[ ] Response is anonymous and within the CFP's stated form/length.
[ ] The revised paper's abstract/intro reflect the strengthened evidence.
[ ] Blocking points prioritized over wishlist items in the revision budget.Output format
[Map] the change-map: each reviewer point → change → location → status
[New data] which blocking points required new measurement, and whether it exists yet
[Schedule] can the required runs finish before the next deadline? (link to workflow)
[Honesty] partial closes named with their scope limits
[Open] any concern still unclosed and the risk it carries into the next round© 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 SenSys-Skills/skills/sensys-author-response of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Sensys 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 |
|---|---|---|---|---|---|---|
| Sensys Author Response this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.3k | 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 Sensys Author Response
What does Sensys Author Response do?
A skill your agent uses 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…. Sensys Author Response is an agent skill from brycewang-stanford/Awesome-Journal-Skills. 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.
When should I use Sensys Author Response?
Sensys Author Response fits situations like: 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; keeping the response anonymous and in the CFPs form.
How do I install Sensys Author Response in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sensys-author-response -a claude-code`. Or copy the skill folder (SenSys-Skills/skills/sensys-author-response in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/sensys-author-response in your project. Claude Code loads it when a task matches its description.
How do I install Sensys Author Response in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sensys-author-response -a codex`. Or copy the skill folder (SenSys-Skills/skills/sensys-author-response in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/sensys-author-response in your project. Codex loads it when a task matches its description.
Can I use Sensys 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 sensys-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/sensys-author-response, .gemini/skills/sensys-author-response, .github/skills/sensys-author-response and .opencode/skills/sensys-author-response in your project.
What does Sensys Author Response need to run?
SKILL.md names no scripts, command-line tools or credentials: Sensys Author Response is instructions for the agent only.
Does Sensys 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 Sensys 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 Sensys Author Response use?
Sensys 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 Sensys Author Response use?
About 1.3k tokens (SKILL.md is roughly 5.1k 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 Sensys Author Response?
Skills that share tags, products or a category with Sensys 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 Sensys 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.