A skill your agent uses when revising a PLDI draft for the venue's voice — design insight before tool name, mechanisms instead of adjectives, a running example that carries the semantics, honest…

MITAuto-check passedWriting & Content

Install Pldi Writing Style

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

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

GitHub CLI
$ gh skill install brycewang-stanford/Awesome-Journal-Skills pldi-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/PLDI-Skills/skills/pldi-writing-style .claude/skills/pldi-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
pldi-writing-style
GitHub stars
1.2k
Token cost
~1.1k tokens
SKILL.md length
476 words
Files
1
Skills in repo
2,387
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when revising a PLDI draft for the venue's voice — design insight before tool name, mechanisms instead of adjectives, a running example that carries the semantics, honest…

  • Works in 4 steps: What breaks today? The concrete program,… → What is the insight? One sentence a… → Does it exist? The implementation… → …
  • Revising a PLDI draft for the venues voice — design insight before tool name
  • SKILL.md covers The first-page contract, Style table: draft reflex →…, The running example discipline and Claim ledger, plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Pldi Writing Style is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when revising a PLDI draft for the venue's voice — design insight before tool name, mechanisms instead of adjectives, a running example that carries the semantics, honest limitation statements, and prose that fits the single-column acmsmall journal format without padding toward the page cap.

Its SKILL.md is about 1.1k 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 a PLDI draft for the venues voice — design insight before tool name
  • Mechanisms instead of adjectives
  • A running example that carries the semantics
  • Honest limitation statements

Example prompts

  • “/pldi-writing-style”

Workflow steps

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

  1. What breaks today? The concrete program, workload, or proof burden that
  2. What is the insight? One sentence a compiler writer could act on
  3. Does it exist? The implementation substrate — which compiler, which IR,
  4. What is the headline evidence? The number, with its suite and baseline

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

Pldi Writing Style loads about 1.1k tokens when it runs. Until then it costs about 79 tokens; SKILL.md has 476 words of instructions outside code blocks.

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

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). 476 words, ~1,067 tokens.

Download SKILL.mdSave it as .claude/skills/pldi-writing-style/SKILL.md (or your agent's skills folder).
name
pldi-writing-style
description
Use when revising a PLDI draft for the venue's voice — design insight before tool name, mechanisms instead of adjectives, a running example that carries the semantics, honest limitation statements, and prose that fits the single-column acmsmall journal format without padding toward the page cap.

PLDI Writing Style

A PLDI paper is an engineering argument written for people who will try to break it. The style that survives has three habits: it states the hard case before the solution, it explains mechanisms rather than accumulating adjectives, and it scopes every claim to exactly what the evaluation shows. Since the PACMPL switch, the published object is a journal article in single-column acmsmall — roomier lines than the old two-column look, but the same conference-grade cap on text pages, so the format rewards clarity, not length.

The first-page contract

By the end of page one a reviewer should be able to answer four questions:

  1. What breaks today? The concrete program, workload, or proof burden that existing techniques mishandle — shown, ideally, as a small code example.
  2. What is the insight? One sentence a compiler writer could act on ("summarize modules by polymorphic escape signatures"), not a property wish ("fast and precise").
  3. Does it exist? The implementation substrate — which compiler, which IR, which proof assistant.
  4. What is the headline evidence? The number, with its suite and baseline attached, plus the paper's stated limit.

The worked rewrite in resources/worked-examples/01-introduction.md performs this transformation end to end.

Style table: draft reflex → PLDI voice

Draft reflexPLDI voice
"Our novel framework significantly outperforms...""On suite S, T improves geomean runtime 1.17x over B at -O2 (30 runs, 95% CI)"
Tool name in the title, insight in §4Insight in the title and abstract; the tool demonstrates it
Related work as a guided museum tourEach cited line ends with the delta from this paper (pldi-related-work)
Limitations paragraph as an apology in §8Restrictions stated where introduced, with their cost measured
Semantics by proseJudgments, figures, and a running example threaded through §3-§5
Padding toward the capWhitespace returned; reviewers never reward a full 20 pages for its own sake
Show full SKILL.md (167 more words)Show less

The running example discipline

Pick one small program that exhibits the hard case and reuse it everywhere: to motivate (§1), to walk the semantics (§3), to show the transformation (§4), and as the first row of the evaluation (§6). One example that a reviewer can trace end-to-end beats five disconnected snippets — and it is the cheapest insurance against the "I could not follow the analysis" review.

Claim ledger

Before the final pass, extract every claim sentence and demand its evidence address:

text
CLAIM                                    -> EVIDENCE
"sound modulo first-class continuations" -> Thm 2 (§5) + restriction check (§4.4)
"majority of closures stack-allocated"   -> Table 3, 11/14 programs
"under 3% compile-time overhead"         -> Table 5, 30 timed builds, CI
"no whole-program pass required"         -> §4.2 construction, artifact demo

Any claim without an address gets weakened or cut; any evidence without a claim is a candidate for the supplement (pldi-supplementary).

Sentence-level habits

  • Present tense for the system's behavior, past tense for the experiments run.
  • Name concrete infrastructure ("an LLVM 18 pass", "a Rocq development of 12k lines") — abstraction here reads as evasion.
  • Kill the "increasingly popular/important" opener; start at the hard case.
  • Define notation once, in a figure, before first use; PLDI reviewers cite notation drift as a soundness smell, not a typo.

Output format

text
[First-page contract] hard case / insight sentence / substrate / headline number: each present?
[Running example] one program threaded through §1-§6? yes/no
[Claim ledger] n claims, n addressed, list the orphans
[Tone flags] adjectives standing in for mechanisms; apology-style limitations
[Cut list] <sections/paragraphs to compress before the cap does it for you>

© 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 PLDI-Skills/skills/pldi-writing-style of brycewang-stanford/Awesome-Journal-Skills.

Open the folder on GitHubat commit 932eb23

Compare with similar skills

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

Pldi Writing Style compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Pldi Writing Style this skillbrycewang-stanford/Awesome-Journal-Skills1.2k—~1.1kAutomated 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

Questions about Pldi Writing Style

What does Pldi Writing Style do?

A skill your agent uses when revising a PLDI draft for the venue's voice — design insight before tool name, mechanisms instead of adjectives, a running example that carries the semantics, honest…. Pldi Writing Style is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when revising a PLDI draft for the venue's voice — design insight before tool name, mechanisms instead of adjectives, a running example that carries the semantics, honest limitation statements, and prose that fits the single-column acmsmall journal format without padding toward the page cap.

When should I use Pldi Writing Style?

Pldi Writing Style fits situations like: revising a PLDI draft for the venues voice — design insight before tool name; mechanisms instead of adjectives; A running example that carries the semantics; honest limitation statements.

How do I install Pldi Writing Style in Claude Code?

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

How do I install Pldi Writing Style in Codex?

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

Can I use Pldi 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 pldi-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/pldi-writing-style, .gemini/skills/pldi-writing-style, .github/skills/pldi-writing-style and .opencode/skills/pldi-writing-style in your project.

What does Pldi Writing Style need to run?

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

Does Pldi 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 Pldi 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 Pldi Writing Style use?

Pldi 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 Pldi Writing Style use?

About 1.1k tokens (SKILL.md is roughly 4.3k 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 Pldi Writing Style?

Skills that share tags, products or a category with Pldi 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 Pldi 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.