Marketing Campaign
affaan-m/ECC
End-to-end marketing campaign planning and execution. An agent skill from affaan-m/ECC.
A skill your agent uses when planning a PLDI campaign across its annual clock — backward-planning from the November deadline through winter reviewing, the February response window, March…
MITAuto-check passed
Install Pldi Workflow
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pldi-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills pldi-workflow --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-workflow .claude/skills/pldi-workflow && 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-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PLDI-Skills/skills/pldi-workflow into .claude/skills/pldi-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pldi-workflow", 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-workflowType 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-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills pldi-workflow --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-workflow .agents/skills/pldi-workflow && 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-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PLDI-Skills/skills/pldi-workflow into .agents/skills/pldi-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pldi-workflow", 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-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills pldi-workflow --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-workflow .cursor/skills/pldi-workflow && 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-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PLDI-Skills/skills/pldi-workflow into .cursor/skills/pldi-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pldi-workflow", 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-workflow--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-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills pldi-workflow --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-workflow .gemini/skills/pldi-workflow && 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-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PLDI-Skills/skills/pldi-workflow into .gemini/skills/pldi-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pldi-workflow", 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-workflowInstalls 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-workflow -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-workflow .github/skills/pldi-workflow && 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-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PLDI-Skills/skills/pldi-workflow into .github/skills/pldi-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pldi-workflow", 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-workflow -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-workflow --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-workflow .opencode/skills/pldi-workflow && 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-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PLDI-Skills/skills/pldi-workflow into .opencode/skills/pldi-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pldi-workflow", 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-workflow- GitHub stars
- 1.2k
- Token cost
- ~985 tokens
- SKILL.md length
- 374 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when planning a PLDI campaign across its annual clock — backward-planning from the November deadline through winter reviewing, the February response window, March…
- Planning a PLDI campaign across its annual clock — backward-planning from the November deadline through winter reviewing
- SKILL.md covers Backward plan from the…, The long tail after the deadline, Ownership map and Rejection routing, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- The February response window
What it does
Pldi Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning a PLDI campaign across its annual clock — backward-planning from the November deadline through winter reviewing, the February response window, March notification, post-acceptance artifact evaluation, PACMPL production, and the June conference, with owners for each deliverable.
Its SKILL.md is about 990 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
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
- Planning a PLDI campaign across its annual clock — backward-planning from the November deadline through winter reviewing
- The February response window
- March notification
- Post-acceptance artifact evaluation
Example prompts
- “/pldi-workflow”
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 Workflow loads about 985 tokens when it runs. Until then it costs about 77 tokens; SKILL.md has 374 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). 374 words, ~985 tokens.
Download SKILL.mdSave it as
.claude/skills/pldi-workflow/SKILL.md (or your agent's skills folder).- name
- pldi-workflow
- description
- Use when planning a PLDI campaign across its annual clock — backward-planning from the November deadline through winter reviewing, the February response window, March notification, post-acceptance artifact evaluation, PACMPL production, and the June conference, with owners for each deliverable.
PLDI Workflow
PLDI is an annual, single-deadline venue with a long tail: the paper is due in November, but the project is not finished until the PACMPL article, the badged Zenodo artifact, and the June talk have all shipped. Plan all three from the start. Anchor dates below are the 2026 cycle (deadline Nov 13, 2025; response Feb 17-21, 2026; notification Mar 5, 2026; registration opened Mar 16; conference in Boulder Jun 15-19, 2026) — reread the current dates page before scheduling anything, and note that PLDI 2027's calendar was unpublished as of 2026-07-08 (待核实).
PLDI has no standing editor-in-chief and charges no submission fee; leadership
rotates per edition (2026: General Chair Bor-Yuh Evan Chang, Program Chair Manu
Sridharan), the conference is funded through registration, and the PACMPL
open-access cost is handled through SIGPLAN/ACM Open arrangements at
camera-ready time (pldi-camera-ready), not at submission.
Backward plan from the November deadline
| Weeks out | Milestone for a compiler/analysis paper |
|---|---|
| 12+ | Mechanism frozen; running example chosen; suite + baselines locked (pldi-experiments) |
| 8 | Implementation feature-complete on the suite; measurement protocol scripted (pldi-reproducibility) |
| 6 | Full benchmark campaign run once end-to-end; losing benchmarks diagnosed |
| 4 | Complete draft in acmsmall; proofs or soundness argument internally reviewed |
| 3 | Mock review by a PL colleague outside the project; ablation gaps closed |
| 2 | Final measurement run from clean scripts; claim ledger reconciled (pldi-writing-style) |
| 1 | Anonymity sweep, supplement assembly, HotCRP fields, dual-submission check |
| 0 | Upload with a day of slack |
Show full SKILL.md (138 more words)Show less
The long tail after the deadline
Nov: submit; archive exact PDF + scripts + raw results
Dec-Jan: keep the artifact warm — the response window may need a rerun
Feb: response window (days, not weeks): triage -> draft -> co-author pass -> submit
Mar: decision. Accept: start AE packaging same week; camera-ready plan.
Reject: file reviews against the claim ledger; decide POPL/OOPSLA/next PLDI.
Apr-May: artifact evaluation runs; PACMPL production; register; build the talk.
Jun: conference. Post-talk: sync the Zenodo record with the final article.Two scheduling traps dominate. First, the response window is short and fixed —
a co-author on vacation in late February is a real project risk; put the window
on calendars in November. Second, artifact evaluation begins right after
notification, so the team that celebrates acceptance for two weeks starts AE
already behind (pldi-artifact-evaluation).
Ownership map
Assign one named owner each for: the measurement protocol, the anonymity sweep, the response draft, the artifact, and the camera-ready/rights workflow. The artifact owner should not be the graduating student whose defense is in April.
Rejection routing
A PLDI reject in March leaves useful runway: OOPSLA and ICFP deadlines, or the
next PLDI in November. Route by what the reviews attacked — soundness objections
must be fixed before any resubmission inside the same reviewer community
(pldi-review-process, pldi-topic-selection).
Output format
[Stage] design / implementation / evaluation / writing / submitted / response / decided / post-acceptance
[Next hard date] <from the live dates page; 待核实 if unpublished>
[Critical path] <three tasks gating the next stage>
[Owners] protocol / anonymity / response / artifact / camera-ready
[Long-tail risks] response-window availability, AE start, registration, talk© 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-workflow of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Pldi Workflow 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 Workflow this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~985 | Automated safety check: Pass | MIT | |
| Marketing Campaignaffaan-m/ECC | 276k | 1 repos | ~1.3k | Automated safety check: Pass | MIT | |
| Campaign Analyticsalirezarezvani/claude-skills | 28k | 1 repos | ~2.1k | Automated safety check: Pass | MIT | |
| Campaign Cleaner AutomationComposioHQ/awesome-claude-skills | 77k | 3 repos | ~764 | Automated safety check: Pass | None | |
| Ad Campaign Analyzersickn33/agentic-awesome-skills | 47k | 1 repos | ~4.3k | Automated safety check: Pass | MIT | |
| Ad Campaign Analyzergithub/awesome-copilot | 40k | 2 repos | ~3.5k | Automated safety check: Pass | MIT |
Similar skills
Campaign Analytics
alirezarezvani/claude-skills
Calculates attribution, funnel and ROI figures for marketing campaigns with three Python scripts that need only the standard library.
Campaign Cleaner Automation
ComposioHQ/awesome-claude-skills
Automate Campaign Cleaner tasks via Rube MCP (Composio). An agent skill from ComposioHQ/awesome-claude-skills.
Ad Campaign Analyzer
sickn33/agentic-awesome-skills
Analyze cross-channel campaign data, quantify uncertainty, and propose evidence-labeled budget tests without overstating causality.
- Official
Ad Campaign Analyzer
github/awesome-copilot
A skill your agent uses when the user shares ad campaign performance data and asks what to cut, scale, or test.
Executing Marketing Campaigns
davila7/claude-code-templates
Plans, creates, and optimizes marketing campaigns including content strategy, social media, email, and analytics.
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…
Questions about Pldi Workflow
What does Pldi Workflow do?
A skill your agent uses when planning a PLDI campaign across its annual clock — backward-planning from the November deadline through winter reviewing, the February response window, March…. Pldi Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning a PLDI campaign across its annual clock — backward-planning from the November deadline through winter reviewing, the February response window, March notification, post-acceptance artifact evaluation, PACMPL production, and the June conference, with owners for each deliverable.
When should I use Pldi Workflow?
Pldi Workflow fits situations like: planning a PLDI campaign across its annual clock — backward-planning from the November deadline through winter reviewing; the February response window; march notification; post-acceptance artifact evaluation.
How do I install Pldi Workflow in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pldi-workflow -a claude-code`. Or copy the skill folder (PLDI-Skills/skills/pldi-workflow in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/pldi-workflow in your project. Claude Code loads it when a task matches its description.
How do I install Pldi Workflow in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pldi-workflow -a codex`. Or copy the skill folder (PLDI-Skills/skills/pldi-workflow in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/pldi-workflow in your project. Codex loads it when a task matches its description.
Can I use Pldi Workflow 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-workflow -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-workflow, .gemini/skills/pldi-workflow, .github/skills/pldi-workflow and .opencode/skills/pldi-workflow in your project.
What does Pldi Workflow need to run?
SKILL.md names no scripts, command-line tools or credentials: Pldi Workflow is instructions for the agent only.
Does Pldi Workflow 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 Workflow 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 Workflow use?
Pldi Workflow 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 Workflow use?
About 985 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 Workflow?
Skills that share tags, products or a category with Pldi Workflow: Marketing Campaign (affaan-m/ECC, 276k stars), Campaign Analytics (alirezarezvani/claude-skills, 28k stars), Campaign Cleaner Automation (ComposioHQ/awesome-claude-skills, 77k stars) and Ad Campaign Analyzer (sickn33/agentic-awesome-skills, 47k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Pldi Workflow?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,228 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.