Ieee Paper Reader
CloudWave818/ieee-skills
Read, decompose, and analyze IEEE-style papers using routed technical-reading workflows.
A skill your agent uses when writing the related-work and positioning of an ACM PODC paper — covering the distributed-computing literature lanes (PODC/DISC/SPAA and the JACM / Distributed Computing…
Install Podc Related Work
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill podc-related-work -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills podc-related-work --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/PODC-Skills/skills/podc-related-work .claude/skills/podc-related-work && 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 "podc-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PODC-Skills/skills/podc-related-work into .claude/skills/podc-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "podc-related-work", 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/PODC-Skills/skills/podc-related-workType 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 podc-related-work -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills podc-related-work --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/PODC-Skills/skills/podc-related-work .agents/skills/podc-related-work && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "podc-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PODC-Skills/skills/podc-related-work into .agents/skills/podc-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "podc-related-work", 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 podc-related-work -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills podc-related-work --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/PODC-Skills/skills/podc-related-work .cursor/skills/podc-related-work && 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 "podc-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PODC-Skills/skills/podc-related-work into .cursor/skills/podc-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "podc-related-work", 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 PODC-Skills/skills/podc-related-work--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 podc-related-work -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills podc-related-work --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/PODC-Skills/skills/podc-related-work .gemini/skills/podc-related-work && 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 "podc-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PODC-Skills/skills/podc-related-work into .gemini/skills/podc-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "podc-related-work", 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 podc-related-workInstalls 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 podc-related-work -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/PODC-Skills/skills/podc-related-work .github/skills/podc-related-work && 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 "podc-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PODC-Skills/skills/podc-related-work into .github/skills/podc-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "podc-related-work", 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 podc-related-work -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 podc-related-work --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/PODC-Skills/skills/podc-related-work .opencode/skills/podc-related-work && 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 "podc-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PODC-Skills/skills/podc-related-work into .opencode/skills/podc-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "podc-related-work", 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
podc-related-work- GitHub stars
- 1.2k
- Token cost
- ~1.4k tokens
- SKILL.md length
- 623 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when writing the related-work and positioning of an ACM PODC paper — covering the distributed-computing literature lanes (PODC/DISC/SPAA and the JACM / Distributed Computing…
- Writing a model-and-bound-precise delta over prior results
- SKILL.md covers The literature lanes, Write the delta in the field's…, Distinguish your model from… and Positioning your contribution, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Distinguishing your model from neighboring ones
What it does
Podc Related Work is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when writing the related-work and positioning of an ACM PODC paper — covering the distributed-computing literature lanes (PODC/DISC/SPAA and the JACM / Distributed Computing journals), writing a model-and-bound-precise delta over prior results, distinguishing your model from neighboring ones, and keeping self-citation safe under lightweight double-blind review.
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 Literature review, Citation management and Positioning and messaging. 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
- Writing a model-and-bound-precise delta over prior results
- Distinguishing your model from neighboring ones
- Keeping self-citation safe under lightweight double-blind review
Example prompts
- “/podc-related-work”
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 Related Work loads about 1.4k tokens when it runs. Until then it costs about 96 tokens; SKILL.md has 623 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). 623 words, ~1,434 tokens.
Download SKILL.mdSave it as
.claude/skills/podc-related-work/SKILL.md (or your agent's skills folder).- name
- podc-related-work
- description
- Use when writing the related-work and positioning of an ACM PODC paper — covering the distributed-computing literature lanes (PODC/DISC/SPAA and the JACM / Distributed Computing journals), writing a model-and-bound-precise delta over prior results, distinguishing your model from neighboring ones, and keeping self-citation safe under lightweight double-blind review.
PODC Related Work
Position against results, not topics. In distributed-computing theory a "related" paper is one that proves a bound in a comparable model, and your delta must be stated in the currency the field uses: model + problem + cost measure + bound. A related-work section that lists topics ("several works study consensus") without the bounds and models tells a PODC reviewer nothing.
The literature lanes
- PODC and DISC — the two distributed-theory flagships; most of your closest prior bounds live here. They share the Dijkstra Prize and Dissertation Award and much of a reviewer pool, so their results are the ones your reviewers know best.
- SPAA — parallel algorithms/architectures; relevant for shared-memory and concurrency results, less so for message-passing/fault-tolerance.
- STOC / FOCS / SODA — where a distributed result's sequential core or a key combinatorial lemma may have appeared; cite when your technique descends from sequential theory.
- Journals — JACM and Distributed Computing — the archival, definitive versions of many results (FLP, partial synchrony, linearizability). Cite the journal version for the canonical statement, and the conference version if you specifically mean that edition.
- Focused venues — OPODIS, SIROCCO, SSS, ICDCN — for niche models (mobile agents, networks, self-stabilization).
- Systems venues / arXiv — for applied or very recent work; cite carefully and note when a result is empirical rather than proved.
Write the delta in the field's currency
For each closest prior result, state the comparison precisely:
[Prior] <authors, venue/year>: <problem> in <model>, <bound> (e.g., O(n^2) messages, t < n/2, synchronous)
[Ours] same problem in <model>: <bound> (e.g., O(n log n) messages, t < n/3, partial synchrony)
[Delta] what improved and at what cost: better message complexity but weaker resilience / stronger
adversary / different timing model — state the trade honestlyThe discipline is to make model differences explicit. "We improve on [X]" is misleading if [X] was synchronous and you are asynchronous, or if [X] tolerated more faults. A PODC reviewer will notice an apples-to-oranges comparison immediately, and it reads as either sloppiness or spin.
Distinguish your model from neighbors
Much apparent overlap dissolves once models are pinned down. Make sure the reader cannot confuse your setting with an adjacent one:
- Synchrony: a bound under synchrony does not contradict a lower bound under asynchrony.
- Fault model: crash-tolerant and Byzantine-tolerant results are not comparable head-to-head.
- Adversary: adaptive vs. oblivious changes what is achievable; say which you assume.
- Cost measure: a round-optimal protocol may be message-suboptimal; name the measure you optimize and acknowledge the others.
Show full SKILL.md (275 more words)Show less
Positioning your contribution
- Delta-first: open the related-work discussion (or the introduction's positioning paragraph) with what is new relative to the nearest result, not with a history of the problem.
- Concede honestly: if a prior protocol beats you on one measure while you beat it on another, say so. A trade-off stated plainly is a stronger paper than an overclaimed strict improvement.
- Locate the lower bound: if your algorithm is optimal, cite (or prove) the matching lower bound and say which prior lower bound your result meets or circumvents (by changing the model).
Self-citation under lightweight double-blind
PODC 2026 is lightweight double-blind, so self-citations must not de-anonymize you:
- Refer to your own prior work in the third person: "Prior work [12] shows..." never "In our earlier paper [12] we show...".
- Do not write "as we proved in [12]" or "extending our framework [7]".
- Keep the citation itself in the bibliography (do not remove it — that distorts the record); just neutralize the phrasing that reveals authorship.
- Watch for indirect leaks: "building on the model of [our group's] system X" or an acknowledgement of a grant tied to you.
Common failures
- Topic lists instead of bound comparisons — no models, no complexities, no delta.
- Apples-to-oranges "improvements" — comparing across incompatible synchrony/fault/adversary assumptions without flagging it.
- Missing the closest result — a reviewer who works in your subarea knows the one paper you did not cite; that omission reads as either ignorance or evasion.
- Journal-vs-conference confusion — citing a PODC edition for a result whose canonical statement is a JACM article (or vice versa); see the exemplars library's omissions list.
- Self-citation leak — first-person references to your own prior work under double-blind.
Output format
[Lanes covered] PODC/DISC/SPAA/STOC-FOCS-SODA/journals/focused venues — each relevant one present?
[Delta table] for each closest prior result: model, bound, ours, honest trade-off
[Model distinctions] synchrony/faults/adversary/cost-measure differences made explicit?
[Optimality] matching lower bound located/cited/proved?
[Double-blind] self-citations third-person; no grant/group leaks?
[Fix queue] <missing closest results; over/under-claimed deltas; leaks to fix>© 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-related-work of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Podc Related Work 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 |
|---|---|---|---|---|---|---|
| Podc Related Work this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Ieee Paper ReaderCloudWave818/ieee-skills | 359 | — | ~591 | Automated safety check: Pass | MIT | |
| Gec Literature Positioningfranklee16/academic-research-skills | 223 | 1 repos | ~855 | Automated safety check: Pass | None | |
| Jpe Literature Positioningfranklee16/academic-research-skills | 223 | 1 repos | ~1.1k | Automated safety check: Pass | None | |
| Systematic Review ScreenerImbad0202/academic-research-skills | 51k | — | ~8.4k | Automated safety check: Pass | Custom licence | |
| Literature Reviewneflibata-feng/MyArxiv-Agent | 126 | 20 repos | ~5.9k | Automated safety check: Notes | MIT |
Similar skills
Gec Literature Positioning
franklee16/academic-research-skills
A skill your agent uses when positioning a Global Environmental Change (GEC) manuscript against the relevant literatures.
Jpe Literature Positioning
franklee16/academic-research-skills
A skill your agent uses when writing or repairing the introduction and related-work framing for a Journal of Political Economy (JPE) manuscript — situating the contribution in the economics…
Systematic Review Screener
Imbad0202/academic-research-skills
Screens records for systematic, scoping and rapid reviews against fixed eligibility rules, using two blinded AI reviewers and a third adjudicator, with traceable PRISMA counts.
Literature Review
neflibata-feng/MyArxiv-Agent
Conduct comprehensive, systematic literature reviews using multiple academic databases (PubMed, arXiv, bioRxiv, Semantic Scholar, etc.).
Preprint Search on bioRxiv
LigphiDonk/Oh-my--paper
Searches bioRxiv life sciences preprints by keyword, author, date range or category with a Python script, returning JSON metadata and optional PDF downloads.
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 Podc Related Work
What does Podc Related Work do?
A skill your agent uses when writing the related-work and positioning of an ACM PODC paper — covering the distributed-computing literature lanes (PODC/DISC/SPAA and the JACM / Distributed Computing…. Podc Related Work is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when writing the related-work and positioning of an ACM PODC paper — covering the distributed-computing literature lanes (PODC/DISC/SPAA and the JACM / Distributed Computing journals), writing a model-and-bound-precise delta over prior results, distinguishing your model from neighboring ones, and keeping self-citation safe under lightweight double-blind review.
When should I use Podc Related Work?
Podc Related Work fits situations like: writing a model-and-bound-precise delta over prior results; distinguishing your model from neighboring ones; keeping self-citation safe under lightweight double-blind review.
How do I install Podc Related Work in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill podc-related-work -a claude-code`. Or copy the skill folder (PODC-Skills/skills/podc-related-work in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/podc-related-work in your project. Claude Code loads it when a task matches its description.
How do I install Podc Related Work in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill podc-related-work -a codex`. Or copy the skill folder (PODC-Skills/skills/podc-related-work in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/podc-related-work in your project. Codex loads it when a task matches its description.
Can I use Podc Related Work 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-related-work -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-related-work, .gemini/skills/podc-related-work, .github/skills/podc-related-work and .opencode/skills/podc-related-work in your project.
What does Podc Related Work need to run?
SKILL.md names no scripts, command-line tools or credentials: Podc Related Work is instructions for the agent only.
Does Podc Related Work 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 Related Work 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 Related Work use?
Podc Related Work 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 Related Work use?
About 1.4k tokens (SKILL.md is roughly 5.7k 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 Related Work?
Skills that share tags, products or a category with Podc Related Work: Ieee Paper Reader (CloudWave818/ieee-skills, 359 stars), Gec Literature Positioning (franklee16/academic-research-skills, 223 stars), Jpe Literature Positioning (franklee16/academic-research-skills, 223 stars) and Systematic Review Screener (Imbad0202/academic-research-skills, 51k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Podc Related Work?
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.