A skill your agent uses when revising an ACM SoCC paper for a cloud-scale problem an operator recognizes on the first page, a contribution at the systems-and-data intersection, evidence measured on…
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill socc-writing-style -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills socc-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/SoCC-Skills/skills/socc-writing-style .claude/skills/socc-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 "socc-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SoCC-Skills/skills/socc-writing-style into .claude/skills/socc-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "socc-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/SoCC-Skills/skills/socc-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 socc-writing-style -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills socc-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/SoCC-Skills/skills/socc-writing-style .agents/skills/socc-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 "socc-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SoCC-Skills/skills/socc-writing-style into .agents/skills/socc-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "socc-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 socc-writing-style -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills socc-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/SoCC-Skills/skills/socc-writing-style .cursor/skills/socc-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 "socc-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SoCC-Skills/skills/socc-writing-style into .cursor/skills/socc-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "socc-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 SoCC-Skills/skills/socc-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 socc-writing-style -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills socc-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/SoCC-Skills/skills/socc-writing-style .gemini/skills/socc-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 "socc-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SoCC-Skills/skills/socc-writing-style into .gemini/skills/socc-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "socc-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 socc-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 socc-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/SoCC-Skills/skills/socc-writing-style .github/skills/socc-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 "socc-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SoCC-Skills/skills/socc-writing-style into .github/skills/socc-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "socc-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 socc-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 socc-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/SoCC-Skills/skills/socc-writing-style .opencode/skills/socc-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 "socc-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SoCC-Skills/skills/socc-writing-style into .opencode/skills/socc-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "socc-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.
socc-writing-styleA skill your agent uses when revising an ACM SoCC paper for a cloud-scale problem an operator recognizes on the first page, a contribution at the systems-and-data intersection, evidence measured on…
Socc Writing Style is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when revising an ACM SoCC paper for a cloud-scale problem an operator recognizes on the first page, a contribution at the systems-and-data intersection, evidence measured on a real or realistic deployment with tail latency and cost as first-class, dual-anonymous wording, and disciplined use of the acmart 12-page budget.
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 Writing & Content, covering Brand voice and tone. 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.
Socc Writing Style loads about 1.3k tokens when it runs. Until then it costs about 86 tokens; SKILL.md has 581 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). 581 words, ~1,347 tokens.
.claude/skills/socc-writing-style/SKILL.md (or your agent's skills folder).Use this when revising the main paper. SoCC papers are read by a joint SIGMOD+SIGOPS audience, so they need a cloud-scale problem stated in operator terms on the first page and evidence a skeptic from either community trusts. The failure this skill prevents is a paper that reads like a pure-OS result with a cloud title glued on, or a benchmark with no systems contribution.
| Section | Job it must do | Common failure |
|---|---|---|
| Intro | Operator problem, inadequacy at scale, contribution, evidence preview, cloud payoff — first page | Leads with a technology trend, not a problem |
| Background/Motivation | Why current cloud systems fall short here, grounded in scale | Motivation by assertion, no measured gap |
| Design / Study | The mechanism or the measurement setup, reproducibly, with the testbed/trace | Method described too thinly to re-deploy |
| Evaluation | Throughput, tail, and cost vs. tuned baselines on a real/realistic system | Mean-only metrics; simulation standing in for deployment |
| Limitations | The external-validity limits that bite (provider, region, regimes) | Generic or absent |
| Related work | Delta-first positioning across systems and data venues | Catalog of citations with no contrast |
| Draft pattern | SoCC-safe rewrite |
|---|---|
| "Our system significantly improves performance." | "raises throughput X% and holds p99 within the SLO on a 200-node testbed vs. <tuned baseline>" |
| "We evaluate on a large workload." | "We replay a production trace of N invocations across M functions (provenance in §3)" |
| "Results show our approach works well." | "cuts provisioned instance-seconds Y% at equal p99 (Fig. 3); limits in §6" |
| "State-of-the-art performance." | Claim scoped to the workloads, scale, and cost model actually tested |
| "It scales." | "sustains the SLO from 10 to 200 nodes; beyond that, <named bottleneck>" |
[Tail] report p95/p99 (p99.9 where it bites), not just the mean; show the distribution
[Cost] state the pricing model; report instance-seconds or $ so the saving is checkable
[Baseline] tune every baseline with a documented, equal budget; an untuned baseline is a weakness
[Scale] show behavior across sizes; name the bottleneck where it stops scaling
[Limits] single-provider / one-region / tested-regime limits stated next to the resultsA draft with three mechanisms, twelve figures, and a sprawling background: keep the one mechanism that carries the contribution, the throughput/p99/cost figures that decide it, tuned baselines, and a limitations paragraph; move secondary regimes and full config sweeps to the artifact with forward references; cut background to the measured gap the paper closes. The test of a good cut: a reviewer should be able to answer "what did it improve, at what tail and cost, versus what baseline, and where does it stop working?" from the body alone.
[Writing diagnosis] clear / under-motivated / mean-only / over-claimed / over-scoped
[First-page fix] <new framing leading with the operator problem in cost/tail terms>
[Evidence audit] <claim -> deployment/trace -> tail+cost reported -> tuned baseline? yes/no>
[Limitations fix] <external-validity limit that bites -> where to state it>
[Anonymity edits] <system/cluster/trace names / self-citations / links to rewrite>© 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 SoCC-Skills/skills/socc-writing-style of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Socc 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 |
|---|---|---|---|---|---|---|
| Socc Writing Style this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.3k | Automated safety check: Pass | MIT | |
| Narrative Enablement Kitaaron-he-zhu/aaron-marketing-skills | 2.9k | — | ~3.4k | Automated safety check: Pass | Apache-2.0 | |
| Avoid AI Writingconorbronsdon/avoid-ai-writing | 4.9k | 3 repos | ~8.1k | Automated safety check: Pass | MIT | |
| BrandOhh-889/skyroc | 795 | 13 repos | ~733 | Automated safety check: Pass | MIT | |
| Khazix WeChat Article WriterKKKKhazix/khazix-skills | 21k | 1 repos | ~2.9k | Automated safety check: Pass | MIT | |
| Writing Guidelinesvercel-labs/agent-skills | 32k | 7 repos | ~309 | Automated safety check: Pass | None |
aaron-he-zhu/aaron-marketing-skills
A skill your agent uses when the user asks to "make everyone tell the same story", "write our elevator pitch ladder", or "build a spokesperson Q&A and approved boilerplate pack"; derives from the…
conorbronsdon/avoid-ai-writing
Audit and rewrite content to remove AI writing patterns ("AI-isms").
Ohh-889/skyroc
Brand voice, visual identity, messaging frameworks, asset management, brand consistency.
KKKKhazix/khazix-skills
Writes long-form WeChat official account articles in the personal style of the Khazix account, from briefs, links, PDFs or rough notes, with a topic quality check.
vercel-labs/agent-skills
Review docs/prose for Writing Guidelines compliance. An agent skill from vercel-labs/agent-skills.
theclaymethod/unslop
Removes AI writing tells from prose through an audit-first flow, routing to a two-pass rewrite, a report-only cleanup, voice teaching or mimicry depending on the sub-command used.
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 an ACM SoCC paper for a cloud-scale problem an operator recognizes on the first page, a contribution at the systems-and-data intersection, evidence measured on…. Socc Writing Style is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when revising an ACM SoCC paper for a cloud-scale problem an operator recognizes on the first page, a contribution at the systems-and-data intersection, evidence measured on a real or realistic deployment with tail latency and cost as first-class, dual-anonymous wording, and disciplined use of the acmart 12-page budget.
Socc Writing Style fits situations like: revising an ACM SoCC paper for a cloud-scale problem an operator recognizes on the first page; A contribution at the systems-and-data intersection; evidence measured on a real; realistic deployment with tail latency and cost as first-class.
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill socc-writing-style -a claude-code`. Or copy the skill folder (SoCC-Skills/skills/socc-writing-style in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/socc-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 socc-writing-style -a codex`. Or copy the skill folder (SoCC-Skills/skills/socc-writing-style in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/socc-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 socc-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/socc-writing-style, .gemini/skills/socc-writing-style, .github/skills/socc-writing-style and .opencode/skills/socc-writing-style in your project.
SKILL.md names no scripts, command-line tools or credentials: Socc 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.
Socc 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.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.
Skills that share tags, products or a category with Socc Writing Style: Narrative Enablement Kit (aaron-he-zhu/aaron-marketing-skills, 2.9k stars), Avoid AI Writing (conorbronsdon/avoid-ai-writing, 4.9k stars), Brand (Ohh-889/skyroc, 795 stars) and Khazix WeChat Article Writer (KKKKhazix/khazix-skills, 21k 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.
