Academic Venue Research
joshua-zyy/academic-paper-writer
Research target venue requirements and writing style for CS/AI/ML papers.
A skill your agent uses when revising a SIGMOD research paper's prose and structure, covering the data-management framing readers expect on page one, running examples and architecture figures…
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sigmod-writing-style -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sigmod-writing-style --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-writing-style .claude/skills/sigmod-writing-style && 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-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SIGMOD-Skills/skills/sigmod-writing-style into .claude/skills/sigmod-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sigmod-writing-style", 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-writing-styleType 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-writing-style -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sigmod-writing-style --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-writing-style .agents/skills/sigmod-writing-style && 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-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SIGMOD-Skills/skills/sigmod-writing-style into .agents/skills/sigmod-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sigmod-writing-style", 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-writing-style -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sigmod-writing-style --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-writing-style .cursor/skills/sigmod-writing-style && 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-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SIGMOD-Skills/skills/sigmod-writing-style into .cursor/skills/sigmod-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sigmod-writing-style", 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-writing-style--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-writing-style -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sigmod-writing-style --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-writing-style .gemini/skills/sigmod-writing-style && 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-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SIGMOD-Skills/skills/sigmod-writing-style into .gemini/skills/sigmod-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sigmod-writing-style", 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-writing-styleInstalls 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-writing-style -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-writing-style .github/skills/sigmod-writing-style && 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-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SIGMOD-Skills/skills/sigmod-writing-style into .github/skills/sigmod-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sigmod-writing-style", 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-writing-style -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-writing-style --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-writing-style .opencode/skills/sigmod-writing-style && 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-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SIGMOD-Skills/skills/sigmod-writing-style into .opencode/skills/sigmod-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sigmod-writing-style", 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.
sigmod-writing-styleA skill your agent uses when revising a SIGMOD research paper's prose and structure, covering the data-management framing readers expect on page one, running examples and architecture figures…
Sigmod Writing Style is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when revising a SIGMOD research paper's prose and structure, covering the data-management framing readers expect on page one, running examples and architecture figures, scoping systems claims to measured workloads, third-person anonymity phrasing, and fitting a systems argument into 12 ACM-template pages.
Its SKILL.md is about 1.4k 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, covering Brand voice and tone and Programmatic SEO. 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.
Read from SKILL.md and the folder at commit 932eb23. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Sigmod Writing Style loads about 1.4k tokens when it runs. Until then it costs about 83 tokens; SKILL.md has 653 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from brycewang-stanford/Awesome-Journal-Skills at commit 932eb23, republished under its MIT licence (© brycewang-stanford). 653 words, ~1,396 tokens.
.claude/skills/sigmod-writing-style/SKILL.md (or your agent's skills folder).SIGMOD prose is engineering argumentation: a reader who builds database systems should finish page one knowing what breaks today, what mechanism you built, and what measurement proves it. The 12-page ACM-template budget (references excluded) is generous by conference standards, which removes the usual excuse — at this venue, missing detail reads as concealment rather than compression.
Within the first page, in some order: the workload or application pressure that makes the problem real now; why the incumbent technique fails at that pressure point (with a number if possible); the mechanism in one concrete sentence; the headline measured result with its setting attached; and the contribution list phrased as artifacts a reader can verify — an algorithm, a system component, a proof, an evaluation.
A first paragraph that opens with "Data volumes are growing exponentially" has already spent its welcome; open instead inside the specific bottleneck.
The single most recognizable SIGMOD stylistic device: one small, concrete example — a table, a query, a workload snippet — introduced in Section 1 or 2 and threaded through the design sections. Every operator, data structure, or protocol step is shown acting on it. Papers that explain a join algorithm purely in symbols, when three rows and two tables would show it, get "hard to follow" reviews from people fully capable of reading the symbols.
| Draft claim | Survives review as |
|---|---|
| "Up to 10x faster than X" | "10x on skewed reads at sf=100; 1.3x on uniform writes (Fig 8)" |
| "Scales linearly" | "Near-linear to 64 cores; contention flattens beyond (Fig 9)" |
| "Negligible overhead" | "3-6% p99 latency overhead across the mixes tested (Tab 4)" |
| "Guarantees consistency" | "Snapshot isolation; serializable with Sec 4.3's lock, at cost Y" |
| "First system to..." | Scoped precisely, or cut — a PC full of builders will find prior art |
The pattern: attach every superlative to a figure, a workload, and a boundary. Database reviewers respect a stated limitation and hunt an unstated one.
sigmod-supplementary), but the invariant itself
must be stated in the body, precisely.Write about your own prior systems in the third person, and scrub the tells: "we extend the engine of [12]" not "we extend our engine [12]"; no internal codenames that a search engine maps to a company; no "deployed at a major cloud provider" phrasing that narrows the author set to two teams. These rules bind for the entire multi-round review, including revised text.
p1 Problem, failure of incumbents, mechanism, headline number
p2-3 Background + running example; the example does the teaching
p4-7 Design: architecture figure, core algorithm, invariants
p8 Correctness/complexity sketch; report carries the full proof
p9-11 Evaluation: setup table first, then claims in figure order
p12 Related work in contrast form + limitations + conclusionTreat the evaluation-setup half page as immovable: hardware, datasets, workloads, baselines, tuning provenance. Cutting it to rescue a design subsection trades a clarity comment for an evidence objection — a bad trade in this reviewer pool.
<mechanism> for <setting>"); earn the name by
making the mechanism clause precise, not grand.[Page-one audit] pressure / incumbent failure / mechanism / number present?
[Running example] exists and threads through design sections yes/no
[Claim ledger] each superlative -> figure + workload + boundary
[Voice sweep] third-person self-references, codename leaks
[Budget check] section allocation vs. the 12-page plan
[Priority rewrites] ordered list© brycewang-stanford, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in SIGMOD-Skills/skills/sigmod-writing-style of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Sigmod Writing Style 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 Writing Style this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Academic Venue Researchjoshua-zyy/academic-paper-writer | 115 | — | ~626 | Automated safety check: Pass | MIT | |
| Agsy Writing Stylefranklee16/academic-research-skills | 223 | 1 repos | ~1k | Automated safety check: Pass | None | |
| Artbull Writing Style And Citationfranklee16/academic-research-skills | 223 | 1 repos | ~848 | Automated safety check: Pass | None | |
| Ectheory Writing Stylefranklee16/academic-research-skills | 223 | 1 repos | ~874 | Automated safety check: Pass | None | |
| Io Writing Stylefranklee16/academic-research-skills | 223 | 1 repos | ~1.1k | Automated safety check: Pass | None |
joshua-zyy/academic-paper-writer
Research target venue requirements and writing style for CS/AI/ML papers.
franklee16/academic-research-skills
A skill your agent uses when drafting or polishing an Agricultural Systems (AgSy) manuscript so it reads clearly for a systems-science audience, follows the journal's format, and meets front-matter…
franklee16/academic-research-skills
A skill your agent uses when polishing prose and formatting citations for an Art Bulletin article to The Chicago Manual of Style — endnotes (not author-date), full credit-line captions, and…
franklee16/academic-research-skills
A skill your agent uses to polish the prose, notation, and proof exposition of an Econometric Theory (ET) manuscript — theorem-proof clarity, consistent notation, APA author-date references, and ET…
franklee16/academic-research-skills
A skill your agent uses when drafting or polishing an International Organization (IO) manuscript so it reads for international-relations scholars across paradigms, fits the word caps (Research…
franklee16/academic-research-skills
A skill your agent uses when drafting or polishing prose for a Journal of Applied Econometrics (JAE) manuscript to its house conventions — a 100-word citation-free summary, up to six keywords…
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running and reporting the analysis for an Annals of the American Association of Geographers manuscript — spatial statistics and modeling, remote-sensing accuracy, or…
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when positioning an Annals of the American Association of Geographers manuscript in the literature — engaging geographic scholarship across the relevant area and the…
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when responding to an Annals of the American Association of Geographers decision letter (major/minor revision) — building a point-by-point response to the subject editor and…
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when defending the research design of an Annals of the American Association of Geographers manuscript — spatial/quantitative analysis and GIScience, remote-sensing and…
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when you need to understand how the Annals of the American Association of Geographers evaluates a manuscript — double-anonymous review routed through a subject editor by…
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running the final pre-submission preflight for the Annals of the American Association of Geographers via ScholarOne Manuscripts — area/article-type selection…
Categories
A skill your agent uses when revising a SIGMOD research paper's prose and structure, covering the data-management framing readers expect on page one, running examples and architecture figures…. Sigmod Writing Style is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when revising a SIGMOD research paper's prose and structure, covering the data-management framing readers expect on page one, running examples and architecture figures, scoping systems claims to measured workloads, third-person anonymity phrasing, and fitting a systems argument into 12 ACM-template pages.
Sigmod Writing Style fits situations like: revising a SIGMOD research papers prose and structure; covering the data-management framing readers expect on page one; running examples and architecture figures; scoping systems claims to measured workloads.
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sigmod-writing-style -a claude-code`. Or copy the skill folder (SIGMOD-Skills/skills/sigmod-writing-style in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/sigmod-writing-style in your project. Claude Code loads it when a task matches its description.
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sigmod-writing-style -a codex`. Or copy the skill folder (SIGMOD-Skills/skills/sigmod-writing-style in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/sigmod-writing-style in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sigmod-writing-style -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-writing-style, .gemini/skills/sigmod-writing-style, .github/skills/sigmod-writing-style and .opencode/skills/sigmod-writing-style in your project.
SKILL.md names no scripts, command-line tools or credentials: Sigmod Writing Style is instructions for the agent only.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Sigmod Writing Style is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.4k tokens (SKILL.md is roughly 5.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Sigmod Writing Style: Academic Venue Research (joshua-zyy/academic-paper-writer, 115 stars), Agsy Writing Style (franklee16/academic-research-skills, 223 stars), Artbull Writing Style And Citation (franklee16/academic-research-skills, 223 stars) and Ectheory Writing Style (franklee16/academic-research-skills, 223 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,231 GitHub stars. The repository holds 2,387 skills in this directory. The repository was last updated on September 27, 2026.
Source: brycewang-stanford/Awesome-Journal-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.