Hypothesis Generation
spacering-net/codeg
Structured hypothesis formulation from observations. An agent skill from spacering-net/codeg.
A skill your agent uses when drafting ACM CoNEXT author responses, covering the initial-review rebuttal and — distinctively — the one-shot "major" revision response letter that must stay…
Install Conext Author Response
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill conext-author-response -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills conext-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/CoNEXT-Skills/skills/conext-author-response .claude/skills/conext-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 "conext-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CoNEXT-Skills/skills/conext-author-response into .claude/skills/conext-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "conext-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/CoNEXT-Skills/skills/conext-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 conext-author-response -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills conext-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/CoNEXT-Skills/skills/conext-author-response .agents/skills/conext-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 "conext-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CoNEXT-Skills/skills/conext-author-response into .agents/skills/conext-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "conext-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 conext-author-response -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills conext-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/CoNEXT-Skills/skills/conext-author-response .cursor/skills/conext-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 "conext-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CoNEXT-Skills/skills/conext-author-response into .cursor/skills/conext-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "conext-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 CoNEXT-Skills/skills/conext-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 conext-author-response -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills conext-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/CoNEXT-Skills/skills/conext-author-response .gemini/skills/conext-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 "conext-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CoNEXT-Skills/skills/conext-author-response into .gemini/skills/conext-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "conext-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 conext-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 conext-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/CoNEXT-Skills/skills/conext-author-response .github/skills/conext-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 "conext-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CoNEXT-Skills/skills/conext-author-response into .github/skills/conext-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "conext-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 conext-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 conext-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/CoNEXT-Skills/skills/conext-author-response .opencode/skills/conext-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 "conext-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CoNEXT-Skills/skills/conext-author-response into .opencode/skills/conext-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "conext-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
conext-author-response- GitHub stars
- 1.2k
- Token cost
- ~1.3k tokens
- SKILL.md length
- 575 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when drafting ACM CoNEXT author responses, covering the initial-review rebuttal and — distinctively — the one-shot "major" revision response letter that must stay…
- Drafting ACM CoNEXT author responses
- SKILL.md covers Triage (both turns), Turn 1 — the initial rebuttal, Turn 2 — the one-shot… and Reviewer pushback patterns, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Covering the initial-review rebuttal and — distinctively — the one-shot major revision response letter that must stay double-anonymous
What it does
Conext Author Response is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when drafting ACM CoNEXT author responses, covering the initial-review rebuttal and — distinctively — the one-shot "major" revision response letter that must stay double-anonymous, map every "minimum necessary change" to a concrete tracked edit, and survive a single re-review by the original reviewers and a shepherd under PACMNET.
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.
It sits in Research & Science. 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
- Drafting ACM CoNEXT author responses
- Covering the initial-review rebuttal and — distinctively — the one-shot major revision response letter that must stay double-anonymous
- Map every minimum necessary change to a concrete tracked edit
- Survive a single re-review by the original reviewers and a shepherd under PACMNET
Example prompts
- “revision response letter that must stay double-anonymous, map every”
- “/conext-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
Conext Author Response loads about 1.3k tokens when it runs. Until then it costs about 90 tokens; SKILL.md has 575 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). 575 words, ~1,341 tokens.
Download SKILL.mdSave it as
.claude/skills/conext-author-response/SKILL.md (or your agent's skills folder).- name
- conext-author-response
- description
- Use when drafting ACM CoNEXT author responses, covering the initial-review rebuttal and — distinctively — the one-shot "major" revision response letter that must stay double-anonymous, map every "minimum necessary change" to a concrete tracked edit, and survive a single re-review by the original reviewers and a shepherd under PACMNET.
CoNEXT Author Response
Use this after CoNEXT reviews are released. CoNEXT has two distinct speaking turns, and conflating them is a common mistake: a short initial rebuttal, and — if you receive a one-shot major revision — a full, journal-style response letter accompanying a revised paper that the original reviewers re-read exactly once. Both must respect double-anonymity: the letter itself must not reveal authors, institutions, testbeds, or repository ownership.
Triage (both turns)
- Answer what affects the decision: significance, soundness, measurement quality, baseline fairness, clarity, and reproducibility.
- Use evidence that already exists or that the revision will concretely add — never a vague promise.
- Correct factual misreadings first; a reviewer who misread a figure or a testbed setup is often persuadable.
- Keep every word anonymous. Do not name your system's real name, your institution, your operator partner, a grant, or a private repository, even to strengthen a point.
Turn 1 — the initial rebuttal
Short and decision-focused. One decision-critical point per reviewer beats an exhaustive reply. Concede what is true, correct what is misread, and point to exactly where the answer lives in the submitted paper or artifact. Do not paste large new results the reviewers cannot verify in the time they have.
Turn 2 — the one-shot major-revision response letter (the distinctive CoNEXT move)
A major revision is a genuine, one-shot revise-and-resubmit against a list of minimum necessary changes. The letter is a change ledger: for every item on that list (and every substantive reviewer request), either make the change and show it, or decline it with a reason.
[MNC-1] Minimum-necessary change (quoted briefly)
-> Action: DONE | added the real-buffer testbed run, §5.2, Table 3; effect sizes reported
-> Where: §5.2, Table 3; artifact/testbed/rq2/
[MNC-2] Minimum-necessary change
-> Action: DECLINED (with reason) | the requested baseline needs operator telemetry we
cannot release without breaking anonymity/agreement; added a limitation note instead (§6.1)
[R2.1] Reviewer request (not on the MNC list)
-> Action: PARTIAL | added the ablation; the larger multi-site deployment is out of scope
for the revision window and is noted as future workThe rule that turns a one-shot revision into an acceptance: no silent omissions. A minimum-necessary change that is neither done nor explicitly declined is exactly what the single second read punishes. Assume a shepherd will check each item against the revised PDF.
Show full SKILL.md (279 more words)Show less
Reviewer pushback patterns
| Pushback | What it signals | CoNEXT-ready response |
|---|---|---|
| "Evaluated in simulation, not on real hardware" | Platform-realism doubt | Add a testbed/deployment run on the real target, or scope the claim and name the gap as a limitation |
| "The baseline is not tuned/fair" | Soundness doubt about the comparison | Re-run with an equal, documented configuration; report the new numbers, or justify the choice |
| "Does this generalize beyond one path/network?" | External-validity limit | Add vantage points or subjects, or scope the claim and name the limit |
| "The measurement is a proxy for the real outcome" | Construct-validity objection | Add the ground-truth subset or bound the proxy; state the residual threat plainly |
| "The artifact does not run / is missing" | Reproducibility gap | Fix and re-anonymize the artifact; describe the run path in the letter |
| "Contribution overlaps prior work X" | Novelty/delta doubt | Sharpen the delta sentence; add the missing comparison |
Anonymity in the letter (easy to slip)
- Refer to your own prior work in the third person, as in the paper.
- Describe artifact and testbed changes without linking to an identity-revealing repository or an internal hostname; use the anonymized location.
- Do not thank a named collaborator, operator partner, or funder inside the response.
Calibration
- Respond to the criterion the reviewer actually raised, not the one you would rather defend.
- Length and format norms for both turns, and the exact revision window, vary by cycle; confirm the current instructions before sending.
- The TPC discussion and the shepherd decide; write the letter as evidence for an advocate, and make the revised paper — not the letter — carry the argument.
- Remember it is one shot: there is no second revision round, so leave nothing on the change list unaddressed.
Output format
[Turn] initial rebuttal / one-shot major-revision response letter
[Priority issue] <reviewer concern>
[Decision dimension] significance / soundness / measurement quality / baselines / clarity / reproducibility
[Change ledger] <minimum-necessary change -> DONE/PARTIAL/DECLINED + where in paper/artifact>
[Anonymity check] <no identity leak in the letter: 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
Files
Just SKILL.md in CoNEXT-Skills/skills/conext-author-response of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Conext 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 |
|---|---|---|---|---|---|---|
| Conext Author Response this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.3k | Automated safety check: Pass | MIT | |
| Hypothesis Generationspacering-net/codeg | 3.9k | 14 repos | ~3.6k | Automated safety check: Notes | MIT | |
| GitHub Deep Researchbytedance/deer-flow | 84k | 4 repos | ~1.3k | Automated safety check: Pass | MIT | |
| Nature Paper CardYuan1z0825/nature-skills | 47k | 2 repos | ~2.1k | Automated safety check: Pass | Apache-2.0 | |
| Content Research Writerweapp-tailwindcss/weapp-tailwindcss | 1.9k | 25 repos | ~3.5k | Automated safety check: Pass | MIT | |
| Last30daysmvanhorn/last30days-skill | 64k | — | ~7.9k | Automated safety check: Notes | MIT |
Similar skills
GitHub Deep Research
bytedance/deer-flow
Researches a GitHub repository over four rounds using the GitHub API and web search, then writes a structured markdown report with timeline, metrics and Mermaid diagrams.
Nature Paper Card
Yuan1z0825/nature-skills
Builds a structured deep-reading card for one scientific paper, covering methods, how experiments support claims, limitations and research ideas, with a script to prepare the source.
Content Research Writer
weapp-tailwindcss/weapp-tailwindcss
Assists in writing high-quality content by conducting research, adding citations, improving hooks, iterating on outlines, and providing real-time feedback on each section.
Last30days
mvanhorn/last30days-skill
Research what people actually say about any topic in the last 30 days.
Peer Review
spacering-net/codeg
Structured manuscript/grant review with checklist-based evaluation.
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…
Related
Categories
Questions about Conext Author Response
What does Conext Author Response do?
A skill your agent uses when drafting ACM CoNEXT author responses, covering the initial-review rebuttal and — distinctively — the one-shot "major" revision response letter that must stay…. Conext Author Response is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when drafting ACM CoNEXT author responses, covering the initial-review rebuttal and — distinctively — the one-shot "major" revision response letter that must stay double-anonymous, map every "minimum necessary change" to a concrete tracked edit, and survive a single re-review by the original reviewers and a shepherd under PACMNET.
When should I use Conext Author Response?
Conext Author Response fits situations like: drafting ACM CoNEXT author responses; covering the initial-review rebuttal and — distinctively — the one-shot major revision response letter that must stay double-anonymous; map every minimum necessary change to a concrete tracked edit; survive a single re-review by the original reviewers and a shepherd under PACMNET.
How do I install Conext Author Response in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill conext-author-response -a claude-code`. Or copy the skill folder (CoNEXT-Skills/skills/conext-author-response in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/conext-author-response in your project. Claude Code loads it when a task matches its description.
How do I install Conext Author Response in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill conext-author-response -a codex`. Or copy the skill folder (CoNEXT-Skills/skills/conext-author-response in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/conext-author-response in your project. Codex loads it when a task matches its description.
Can I use Conext 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 conext-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/conext-author-response, .gemini/skills/conext-author-response, .github/skills/conext-author-response and .opencode/skills/conext-author-response in your project.
What does Conext Author Response need to run?
SKILL.md names no scripts, command-line tools or credentials: Conext Author Response is instructions for the agent only.
Does Conext 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 Conext 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 Conext Author Response use?
Conext 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 Conext Author Response use?
About 1.3k tokens (SKILL.md is roughly 5.4k 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 Conext Author Response?
Skills that share tags, products or a category with Conext Author Response: Hypothesis Generation (spacering-net/codeg, 3.9k stars), GitHub Deep Research (bytedance/deer-flow, 84k stars), Nature Paper Card (Yuan1z0825/nature-skills, 47k stars) and Content Research Writer (weapp-tailwindcss/weapp-tailwindcss, 1.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Conext 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.