Markdown Article Formatter
JimLiu/baoyu-skills
Reformats plain text or Markdown articles with frontmatter, a title, a summary, headings, bold, lists and code blocks, and saves a separate formatted copy.
A skill your agent uses when drafting a PLDI author response inside the short February window — triaging reviewer objections about soundness, baselines, and benchmark validity, correcting factual…
Install Pldi Author Response
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pldi-author-response -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills pldi-author-response --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/PLDI-Skills/skills/pldi-author-response .claude/skills/pldi-author-response && 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 "pldi-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PLDI-Skills/skills/pldi-author-response into .claude/skills/pldi-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pldi-author-response", 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/PLDI-Skills/skills/pldi-author-responseType 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 pldi-author-response -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills pldi-author-response --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/PLDI-Skills/skills/pldi-author-response .agents/skills/pldi-author-response && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "pldi-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PLDI-Skills/skills/pldi-author-response into .agents/skills/pldi-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pldi-author-response", 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 pldi-author-response -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills pldi-author-response --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/PLDI-Skills/skills/pldi-author-response .cursor/skills/pldi-author-response && 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 "pldi-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PLDI-Skills/skills/pldi-author-response into .cursor/skills/pldi-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pldi-author-response", 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 PLDI-Skills/skills/pldi-author-response--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 pldi-author-response -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills pldi-author-response --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/PLDI-Skills/skills/pldi-author-response .gemini/skills/pldi-author-response && 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 "pldi-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PLDI-Skills/skills/pldi-author-response into .gemini/skills/pldi-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pldi-author-response", 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 pldi-author-responseInstalls 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 pldi-author-response -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/PLDI-Skills/skills/pldi-author-response .github/skills/pldi-author-response && 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 "pldi-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PLDI-Skills/skills/pldi-author-response into .github/skills/pldi-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pldi-author-response", 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 pldi-author-response -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 pldi-author-response --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/PLDI-Skills/skills/pldi-author-response .opencode/skills/pldi-author-response && 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 "pldi-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PLDI-Skills/skills/pldi-author-response into .opencode/skills/pldi-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pldi-author-response", 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.
Facts
- Skill name
pldi-author-response- GitHub stars
- 1.2k
- Token cost
- ~971 tokens
- SKILL.md length
- 387 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when drafting a PLDI author response inside the short February window — triaging reviewer objections about soundness, baselines, and benchmark validity, correcting factual…
- Drafting a PLDI author response inside the short February window — triaging reviewer objections about soundness
- SKILL.md covers Triage before writing, Rules that keep responses alive, A working skeleton and After the window, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Benchmark validity
What it does
Pldi Author Response is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when drafting a PLDI author response inside the short February window — triaging reviewer objections about soundness, baselines, and benchmark validity, correcting factual errors with pointers into the submitted PDF, and committing to feasible revisions without promising new systems work.
Its SKILL.md is about 970 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 Documents & Office. 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
- Drafting a PLDI author response inside the short February window — triaging reviewer objections about soundness
- Benchmark validity
- Correcting factual errors with pointers into the submitted PDF
- Committing to feasible revisions without promising new systems work
Example prompts
- “/pldi-author-response”
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 Author Response loads about 971 tokens when it runs. Until then it costs about 79 tokens; SKILL.md has 387 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.
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). 387 words, ~971 tokens.
Download SKILL.mdSave it as
.claude/skills/pldi-author-response/SKILL.md (or your agent's skills folder).- name
- pldi-author-response
- description
- Use when drafting a PLDI author response inside the short February window — triaging reviewer objections about soundness, baselines, and benchmark validity, correcting factual errors with pointers into the submitted PDF, and committing to feasible revisions without promising new systems work.
PLDI Author Response
PLDI 2026 gave authors a five-day response window, February 17-21, 2026, between
review delivery and the March 5 notification (dates from pldi26.sigplan.org,
read 2026-07-08; every cycle re-times this). The response is read by people who
build compilers and verifiers for a living: precision beats rhetoric, and a
pointer into your own submitted PDF beats a paragraph of reassurance.
Triage before writing
Sort every reviewer point into one of four buckets and answer them in this order:
| Bucket | Example at PLDI | Correct move |
|---|---|---|
| Factual error | "The analysis ignores exceptions" when §4.2 handles them | Quote §4.2 verbatim, one sentence of context |
| Soundness doubt | "Theorem 2 seems to assume no reentrancy" | State the assumption's exact location; if the reviewer is right, say what the fix costs |
| Evaluation gap | "No comparison against the LLVM baseline at -O2" | Give the number if it exists in your logs; otherwise commit to the exact experiment, not to "more evaluation" |
| Scope disagreement | "Why not handle JIT compilation?" | Defend the stated scope; do not promise to widen it |
A soundness doubt outranks everything. One reviewer convinced your core theorem or transformation is broken outweighs three asking for extra benchmarks, so spend your first and best paragraph there.
Show full SKILL.md (186 more words)Show less
Rules that keep responses alive
- Answer the question asked. Implementor-reviewers notice deflection immediately; a direct "yes, our technique fails on X, and here is why the claim survives" earns more than a hedge.
- No new contributions. New numbers are acceptable only when they answer a direct question and come from the already-described setup — for instance, a requested baseline flag configuration. A new algorithm or proof in a rebuttal reads as an admission the submission was premature.
- Quote yourself by section and line, not by memory. Reviewers reread exactly what you cite; a wrong pointer costs credibility twice.
- Budget by damage. Give the most negative substantive review the most space; do not spend a page thanking the champion reviewer.
- Stay anonymous. Double-blind persists through the response; no links that resolve to your lab.
A working skeleton
We thank all reviewers. We first address the soundness question (Rev B),
then the baseline request (Rev A, Rev C), then smaller points.
[B1: soundness of Thm 2 under reentrancy]
Assumption A3 (§5.1, p.12) excludes reentrant callbacks; the proof uses it
in Lemma 4. We will state A3 in the theorem statement itself. The
restriction removes 2 of 14 benchmark programs (§6.1 already notes this).
[A2/C3: -O2 baseline]
Our logs include this configuration: geomean 1.11x vs 1.17x reported.
We will add the column to Table 4.
[C5: JIT scope]
Out of scope by design (§2); AOT-only assumptions are used in §4.3.After the window
Archive the response beside the submitted PDF. If the decision is acceptance,
your camera-ready and artifact must actually deliver every "we will" sentence —
PLDI reviewers routinely check; see pldi-camera-ready and
pldi-artifact-evaluation. If it is rejection, the response doubles as the
revision plan for the next November.
Output format
[Decisive issue] <the one objection that moves the decision>
[Bucket map] Rev A: ... / Rev B: ... / Rev C: ...
[New-number policy] <what may be cited, from which logged runs>
[Commitments] <numbered, feasible, camera-ready-sized>
[Anonymity check] pass / fail© 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-author-response of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Pldi Author Response 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 |
|---|---|---|---|---|---|---|
| Pldi Author Response this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~971 | Automated safety check: Pass | MIT | |
| Markdown Article FormatterJimLiu/baoyu-skills | 27k | 6 repos | ~3.5k | Automated safety check: Pass | MIT | |
| MarkitdownImCa0/just-laws | 781 | 14 repos | ~3.2k | Automated safety check: Notes | MIT | |
| Obsidian MarkdownAtmosphere/atmosphere | 3.8k | 20 repos | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| DOCXrvdbreemen/OTGW-firmware | 207 | 33 repos | ~4.3k | Automated safety check: Pass | Proprietary | |
| Word Document Reader and WriterHKUDS/DeepTutor | 41k | — | ~2.5k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Markitdown
ImCa0/just-laws
Convert files and office documents to Markdown. An agent skill from ImCa0/just-laws.
Obsidian Markdown
Atmosphere/atmosphere
Create and edit Obsidian Flavored Markdown with wikilinks, embeds, callouts, properties, and other Obsidian-specific syntax.
DOCX
rvdbreemen/OTGW-firmware
A skill your agent uses whenever the user wants to create, read, edit, or manipulate Word documents (.docx files).
Word Document Reader and Writer
HKUDS/DeepTutor
Reads, creates and edits Word .docx files with python-docx, and drops to raw OOXML for tracked changes, comments and byte-exact edits.
Crossposting
wasp-lang/wasp
Crosspost Wasp blog articles (MDX) to DEV.to and Medium. An agent skill from wasp-lang/wasp.
More from brycewang-stanford/Awesome-Journal-Skills
All 2,387 skills in this repoAaag 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…
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…
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…
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…
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…
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…
Related
Categories
Questions about Pldi Author Response
What does Pldi Author Response do?
A skill your agent uses when drafting a PLDI author response inside the short February window — triaging reviewer objections about soundness, baselines, and benchmark validity, correcting factual…. Pldi Author Response is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when drafting a PLDI author response inside the short February window — triaging reviewer objections about soundness, baselines, and benchmark validity, correcting factual errors with pointers into the submitted PDF, and committing to feasible revisions without promising new systems work.
When should I use Pldi Author Response?
Pldi Author Response fits situations like: drafting a PLDI author response inside the short February window — triaging reviewer objections about soundness; benchmark validity; correcting factual errors with pointers into the submitted PDF; committing to feasible revisions without promising new systems work.
How do I install Pldi Author Response in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pldi-author-response -a claude-code`. Or copy the skill folder (PLDI-Skills/skills/pldi-author-response in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/pldi-author-response in your project. Claude Code loads it when a task matches its description.
How do I install Pldi Author Response in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pldi-author-response -a codex`. Or copy the skill folder (PLDI-Skills/skills/pldi-author-response in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/pldi-author-response in your project. Codex loads it when a task matches its description.
Can I use Pldi Author Response 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-author-response -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-author-response, .gemini/skills/pldi-author-response, .github/skills/pldi-author-response and .opencode/skills/pldi-author-response in your project.
What does Pldi Author Response need to run?
SKILL.md names no scripts, command-line tools or credentials: Pldi Author Response is instructions for the agent only.
Does Pldi Author Response 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 Author Response 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 Author Response use?
Pldi Author Response 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 Author Response use?
About 971 tokens (SKILL.md is roughly 3.9k 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 Author Response?
Skills that share tags, products or a category with Pldi Author Response: Markdown Article Formatter (JimLiu/baoyu-skills, 27k stars), Markitdown (ImCa0/just-laws, 781 stars), Obsidian Markdown (Atmosphere/atmosphere, 3.8k stars) and DOCX (rvdbreemen/OTGW-firmware, 207 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Pldi Author Response?
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.