Read arXiv Paper
karpathy/nanochat
Fetches the TeX source of an arXiv paper from its URL, reads it and writes a markdown summary tied to the nanochat project.
A skill your agent uses when planning an ACM PODS project timeline across its multiple submission cycles per year, from venue fit through the EasyChair abstract-then-paper deadlines, the 48-hour…
Install Pods Workflow
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pods-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills pods-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/PODS-Skills/skills/pods-workflow .claude/skills/pods-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 "pods-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PODS-Skills/skills/pods-workflow into .claude/skills/pods-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pods-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/PODS-Skills/skills/pods-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 pods-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills pods-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/PODS-Skills/skills/pods-workflow .agents/skills/pods-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 "pods-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PODS-Skills/skills/pods-workflow into .agents/skills/pods-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pods-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 pods-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills pods-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/PODS-Skills/skills/pods-workflow .cursor/skills/pods-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 "pods-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PODS-Skills/skills/pods-workflow into .cursor/skills/pods-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pods-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 PODS-Skills/skills/pods-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 pods-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills pods-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/PODS-Skills/skills/pods-workflow .gemini/skills/pods-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 "pods-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PODS-Skills/skills/pods-workflow into .gemini/skills/pods-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pods-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 pods-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 pods-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/PODS-Skills/skills/pods-workflow .github/skills/pods-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 "pods-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PODS-Skills/skills/pods-workflow into .github/skills/pods-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pods-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 pods-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 pods-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/PODS-Skills/skills/pods-workflow .opencode/skills/pods-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 "pods-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PODS-Skills/skills/pods-workflow into .opencode/skills/pods-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pods-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
pods-workflow- GitHub stars
- 1.2k
- Token cost
- ~1.4k tokens
- SKILL.md length
- 687 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when planning an ACM PODS project timeline across its multiple submission cycles per year, from venue fit through the EasyChair abstract-then-paper deadlines, the 48-hour…
- Planning an ACM PODS project timeline across its multiple submission cycles per year
- SKILL.md covers Choosing a cycle, Milestones, Backward plan from the paper… and Failure modes by stage, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- From venue fit through the EasyChair abstract-then-paper deadlines
What it does
Pods Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning an ACM PODS project timeline across its multiple submission cycles per year, from venue fit through the EasyChair abstract-then-paper deadlines, the 48-hour rebuttal, the accept/reject/revision decision and shepherded revision round, PACMMOD-track publication, the arXiv full version, and presentation — with backward-planning offsets for a theory paper and honest handling of cycle choice.
Its SKILL.md is about 1.4k 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 Research & Science, covering Academic paper search. It works with arXiv. 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 an ACM PODS project timeline across its multiple submission cycles per year
- From venue fit through the EasyChair abstract-then-paper deadlines
- The 48-hour rebuttal
- The accept/reject/revision decision and shepherded revision round
Example prompts
- “/pods-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
Pods Workflow loads about 1.4k tokens when it runs. Until then it costs about 106 tokens; SKILL.md has 687 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). 687 words, ~1,371 tokens.
Download SKILL.mdSave it as
.claude/skills/pods-workflow/SKILL.md (or your agent's skills folder).- name
- pods-workflow
- description
- Use when planning an ACM PODS project timeline across its multiple submission cycles per year, from venue fit through the EasyChair abstract-then-paper deadlines, the 48-hour rebuttal, the accept/reject/revision decision and shepherded revision round, PACMMOD-track publication, the arXiv full version, and presentation — with backward-planning offsets for a theory paper and honest handling of cycle choice.
PODS Workflow
Use this as the project-management skill for a PODS submission. Replace every date with the current official timetable and work backwards from the abstract deadline, which precedes the full-paper deadline by about a week in each cycle. PODS runs multiple submission cycles per year and every paper may hit a revision round with a shepherd, so plan for a two-round-per-cycle process, not a single accept/reject.
PODS is a symposium whose papers are journal articles in the PACMMOD PODS track: it has no standing editor-in-chief and no APC in the systems sense. Rotating leadership is the per-edition PODS PC Chair (PODS 2026: Ke Yi, HKUST, verified 2026-07-09) appointed with ACM SIGMOD and SIGACT; the cost model is registration and at least one author presents. Chairs rotate yearly — re-check the organization page rather than carrying a name forward.
Choosing a cycle
PODS's multi-cycle calendar is a planning lever, not just a constraint. As of 2026-07-09, PODS 2026 (Bengaluru) has already met, so the live target is PODS 2027 (Huntington Beach): Cycle 1 closed 30 May 2026, and Cycle 2 (abstract+COI 10 Oct 2026, paper 17 Oct 2026) is the next live deadline.
- Submit when the proof is complete, not when the cycle is nearest. A rushed, gap-filled proof draws a reject that burns the cycle; PODS's next cycle is only a season away, so the cost of waiting one cycle is far smaller than at a once-a-year venue.
- A reject cannot be immediately re-submitted. Recent SIGMOD/PODS policy bars resubmitting rejected research-track work for roughly a year of cycles — so a premature submission can cost more than one cycle. Verify the exact wording before relying on the next cycle as a safety net.
Milestones
- Venue fit: confirm PODS over SIGMOD/VLDB/ICDE and over ICDT (
pods-topic-selection). - Result lock: fix the model, the theorem statements, and complete every proof; the appendix is incorporated at submission, so proofs cannot be deferred to a later "full version."
- Abstract + COI: register the real title, abstract, authors, and declared conflicts of interest by the earlier abstract deadline of the chosen cycle.
- Submission: upload the anonymized
acmsmallPDF (body + references + appendix) on EasyChair by the full-paper deadline. - Rebuttal: use the ~48-hour window to correct factual misreadings only.
- Decision: accept / reject / revision (minor or major).
- Revision (if invited): implement the revision items within the given window; a shepherd judges whether the revision is satisfactory.
- Acceptance: prepare the PACMMOD camera-ready, post the full version on arXiv, register, and present at PODS.
Show full SKILL.md (277 more words)Show less
Backward plan from the paper deadline
| Weeks out (heuristic) | Theory-paper milestone |
|---|---|
| 10+ | Model and problem fixed; main theorem statements conjectured |
| 8 | Core proofs complete; lower-bound/upper-bound gap closed or scoped honestly |
| 6 | Full draft in acmsmall; every stated theorem has a complete proof in body or appendix |
| 4 | Appendix assembled and incorporated; anonymity sweep on paper and appendix |
| 3 | Internal read by a theory colleague who checks a proof end to end |
| 2 | Tighten definitions, related-work delta, page budget (15 pp excl. refs) |
| 1 | Final proof-read of the hardest proof; COI list prepared |
| 0 | Abstract by its earlier cutoff, then paper + appendix on EasyChair |
These offsets are planning heuristics only — anchor every one to the current Important Dates page, never to a previous cycle's calendar.
Failure modes by stage
- A proof still open at week 6 forces a "sketch in the appendix" that the reviewers will not accept — the classic PODS reject in the making. Close the gap or scope the claim.
- Leaving the appendix to the final week produces incomplete proofs and identity leaks under double-anonymity (a named system, an acknowledgement).
- Skipping the colleague read forfeits the one chance to hear "your Lemma 4 is circular" from a friend instead of a reviewer.
- Treating a revision as automatic and under-budgeting the revision window turns a winnable minor revision into a reject when the shepherd is unsatisfied.
Coordination notes
- Assign one author to own the proof appendix and its anonymity, and another to own the EasyChair fields and COI list; shared ownership is how both slip.
- Archive the exact submitted PDF and appendix — the revision round and the arXiv full version must correspond to them precisely.
Output format
[Current stage] idea / proofs / writing / abstract-registered / submitted / revision / accepted
[Chosen cycle] cycle 1 / cycle 2, with the next official deadline (date + source, or unknown)
[Critical path] <three tasks that determine readiness — usually a proof gap and the appendix>
[Risk register] <open proof / page budget / anonymity / revision window / arXiv full version>
[Owner map] <task -> person or role>© 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 PODS-Skills/skills/pods-workflow of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Pods 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 |
|---|---|---|---|---|---|---|
| Pods Workflow this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Read arXiv Paperkarpathy/nanochat | 59k | 1 repos | ~494 | Automated safety check: Pass | MIT | |
| Literature Reviewneflibata-feng/MyArxiv-Agent | 126 | 20 repos | ~5.9k | Automated safety check: Notes | MIT | |
| Openalex Databaseneflibata-feng/MyArxiv-Agent | 126 | 12 repos | ~3k | Automated safety check: Pass | Custom licence | |
| Citation ManagementK-Dense-AI/claude-scientific-writer | 2.4k | 2 repos | ~3.9k | Automated safety check: Notes | MIT | |
| Citation Managementneflibata-feng/MyArxiv-Agent | 126 | 19 repos | ~8.1k | Automated safety check: Notes | MIT |
Similar skills
Literature Review
neflibata-feng/MyArxiv-Agent
Conduct comprehensive, systematic literature reviews using multiple academic databases (PubMed, arXiv, bioRxiv, Semantic Scholar, etc.).
Openalex Database
neflibata-feng/MyArxiv-Agent
Query and analyze scholarly literature using the OpenAlex database.
Citation Management
K-Dense-AI/claude-scientific-writer
Finds papers in OpenAlex, PubMed and Google Scholar, turns DOIs, PMIDs and arXiv IDs into clean BibTeX, and validates citations for a manuscript or thesis.
Citation Management
neflibata-feng/MyArxiv-Agent
Comprehensive citation management for academic research. An agent skill from neflibata-feng/MyArxiv-Agent.
Systematic Literature Review Builder
bytedance/deer-flow
Searches arXiv across many papers on one topic, extracts each paper's methodology and findings in parallel, and synthesizes a cited literature review.
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
Works with
Categories
Questions about Pods Workflow
What does Pods Workflow do?
A skill your agent uses when planning an ACM PODS project timeline across its multiple submission cycles per year, from venue fit through the EasyChair abstract-then-paper deadlines, the 48-hour…. Pods Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning an ACM PODS project timeline across its multiple submission cycles per year, from venue fit through the EasyChair abstract-then-paper deadlines, the 48-hour rebuttal, the accept/reject/revision decision and shepherded revision round, PACMMOD-track publication, the arXiv full version, and presentation — with backward-planning offsets for a theory paper and honest handling of cycle choice.
When should I use Pods Workflow?
Pods Workflow fits situations like: planning an ACM PODS project timeline across its multiple submission cycles per year; from venue fit through the EasyChair abstract-then-paper deadlines; the 48-hour rebuttal; the accept/reject/revision decision and shepherded revision round.
How do I install Pods Workflow in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pods-workflow -a claude-code`. Or copy the skill folder (PODS-Skills/skills/pods-workflow in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/pods-workflow in your project. Claude Code loads it when a task matches its description.
How do I install Pods Workflow in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pods-workflow -a codex`. Or copy the skill folder (PODS-Skills/skills/pods-workflow in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/pods-workflow in your project. Codex loads it when a task matches its description.
Can I use Pods 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 pods-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/pods-workflow, .gemini/skills/pods-workflow, .github/skills/pods-workflow and .opencode/skills/pods-workflow in your project.
What does Pods Workflow need to run?
SKILL.md names no scripts, command-line tools or credentials: Pods Workflow is instructions for the agent only.
Does Pods 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 Pods 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 Pods Workflow use?
Pods 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 Pods Workflow use?
About 1.4k tokens (SKILL.md is roughly 5.5k 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 Pods Workflow?
Skills that share tags, products or a category with Pods Workflow: Read arXiv Paper (karpathy/nanochat, 59k stars), Literature Review (neflibata-feng/MyArxiv-Agent, 126 stars), Openalex Database (neflibata-feng/MyArxiv-Agent, 126 stars) and Citation Management (K-Dense-AI/claude-scientific-writer, 2.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Pods 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.