Individual skill
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.
PODS-Skills/skills/pods-writing-style/SKILL.md
Source commit 932eb23331721b16e967c59f093781be1928b498
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Network or broad shell
- Last checked
- Nov 9, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,404
- Repository last updated
- Sep 27, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- academic-writing Repository topic
- agent-skills Repository topic
- journal Repository topic
- academic-research Repository topic
- ai-agents Repository topic
- anthropic Repository topic
- awesome-list Repository topic
- claude Repository topic
- claude-code Repository topic
- economics Repository topic
- finance Derived category
- writing Derived category
- research Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 5,428 bytes
Read excerpt
# 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