New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Podc Writing Style

by brycewang-stanford in brycewang-stanford/Awesome-Journal-Skills

A skill your agent uses when drafting or revising the body of an ACM PODC paper — building the distributed-theory skeleton (an explicit model box, the result stated as a theorem up front, a proof…

MITAuto-check passedWriting & Content

Install Podc Writing Style

skills CLI
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill podc-writing-style -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install brycewang-stanford/Awesome-Journal-Skills podc-writing-style --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/PODC-Skills/skills/podc-writing-style .claude/skills/podc-writing-style && rm -rf skills-src

Use ~/.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/

Facts

Skill name
podc-writing-style
GitHub stars
1.2k
Token cost
~1.5k tokens
SKILL.md length
670 words
Files
1
Skills in repo
2,387
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when drafting or revising the body of an ACM PODC paper — building the distributed-theory skeleton (an explicit model box, the result stated as a theorem up front, a proof…

  • Works in 5 steps: The problem inside a fixed model —… → Why the state of the art leaves a gap —… → The result, as a theorem — an explicit… → …
  • Revising the body of an ACM PODC paper — building the distributed-theory skeleton (an explicit model box
  • SKILL.md covers The first-page arc, The model box is non-negotiable, Proof architecture and The 10-page-merits discipline, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Podc Writing Style is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when drafting or revising the body of an ACM PODC paper — building the distributed-theory skeleton (an explicit model box, the result stated as a theorem up front, a proof architecture the reader can navigate, and the 10-page-merits discipline) so the merits case lands within the first 10 pages a PODC committee is guaranteed to read.

Its SKILL.md is about 1.5k 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.

When your agent uses it

  • Revising the body of an ACM PODC paper — building the distributed-theory skeleton (an explicit model box
  • The result stated as a theorem up front
  • A proof architecture the reader can navigate
  • The 10-page-merits discipline) so the merits case lands within the first 10 pages a PODC committee is guaranteed to read

Example prompts

  • “/podc-writing-style”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. The problem inside a fixed model — network (message-passing / shared memory), timing
  2. Why the state of the art leaves a gap — the best prior bound and exactly what it does not
  3. The result, as a theorem — an explicit bound and the resilience/assumptions it holds at, not
  4. Whether it is tight — a matching lower bound elevates an algorithm to an optimality result,
  5. The proof idea in one breath — name the technique (valency, indistinguishability, potential

What it can do on your machine

Read from SKILL.md and the folder at commit 932eb23. It shows what the files ask for, not the result of running them.

  • Tool permissions

    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.

  • Runs code

    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.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Podc Writing Style loads about 1.5k tokens when it runs. Until then it costs about 90 tokens; SKILL.md has 670 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~90
When it runs · the whole SKILL.md, loaded when a task matches
~1.5k

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.

Safety

Auto-check passed

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.

SKILL.md

The full file from brycewang-stanford/Awesome-Journal-Skills at commit 932eb23, republished under its MIT licence (© brycewang-stanford). 670 words, ~1,523 tokens.

Download SKILL.mdSave it as .claude/skills/podc-writing-style/SKILL.md (or your agent's skills folder).
name
podc-writing-style
description
Use when drafting or revising the body of an ACM PODC paper — building the distributed-theory skeleton (an explicit model box, the result stated as a theorem up front, a proof architecture the reader can navigate, and the 10-page-merits discipline) so the merits case lands within the first 10 pages a PODC committee is guaranteed to read.

PODC Writing Style

Write for a reader who will check your proof. A PODC paper is a mathematical argument about a distributed model, and the committee decides on the first 10 pages after the title page (the merits budget). The house style is therefore front-loaded: fix the model, state the result, then prove it — with the proof organized so a reviewer can find and verify each step.

The first-page arc

Lead with the result inside its model, in this order (see the worked example in resources/worked-examples/01-introduction.md):

  1. The problem inside a fixed model — network (message-passing / shared memory), timing (synchronous / asynchronous / partial synchrony), fault model (crash / Byzantine / self-stabilizing), adversary (adaptive / oblivious), and the cost measure (rounds / messages / bits / space).
  2. Why the state of the art leaves a gap — the best prior bound and exactly what it does not achieve in this model.
  3. The result, as a theorem — an explicit bound and the resilience/assumptions it holds at, not "more efficient."
  4. Whether it is tight — a matching lower bound elevates an algorithm to an optimality result, the venue's most valued shape.
  5. The proof idea in one breath — name the technique (valency, indistinguishability, potential function, committee sampling, covering) so the reader knows how the argument goes.

The model box is non-negotiable

Before the first theorem, state the model explicitly and completely. At PODC the model is the theorem — an agreement result under synchrony and under asynchrony are different papers. A checklist for the model box:

text
[Network]     message-passing (point-to-point / broadcast) or shared memory (registers, objects)?
[Topology]    complete graph, arbitrary graph (LOCAL/CONGEST), dynamic network?
[Timing]      synchronous rounds / asynchronous / partial synchrony (GST)?
[Faults]      none / crash / omission / Byzantine / self-stabilizing; how many (t < n/3, etc.)?
[Adversary]   adaptive or oblivious; computational assumptions (if cryptographic)?
[Randomness]  deterministic / randomized (private / shared coins)?
[Cost measure] rounds, messages, bits, space, work — and worst-case vs. expected?

Every theorem must be true in exactly this model, and no proof may silently strengthen a synchrony or weaken an adversary assumption mid-argument. Reviewers hunt for exactly this slippage.

Proof architecture

The proof is the paper, so make it navigable:

  • State lemmas where the argument needs them, each with a one-line role ("Lemma 3 bounds the number of rounds until a committee is honest-majority").
  • Separate the algorithm from its analysis. Present the protocol cleanly (pseudocode in the process's local view), then prove safety, then liveness/complexity.
  • Name invariants. Distributed proofs live on invariants preserved across rounds/steps; state them explicitly and prove they are maintained.
  • Route long proofs to the full version. A proof sketch in the 10-page body with the full proof in the appendix is standard — but the sketch must convince a reviewer the full proof exists (see podc-supplementary).
Show full SKILL.md (286 more words)Show less

The 10-page-merits discipline

The committee is guaranteed to read only the abstract and the first 10 pages. So the first 10 pages must, on their own, let a reviewer decide: they contain the model, the theorem, the delta over prior work, and enough of the proof (in sketch or in full) to believe it. Do not defer the key idea to page 14. Techniques for staying inside the budget:

  • Put the hardest, most novel part of the proof in the body; route routine calculations and standard lemmas to the appendix/full version.
  • Use a clean notation table once, not repeated definitions.
  • Prefer a tight statement plus a proof idea over a verbose informal walk-through.

Prose that helps a proof-checking reader

  • State theorems in the strongest true form — with explicit constants/asymptotics and the exact assumptions, so a reviewer is not left guessing the regime.
  • Do not oversell. "Optimal" requires a matching lower bound; "practical" requires more than a simulation and usually belongs at a systems venue. PODC readers penalize claims the proof does not support.
  • Distinguish O, Θ, Ω, and o carefully; a distributed-theory reviewer reads asymptotics literally.
  • Keep an optional simulation clearly optional — if you include a plot, say it illustrates a constant or a convergence rate and does not establish correctness (see podc-experiments).

Anti-patterns (PODC-specific)

  • The missing model box — "tolerates faults" without saying which faults, timing, or adversary.
  • Bound-free claims — "more efficient" / "scales well" instead of a stated complexity.
  • Simulation-as-proof — a scaling plot standing in for a correctness argument.
  • Proof gaps deferred past page 10 — the key lemma only in the appendix with no body sketch.
  • Sequential result in distributed clothing — if removing distribution leaves the whole contribution, it is a STOC/SODA paper (podc-topic-selection).

Output format

text
[Model box] complete? (network/timing/faults/adversary/randomness/cost measure)
[Result placement] theorem stated on the first page? tightness (matching lower bound) addressed?
[Proof architecture] lemmas stated where used; invariants named; safety/liveness separated?
[10-page merits] model+result+delta+key proof idea all within the first 10 pages? yes/no
[Claim hygiene] "optimal"/"practical" claims backed? asymptotics precise?
[Fix queue] <ordered edits to land the merits case in 10 pages>

© 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

Files

Just SKILL.md in PODC-Skills/skills/podc-writing-style of brycewang-stanford/Awesome-Journal-Skills.

Open the folder on GitHubat commit 932eb23

Compare with similar skills

Podc 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.

Podc Writing Style compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Podc Writing Style this skillbrycewang-stanford/Awesome-Journal-Skills1.2k—~1.5kAutomated safety check: PassMIT
Avoid AI Writingconorbronsdon/avoid-ai-writing4.9k3 repos~8.1kAutomated safety check: PassMIT
BrandOhh-889/skyroc79513 repos~733Automated safety check: PassMIT
Khazix WeChat Article WriterKKKKhazix/khazix-skills21k1 repos~2.9kAutomated safety check: PassMIT
Writing Guidelinesvercel-labs/agent-skills32k7 repos~309Automated safety check: PassNone
Unslop AI Writing Cleanuptheclaymethod/unslop518—~1.7kAutomated safety check: PassMIT

Similar skills

  • Avoid AI Writing

    conorbronsdon/avoid-ai-writing

    Audit and rewrite content to remove AI writing patterns ("AI-isms").

    4.9k GitHub starsUsed in 3 repos~8.1k tokens
    Writing & ContentAuto-check passed

  • Brand

    Ohh-889/skyroc

    Brand voice, visual identity, messaging frameworks, asset management, brand consistency.

    795 GitHub starsUsed in 13 repos~733 tokens
    Writing & ContentAuto-check passed

  • Khazix WeChat Article Writer

    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.

    21k GitHub starsUsed in 1 repo~2.9k tokens
    Writing & ContentAuto-check passed

  • Writing Guidelines

    vercel-labs/agent-skills

    Official

    Review docs/prose for Writing Guidelines compliance. An agent skill from vercel-labs/agent-skills.

    32k GitHub starsUsed in 7 repos~309 tokens
    Writing & ContentAuto-check passed

  • Unslop AI Writing Cleanup

    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.

    518 GitHub stars~1.7k tokensUpdated 1 mo ago
    Writing & ContentAuto-check passed

  • UX Writing

    content-designer/ux-writing-skill

    Applies UX writing practice to interface copy such as buttons, errors, forms and onboarding, using four quality standards and accessibility guidance.

    224 GitHub starsUsed in 1 repo~3.8k tokens
    Writing & ContentAuto-check passed

More from brycewang-stanford/Awesome-Journal-Skills

All 2,387 skills in this repo

  • Aaag Data Analysis

    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…

    1.2k GitHub stars~1.3k tokensUpdated 14 days ago
    Auto-check passed

  • Aaag Literature Positioning

    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…

    1.2k GitHub stars~1.3k tokensUpdated 14 days ago
    Auto-check passed

  • Aaag Rebuttal

    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…

    1.2k GitHub stars~1.4k tokensUpdated 14 days ago
    Auto-check passed

  • Aaag Research Design

    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…

    1.2k GitHub stars~1.4k tokensUpdated 14 days ago
    Auto-check passed

  • Aaag Review Process

    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…

    1.2k GitHub stars~1.3k tokensUpdated 14 days ago
    Auto-check passed

  • Aaag Submission

    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…

    1.2k GitHub stars~1.6k tokensUpdated 14 days ago
    Auto-check passed

Categories

Questions about Podc Writing Style

What does Podc Writing Style do?

A skill your agent uses when drafting or revising the body of an ACM PODC paper — building the distributed-theory skeleton (an explicit model box, the result stated as a theorem up front, a proof…. Podc Writing Style is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when drafting or revising the body of an ACM PODC paper — building the distributed-theory skeleton (an explicit model box, the result stated as a theorem up front, a proof architecture the reader can navigate, and the 10-page-merits discipline) so the merits case lands within the first 10 pages a PODC committee is guaranteed to read.

When should I use Podc Writing Style?

Podc Writing Style fits situations like: revising the body of an ACM PODC paper — building the distributed-theory skeleton (an explicit model box; the result stated as a theorem up front; A proof architecture the reader can navigate; the 10-page-merits discipline) so the merits case lands within the first 10 pages a PODC committee is guaranteed to read.

How do I install Podc Writing Style in Claude Code?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill podc-writing-style -a claude-code`. Or copy the skill folder (PODC-Skills/skills/podc-writing-style in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/podc-writing-style in your project. Claude Code loads it when a task matches its description.

How do I install Podc Writing Style in Codex?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill podc-writing-style -a codex`. Or copy the skill folder (PODC-Skills/skills/podc-writing-style in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/podc-writing-style in your project. Codex loads it when a task matches its description.

Can I use Podc Writing Style in Cursor, Gemini CLI or GitHub Copilot?

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 podc-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/podc-writing-style, .gemini/skills/podc-writing-style, .github/skills/podc-writing-style and .opencode/skills/podc-writing-style in your project.

What does Podc Writing Style need to run?

SKILL.md names no scripts, command-line tools or credentials: Podc Writing Style is instructions for the agent only.

Does Podc Writing Style access the network?

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.

Is Podc Writing Style safe to install?

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.

What licence does Podc Writing Style use?

Podc 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.

How many tokens does Podc Writing Style use?

About 1.5k tokens (SKILL.md is roughly 6.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Podc Writing Style?

Skills that share tags, products or a category with Podc Writing Style: Avoid AI Writing (conorbronsdon/avoid-ai-writing, 4.9k stars), Brand (Ohh-889/skyroc, 795 stars), Khazix WeChat Article Writer (KKKKhazix/khazix-skills, 21k stars) and Writing Guidelines (vercel-labs/agent-skills, 32k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Podc Writing Style?

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.