A skill your agent uses when revising an ACM PODS paper for a precise model and result on the first page, exact theorem statements with matching bounds, complete and self-contained proofs (body plus…
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pods-writing-style -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills pods-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/PODS-Skills/skills/pods-writing-style .claude/skills/pods-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 "pods-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PODS-Skills/skills/pods-writing-style into .claude/skills/pods-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pods-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/PODS-Skills/skills/pods-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 pods-writing-style -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills pods-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/PODS-Skills/skills/pods-writing-style .agents/skills/pods-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 "pods-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PODS-Skills/skills/pods-writing-style into .agents/skills/pods-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pods-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 pods-writing-style -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills pods-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/PODS-Skills/skills/pods-writing-style .cursor/skills/pods-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 "pods-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PODS-Skills/skills/pods-writing-style into .cursor/skills/pods-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pods-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 PODS-Skills/skills/pods-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 pods-writing-style -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills pods-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/PODS-Skills/skills/pods-writing-style .gemini/skills/pods-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 "pods-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PODS-Skills/skills/pods-writing-style into .gemini/skills/pods-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pods-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 pods-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 pods-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/PODS-Skills/skills/pods-writing-style .github/skills/pods-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 "pods-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PODS-Skills/skills/pods-writing-style into .github/skills/pods-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pods-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 pods-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 pods-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/PODS-Skills/skills/pods-writing-style .opencode/skills/pods-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 "pods-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PODS-Skills/skills/pods-writing-style into .opencode/skills/pods-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pods-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.
pods-writing-styleA skill your agent uses when revising an ACM PODS paper for a precise model and result on the first page, exact theorem statements with matching bounds, complete and self-contained proofs (body plus…
Pods Writing Style is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when revising an ACM PODS paper for a precise model and result on the first page, exact theorem statements with matching bounds, complete and self-contained proofs (body plus at-submission appendix), honest assumptions and open cases, double-anonymous wording, and disciplined use of the acmsmall 15-page budget.
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 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.
Pods Writing Style loads about 1.4k tokens when it runs. Until then it costs about 84 tokens; SKILL.md has 604 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). 604 words, ~1,354 tokens.
.claude/skills/pods-writing-style/SKILL.md (or your agent's skills folder).Use this when revising the main paper. PODS papers are read by database theoreticians, so they need a precise model and a precise result stated on the first page and proofs a reviewer can verify. The failure this skill prevents is a paper whose interesting idea is buried under systems language or whose theorems are stated loosely enough that no one can tell what was proved.
| Section | Job it must do | Common failure |
|---|---|---|
| Intro | Problem, model, result, tightness, what it settles — first page | Leads with a system or a trend, not a model and a theorem |
| Preliminaries | Fix the data/query model, notation, and the exact problem | Definitions too informal for the theorem to be unambiguous |
| Main results | State each theorem precisely; give the key proof ideas | Theorems stated so loosely the contribution is unclear |
| Upper bound | The algorithm/construction + its correctness and complexity proof | Complexity asserted, not proved; hidden dependence on parameters |
| Lower bound | The hardness reduction or impossibility, with its assumptions | No matching lower bound, so optimality is unproven |
| Related work | Delta-first positioning against PODS/ICDT/logic literature | A citation catalog with no contrast of results |
| Draft pattern | PODS-safe rewrite |
|---|---|
| "Our algorithm is very efficient." | "runs in O(n log n) data complexity (Thm 3), matching the Ω(n log n) lower bound of §5" |
| "The problem is hard." | "consistent query answering for this class is coNP-complete in data complexity (Thm 2)" |
| "We handle a broad class of queries." | "we prove the dichotomy for all self-join-free conjunctive queries; self-joins remain open (§7)" |
| "Experiments confirm our approach." | "we give a matching lower bound; a small empirical check (§6) illustrates the constants" |
| "It is easy to see that..." | Replace with the actual argument or a pointer to the appendix proof |
[Model] fix the data model, query class, and cost/complexity measure before any theorem
[Quantifiers] say exactly what is universal and what is existential; data vs. combined complexity
[Tightness] pair each upper bound with a lower bound or state the gap as an open problem
[Assumptions] name every conjecture a bound rests on (e.g. OMv, ETH); never present conditional
hardness as unconditional
-> a reader should be able to restate your main theorem exactly from the abstract aloneA draft with an upper-bound algorithm, a lower-bound reduction, three corollaries, and a long preliminaries section: keep both main theorems and their proof ideas in the body, move the full reduction gadget and the corollary proofs to the appendix with forward references, and cut preliminaries to exactly the definitions the theorems use. The test of a good cut: a reviewer should be able to state what was proved and why it is tight from the body alone, and find every full proof in the appendix.
[Writing diagnosis] clear / under-specified model / loose theorems / gap unstated / over-scoped
[First-page fix] <new framing leading with the model and the exact result>
[Theorem audit] <theorem -> hypotheses stated? complexity exact? proof located? tight?>
[Tightness fix] <where a matching lower bound or an honest open-case statement must be added>
[Anonymity edits] <named systems / self-citations / acknowledgements 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 PODS-Skills/skills/pods-writing-style of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Pods 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 |
|---|---|---|---|---|---|---|
| Pods Writing Style this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Crim Writing Stylefranklee16/academic-research-skills | 223 | 1 repos | ~975 | Automated safety check: Pass | None | |
| Est Writing Stylefranklee16/academic-research-skills | 223 | 1 repos | ~798 | Automated safety check: Pass | None | |
| Jaar Writing Stylefranklee16/academic-research-skills | 223 | 1 repos | ~760 | Automated safety check: Pass | None | |
| Jcf Writing Stylefranklee16/academic-research-skills | 223 | 1 repos | ~669 | Automated safety check: Pass | None | |
| Joc Writing Stylefranklee16/academic-research-skills | 223 | 1 repos | ~873 | Automated safety check: Pass | None |
franklee16/academic-research-skills
A skill your agent uses when drafting or polishing a Criminology (ASC / Wiley) manuscript so it reads for an interdisciplinary criminology audience, follows the journal's APA-based style, and uses…
franklee16/academic-research-skills
A skill your agent uses when drafting or polishing the prose of an Environmental Science & Technology (ES&T) manuscript so it reads for a multidisciplinary audience in ACS style and fits the…
franklee16/academic-research-skills
A skill your agent uses when drafting or polishing the prose of a Journal of the American Academy of Religion (JAAR) article so it is clear, analytic, gender-neutral, and readable across the study…
franklee16/academic-research-skills
A skill your agent uses when drafting or polishing prose for a Journal of Corporate Finance (JCF) manuscript — the ≤250-word abstract, 1–7 keywords, author-date (Harvard) in-text citations, and the…
franklee16/academic-research-skills
A skill your agent uses when drafting or polishing a Journal of Communication (JoC) manuscript so it reads for the whole field, follows APA 7th edition, and fits the limits (main document <= 35…
franklee16/academic-research-skills
A skill your agent uses when polishing the prose of a Journal of Political Economy (JPE) manuscript into its spare, analytical, economics-first register.
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 PODS paper for a precise model and result on the first page, exact theorem statements with matching bounds, complete and self-contained proofs (body plus…. Pods Writing Style is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when revising an ACM PODS paper for a precise model and result on the first page, exact theorem statements with matching bounds, complete and self-contained proofs (body plus at-submission appendix), honest assumptions and open cases, double-anonymous wording, and disciplined use of the acmsmall 15-page budget.
Pods Writing Style fits situations like: revising an ACM PODS paper for a precise model and result on the first page; exact theorem statements with matching bounds; complete and self-contained proofs (body plus at-submission appendix); honest assumptions and open cases.
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pods-writing-style -a claude-code`. Or copy the skill folder (PODS-Skills/skills/pods-writing-style in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/pods-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 pods-writing-style -a codex`. Or copy the skill folder (PODS-Skills/skills/pods-writing-style in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/pods-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 pods-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/pods-writing-style, .gemini/skills/pods-writing-style, .github/skills/pods-writing-style and .opencode/skills/pods-writing-style in your project.
SKILL.md names no scripts, command-line tools or credentials: Pods 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.
Pods 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.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 Pods Writing Style: Crim Writing Style (franklee16/academic-research-skills, 223 stars), Est Writing Style (franklee16/academic-research-skills, 223 stars), Jaar Writing Style (franklee16/academic-research-skills, 223 stars) and Jcf 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.
