pods-writing-style
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.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pods-writing-style --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# PODS Writing Style 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. ## Revision rules - **Lead with the model and the result:** the data-management problem, the exact model (data/query model, complexity measure, cost model), the result (a bound, a dichotomy, a semantics, an optimal algorithm), why it is tight or complete, and what it settles — all on the first page. - **State theorems precisely.** Every theorem names its hypotheses, its model, and its exact quantities (data vs. combined complexity, worst-case vs. parameterized, exact vs. approximate). A vague "our problem is hard" is not a PODS theorem. - **Match upper and lower bounds.** The strongest PODS papers close the gap; where you cannot, say so and state the open case rather than hiding it behind "we leave this to future work" without a precise statement. - **Every stated result has a comple
- Revision rules
- Theory-paper skeleton
- Sentence-level rewrites
- Statement discipline
- Vignette: compressing a two-bound paper
- Output format
What does the pods-writing-style skill do?
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.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pods-writing-style --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From brycewang-stanford/Awesome-Journal-Skills, a repository with 909 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.