Hypothesis Generation
spacering-net/codeg
Structured hypothesis formulation from observations. An agent skill from spacering-net/codeg.
A skill your agent uses when reasoning about how a SIGMOD research paper moves through a PACMMOD round, covering double-anonymous CMT reviewing, the author feedback phase, accept/reject/revision…
Install Sigmod Review Process
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sigmod-review-process -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sigmod-review-process --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/SIGMOD-Skills/skills/sigmod-review-process .claude/skills/sigmod-review-process && 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 "sigmod-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SIGMOD-Skills/skills/sigmod-review-process into .claude/skills/sigmod-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sigmod-review-process", 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/SIGMOD-Skills/skills/sigmod-review-processType 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 sigmod-review-process -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sigmod-review-process --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/SIGMOD-Skills/skills/sigmod-review-process .agents/skills/sigmod-review-process && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "sigmod-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SIGMOD-Skills/skills/sigmod-review-process into .agents/skills/sigmod-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sigmod-review-process", 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 sigmod-review-process -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sigmod-review-process --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/SIGMOD-Skills/skills/sigmod-review-process .cursor/skills/sigmod-review-process && 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 "sigmod-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SIGMOD-Skills/skills/sigmod-review-process into .cursor/skills/sigmod-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sigmod-review-process", 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 SIGMOD-Skills/skills/sigmod-review-process--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 sigmod-review-process -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sigmod-review-process --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/SIGMOD-Skills/skills/sigmod-review-process .gemini/skills/sigmod-review-process && 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 "sigmod-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SIGMOD-Skills/skills/sigmod-review-process into .gemini/skills/sigmod-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sigmod-review-process", 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 sigmod-review-processInstalls 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 sigmod-review-process -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/SIGMOD-Skills/skills/sigmod-review-process .github/skills/sigmod-review-process && 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 "sigmod-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SIGMOD-Skills/skills/sigmod-review-process into .github/skills/sigmod-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sigmod-review-process", 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 sigmod-review-process -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 sigmod-review-process --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/SIGMOD-Skills/skills/sigmod-review-process .opencode/skills/sigmod-review-process && 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 "sigmod-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SIGMOD-Skills/skills/sigmod-review-process into .opencode/skills/sigmod-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sigmod-review-process", 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
sigmod-review-process- GitHub stars
- 1.2k
- Token cost
- ~1.5k tokens
- SKILL.md length
- 711 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when reasoning about how a SIGMOD research paper moves through a PACMMOD round, covering double-anonymous CMT reviewing, the author feedback phase, accept/reject/revision…
- Reasoning about how a SIGMOD research paper moves through a PACMMOD round
- SKILL.md covers Anatomy of a round (SIGMOD…, The three verdicts, decoded, Who is reading and Feedback phase leverage, plus 5 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Covering double-anonymous CMT reviewing
What it does
Sigmod Review Process is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when reasoning about how a SIGMOD research paper moves through a PACMMOD round, covering double-anonymous CMT reviewing, the author feedback phase, accept/reject/revision verdicts, the one-month revision window, the 12-month rejection embargo, and how database PC members actually weigh evidence.
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.
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
- Reasoning about how a SIGMOD research paper moves through a PACMMOD round
- Covering double-anonymous CMT reviewing
- The author feedback phase
- Accept/reject/revision verdicts
Example prompts
- “/sigmod-review-process”
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
Sigmod Review Process loads about 1.5k tokens when it runs. Until then it costs about 81 tokens; SKILL.md has 711 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). 711 words, ~1,519 tokens.
Download SKILL.mdSave it as
.claude/skills/sigmod-review-process/SKILL.md (or your agent's skills folder).- name
- sigmod-review-process
- description
- Use when reasoning about how a SIGMOD research paper moves through a PACMMOD round, covering double-anonymous CMT reviewing, the author feedback phase, accept/reject/revision verdicts, the one-month revision window, the 12-month rejection embargo, and how database PC members actually weigh evidence.
SIGMOD Review Process
A SIGMOD research submission enters a journal pipeline with a conference cadence: papers submitted to a PACMMOD round are reviewed double-anonymously through Microsoft CMT, authors get a mid-round feedback window, and the first verdict is three-valued — accept, reject, or revise. Understanding which lever moves which outcome is most of review-stage strategy. Mechanics shift by cycle; reconfirm against the live CFP before relying on any date.
Anatomy of a round (SIGMOD 2027 Round 3 as the concrete case)
Jul 10, 2026 Abstract + conflict declarations close
Jul 17, 2026 Paper deadline (11:59 PM AoE)
Sep 10-17 Author feedback phase: reviews visible, short reply window
Oct 19, 2026 Verdict: accept / reject / major or minor revision
Nov 19, 2026 Revised paper + 4-page letter due (revision cases)
Dec 12, 2026 Final accept/reject on revisionsRoughly three months from PDF to first verdict, five to final — faster than most journals, slower than a rebuttal-only conference, and repeatable four times a year.
The three verdicts, decoded
| Verdict | What it means operationally | Author's real decision |
|---|---|---|
| Accept | Into the round's PACMMOD issue; camera-ready port begins | None — execute |
| Revision (minor/major) | A contract: enumerated requirements, +1 page, one month | Can every requirement land in 30 days? |
| Reject | 12-month embargo from SIGMOD research track (≈3 rounds) | PVLDB / ICDE / rework, not a quick resubmit |
Two consequences deserve emphasis. First, a revision verdict is genuinely
winnable — the requirements are written down, and reviewers judge compliance
rather than re-litigating taste. Second, the embargo makes "just resubmit
next round" impossible, so a rejected SIGMOD paper's next stop is usually a
different venue (see sigmod-topic-selection).
Who is reading
The PC is dominated by database systems researchers and industrial engine builders. Predictable evaluation reflexes:
- They benchmark mentally: the first skim looks for the workload table and the hardware paragraph before the design section gets full attention.
- They know the baselines personally — sometimes literally, as authors or maintainers — so an untuned competitor is recognized on sight.
- Architecture claims are audited against systems they have built: "this cannot be lock-free as described" is a common decisive comment.
- Novelty is measured against both recent PACMMOD/PVLDB output and decades of systems history; rediscovering a 1990s technique under a new name is a classic kill.
Feedback phase leverage
The mid-round window is short and asymmetric: reviewers have already scored, and you are trying to change specific minds before the PC discussion. Highest expected value, in order: correcting an outright factual misreading; answering a direct question with a pointer to a specific table; resolving an apparent contradiction between two of your own sections. Near-zero value: arguing significance, promising future work, or thanking reviewers at length inside a tight character budget.
Show full SKILL.md (324 more words)Show less
Reading a split panel
- One detailed negative review plus shallow positives → the verdict follows the detailed one; answer it line by line in the feedback phase.
- Universal "interesting but evaluation thin" → expect major revision; start the missing experiments before the verdict arrives.
- A correctness objection from a builder of a rival system → treat as the round's decisive issue even if other scores are high.
- Complaints about clarity of the problem statement → often masks a fit problem; consider whether the framing buried the data-management core.
Round vocabulary, decoded
Terms that trip up newcomers to the PACMMOD model:
- Round — one of the year's submission batches; your paper lives its whole life inside a single round unless rejected.
- Issue — the PACMMOD journal number your round's acceptances publish in; citable independently of the conference.
- Feedback phase — the mid-round reply window; not a rebuttal in the score-flipping sense, and not the revision.
- Revision — a formal verdict with enumerated requirements, not an informal second chance; compliance is what gets re-reviewed.
- Embargo — the 12-month bar on returning to the research track after rejection or late withdrawal.
- Shepherd — when assigned, the PC member who verifies promised camera-ready changes; treat their notes as binding.
Etiquette with teeth
Confidentiality and anonymity bind for the whole round: no tweeting the submission, no updating a named preprint mid-round in a way that links to the anonymous version, no contacting suspected reviewers. Violations here are policy matters for chairs, not style points.
After the final decision
Close the loop regardless of outcome. On acceptance, archive the full review thread beside the paper — the shepherding and ARI stages quote it. On rejection, hold a one-hour post-mortem within a week while memory is fresh: classify each objection as fixable-evidence, fixable-writing, or fit, and let that classification pick the next venue rather than pride or sunk cost. Reviews from a SIGMOD round are unusually actionable input for a PVLDB or ICDE resubmission precisely because the reviewer pools overlap.
Output format
[Round position] submitted / feedback window / awaiting verdict / revising
[Panel read] per-reviewer stance and the decisive reviewer
[Verdict forecast] accept / revision / reject, with the driving issue
[Feedback plan] top corrections worth the character budget
[Revision feasibility] 30-day workload if a revision lands
[Embargo contingency] next venue if rejected© 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 SIGMOD-Skills/skills/sigmod-review-process of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Sigmod Review Process 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 |
|---|---|---|---|---|---|---|
| Sigmod Review Process this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.5k | 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 Sigmod Review Process
What does Sigmod Review Process do?
A skill your agent uses when reasoning about how a SIGMOD research paper moves through a PACMMOD round, covering double-anonymous CMT reviewing, the author feedback phase, accept/reject/revision…. Sigmod Review Process is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when reasoning about how a SIGMOD research paper moves through a PACMMOD round, covering double-anonymous CMT reviewing, the author feedback phase, accept/reject/revision verdicts, the one-month revision window, the 12-month rejection embargo, and how database PC members actually weigh evidence.
When should I use Sigmod Review Process?
Sigmod Review Process fits situations like: reasoning about how a SIGMOD research paper moves through a PACMMOD round; covering double-anonymous CMT reviewing; the author feedback phase; accept/reject/revision verdicts.
How do I install Sigmod Review Process in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sigmod-review-process -a claude-code`. Or copy the skill folder (SIGMOD-Skills/skills/sigmod-review-process in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/sigmod-review-process in your project. Claude Code loads it when a task matches its description.
How do I install Sigmod Review Process in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sigmod-review-process -a codex`. Or copy the skill folder (SIGMOD-Skills/skills/sigmod-review-process in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/sigmod-review-process in your project. Codex loads it when a task matches its description.
Can I use Sigmod Review Process 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 sigmod-review-process -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/sigmod-review-process, .gemini/skills/sigmod-review-process, .github/skills/sigmod-review-process and .opencode/skills/sigmod-review-process in your project.
What does Sigmod Review Process need to run?
SKILL.md names no scripts, command-line tools or credentials: Sigmod Review Process is instructions for the agent only.
Does Sigmod Review Process 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 Sigmod Review Process 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 Sigmod Review Process use?
Sigmod Review Process 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 Sigmod Review Process use?
About 1.5k tokens (SKILL.md is roughly 6.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 Sigmod Review Process?
Skills that share tags, products or a category with Sigmod Review Process: 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 Sigmod Review Process?
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.