Literature Review
neflibata-feng/MyArxiv-Agent
Conduct comprehensive, systematic literature reviews using multiple academic databases (PubMed, arXiv, bioRxiv, Semantic Scholar, etc.).
A skill your agent uses when positioning a Web Conference (WWW) submission against prior literature — tracing lineage through three decades of WWW proceedings, contrasting with the…
Install Webconf Related Work
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill webconf-related-work -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills webconf-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/The-Web-Conference-Skills/skills/webconf-related-work .claude/skills/webconf-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 "webconf-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/The-Web-Conference-Skills/skills/webconf-related-work into .claude/skills/webconf-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "webconf-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/The-Web-Conference-Skills/skills/webconf-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 webconf-related-work -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills webconf-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/The-Web-Conference-Skills/skills/webconf-related-work .agents/skills/webconf-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 "webconf-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/The-Web-Conference-Skills/skills/webconf-related-work into .agents/skills/webconf-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "webconf-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 webconf-related-work -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills webconf-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/The-Web-Conference-Skills/skills/webconf-related-work .cursor/skills/webconf-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 "webconf-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/The-Web-Conference-Skills/skills/webconf-related-work into .cursor/skills/webconf-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "webconf-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 The-Web-Conference-Skills/skills/webconf-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 webconf-related-work -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills webconf-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/The-Web-Conference-Skills/skills/webconf-related-work .gemini/skills/webconf-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 "webconf-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/The-Web-Conference-Skills/skills/webconf-related-work into .gemini/skills/webconf-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "webconf-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 webconf-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 webconf-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/The-Web-Conference-Skills/skills/webconf-related-work .github/skills/webconf-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 "webconf-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/The-Web-Conference-Skills/skills/webconf-related-work into .github/skills/webconf-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "webconf-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 webconf-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 webconf-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/The-Web-Conference-Skills/skills/webconf-related-work .opencode/skills/webconf-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 "webconf-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/The-Web-Conference-Skills/skills/webconf-related-work into .opencode/skills/webconf-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "webconf-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
webconf-related-work- GitHub stars
- 1.2k
- Token cost
- ~1.8k tokens
- SKILL.md length
- 837 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when positioning a Web Conference (WWW) submission against prior literature — tracing lineage through three decades of WWW proceedings, contrasting with the…
- Positioning a Web Conference (WWW) submission against prior literature — tracing lineage through three decades of WWW proceedings
- SKILL.md covers Lineage first, novelty second, The sibling-circuit contrast…, Venue-attribution hygiene and The preprint rule shapes…, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Contrasting with the WSDM/CIKM/SIGIR/KDD sibling circuit
What it does
Webconf Related Work is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when positioning a Web Conference (WWW) submission against prior literature — tracing lineage through three decades of WWW proceedings, contrasting with the WSDM/CIKM/SIGIR/KDD sibling circuit, handling the venue's preprint-non-citation rule, and budgeting references against the shared 12-page PDF tail.
Its SKILL.md is about 1.8k 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, Academic paper search and Budgeting and forecasting. 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
- Positioning a Web Conference (WWW) submission against prior literature — tracing lineage through three decades of WWW proceedings
- Contrasting with the WSDM/CIKM/SIGIR/KDD sibling circuit
- Handling the venues preprint-non-citation rule
- Budgeting references against the shared 12-page PDF tail
Example prompts
- “/webconf-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
Webconf Related Work loads about 1.8k tokens when it runs. Until then it costs about 82 tokens; SKILL.md has 837 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). 837 words, ~1,774 tokens.
Download SKILL.mdSave it as
.claude/skills/webconf-related-work/SKILL.md (or your agent's skills folder).- name
- webconf-related-work
- description
- Use when positioning a Web Conference (WWW) submission against prior literature — tracing lineage through three decades of WWW proceedings, contrasting with the WSDM/CIKM/SIGIR/KDD sibling circuit, handling the venue's preprint-non-citation rule, and budgeting references against the shared 12-page PDF tail.
Web Conference Related Work
Related work at this venue does two jobs the generic version skips: it proves the paper knows its WWW lineage (the series runs to 1994, and many web problems have decade-old ancestors reviewers personally remember), and it draws the line against the sibling circuit — WSDM, CIKM, SIGIR, KDD, ICWSM, WebSci — whose reviewer pools overlap heavily with the track panels judging you.
Lineage first, novelty second
Web research recycles its problems as the platform layer changes: link spam → social spam → LLM-generated content; PageRank-era graph analysis → network embeddings → graph neural networks; forum mining → microblog mining → short-video mining. A strong related-work section names the lineage explicitly and locates the contribution at the newest turn:
Weak: "Graph embedding has been widely studied [3,7,12,19]."
Strong: "Web-graph representation moved from link-analysis scores through
embedding objectives (LINE, WWW 2015) to message-passing models
(HAN, WWW 2019); all assume a static snapshot. Our setting -- edges
arriving from a live crawl -- breaks that assumption because ..."The pattern: two or three named waypoints with venues and years, then the assumption every waypoint shares, then why your setting breaks it. One paragraph of this outperforms twenty grouped citations.
The sibling-circuit contrast table
Reviewers here habitually ask "why is this not a WSDM/SIGIR/KDD paper?" Answer inside related work by contrasting evidence norms, not prestige:
| Neighbor | Its center of gravity | Your contrast sentence should say |
|---|---|---|
| WSDM | Web search & mining methods, offline rigor | what your paper adds beyond the method: platform mechanism, measurement, or system |
| SIGIR | Retrieval effectiveness & evaluation | why the web setting (adversaries, freshness, heterogeneity) changes the retrieval problem |
| KDD | Mining methods & deployed data science | what is web-structural rather than generic-tabular/graph |
| CIKM | Broad IR/DB/KM methods | the sharper web claim that the broad venue wouldn't demand |
| ICWSM | Social-media measurement | your computational/methodological delta beyond measurement |
| WebSci | Interdisciplinary web studies | your technical contribution beyond the socio-technical finding |
Cite the nearest paper from each relevant neighbor when one exists; its authors may well be your reviewers, and omitting them reads as either ignorance or evasion.
Venue-attribution hygiene
Misattributing a classic to the wrong venue is a credibility wound with expert
panels. Traps specific to this literature: the PageRank algorithm report is a
Stanford technical report while the search-engine paper (Brin & Page) appeared at
WWW7 1998 in a journal-published proceedings; several "web" classics actually live
at KDD or SIGIR; and the series' own name changed (WWW → The Web Conference, 2018;
ACM Web Conference era from 2022) so citation styles vary across decades. Verify
every load-bearing citation against dblp or the ACM DL — this pack's
resources/exemplars/library.md records five verified WWW papers safe to cite as
lineage waypoints.
The preprint rule shapes citation practice
Two verified 2026 rules interact here: submissions must be original (nothing under review or published elsewhere), and your own anonymized preprint may exist on arXiv/SSRN but the submission must not cite it. For third-party preprints, cite them when they are the real prior art — with arXiv IDs and honest framing as non-archival — but do not treat an uncited arXiv posting as license to claim novelty over it; track reviewers in fast-moving areas (retrieval-augmented AI especially) read arXiv daily. Concurrent work merits a labeled paragraph: "Concurrent and independent: [X] (arXiv, Sep 2025) addresses ...; we differ in ..."
Show full SKILL.md (349 more words)Show less
Budgeting against the shared tail
References and appendix split the same 4-page PDF tail (12 total minus 8 main). Reference-list discipline is therefore a space decision: cite the survey plus the directly-contrasted papers rather than every member of a lineage; drop redundant multi-citations ("[3,7,12,19]" where only [12] is discussed); prefer one recent strong baseline citation over three historical weak ones. A typical healthy budget here is 1.5-2 pages of references, preserving 2+ pages of appendix.
A two-pass drafting workflow
Pass 1, coverage (weeks before the deadline): harvest candidates from the last two proceedings of WWW plus the relevant sibling venue, the track's likely reviewer bibliographies, and the citation graphs of your three closest papers. Verify each candidate's venue on dblp at harvest time — batching verification for later is how misattributions survive into the submission. Pass 2, argument (with the draft stable): delete every citation the text does not discuss, write the lineage paragraph and the sibling-contrast sentences, and re-run a final search two weeks before the deadline for the fast-moving tracks — a September arXiv posting in retrieval-augmented AI can become the rebuttal's central objection if the October submission ignores it.
Ordering heuristic inside the section: lineage first (establishes you belong), nearest neighbors second (establishes the delta), adjacent-discipline anchors last (establishes construct credibility for the mixed panel). The common inverse — starting with a broad sociology-of-the-web sweep — spends the section's best real estate before reaching the papers reviewers will actually compare you to.
Pre-submission checklist
- Lineage paragraph with named, venue-attributed waypoints and the shared assumption your setting breaks.
- One contrast sentence per relevant sibling venue; nearest-neighbor papers from the current and previous cycle cited.
- Every classic verified against dblp/ACM DL; no venue misattributions.
- Own preprint uncited; concurrent work labeled; no novelty claims over papers the section pretends not to know.
- Reference pages counted against the appendix budget.
A final self-test: hand the section to a co-author and ask which two papers a reviewer would demand comparison against. If their answer names a paper the section does not cite, the coverage pass failed regardless of how many references it holds.
Output format
[Lineage] <waypoints named> -> <shared assumption broken>
[Sibling contrasts] WSDM/SIGIR/KDD/CIKM/ICWSM/WebSci: <which drafted, which N/A>
[Attribution audit] <misattributions found and fixed>
[Preprint handling] own-preprint uncited: yes/no; concurrent-work paragraph: yes/no
[Tail cost] references=<pages>, appendix room left=<pages>© 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 The-Web-Conference-Skills/skills/webconf-related-work of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Webconf 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 |
|---|---|---|---|---|---|---|
| Webconf Related Work this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.8k | Automated safety check: Pass | MIT | |
| Literature Reviewneflibata-feng/MyArxiv-Agent | 126 | 20 repos | ~5.9k | Automated safety check: Notes | MIT | |
| Preprint Search on bioRxivLigphiDonk/Oh-my--paper | 739 | 12 repos | ~3.7k | Automated safety check: Pass | MIT | |
| Systematic Literature Review Builderbytedance/deer-flow | 84k | 2 repos | ~4.3k | Automated safety check: Pass | MIT | |
| Paper Research on arXivXiaomiMiMo/MiMo-Code | 14k | — | ~1.5k | Automated safety check: Pass | MIT | |
| Literature Review AgentAr9av/PaperOrchestra | 679 | 1 repos | ~5.2k | Automated safety check: Pass | Custom licence |
Similar skills
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.
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.
Paper Research on arXiv
XiaomiMiMo/MiMo-Code
Searches arXiv, fetches metadata, generates BibTeX, downloads PDFs and finds citations and related papers using a bundled Python script.
Literature Review Agent
Ar9av/PaperOrchestra
Step 3 of the PaperOrchestra pipeline (arXiv:2604.05018). An agent skill from Ar9av/PaperOrchestra.
Autonomous Research
federicodeponte/opendraft
An 18-agent pipeline that turns one topic line into a drafted research paper, literature review, or thesis chapter.
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 Webconf Related Work
What does Webconf Related Work do?
A skill your agent uses when positioning a Web Conference (WWW) submission against prior literature — tracing lineage through three decades of WWW proceedings, contrasting with the…. Webconf Related Work is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when positioning a Web Conference (WWW) submission against prior literature — tracing lineage through three decades of WWW proceedings, contrasting with the WSDM/CIKM/SIGIR/KDD sibling circuit, handling the venue's preprint-non-citation rule, and budgeting references against the shared 12-page PDF tail.
When should I use Webconf Related Work?
Webconf Related Work fits situations like: positioning a Web Conference (WWW) submission against prior literature — tracing lineage through three decades of WWW proceedings; contrasting with the WSDM/CIKM/SIGIR/KDD sibling circuit; handling the venues preprint-non-citation rule; budgeting references against the shared 12-page PDF tail.
How do I install Webconf Related Work in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill webconf-related-work -a claude-code`. Or copy the skill folder (The-Web-Conference-Skills/skills/webconf-related-work in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/webconf-related-work in your project. Claude Code loads it when a task matches its description.
How do I install Webconf Related Work in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill webconf-related-work -a codex`. Or copy the skill folder (The-Web-Conference-Skills/skills/webconf-related-work in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/webconf-related-work in your project. Codex loads it when a task matches its description.
Can I use Webconf 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 webconf-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/webconf-related-work, .gemini/skills/webconf-related-work, .github/skills/webconf-related-work and .opencode/skills/webconf-related-work in your project.
What does Webconf Related Work need to run?
SKILL.md names no scripts, command-line tools or credentials: Webconf Related Work is instructions for the agent only.
Does Webconf 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 Webconf 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 Webconf Related Work use?
Webconf 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 Webconf Related Work use?
About 1.8k tokens (SKILL.md is roughly 7.1k 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 Webconf Related Work?
Skills that share tags, products or a category with Webconf Related Work: Literature Review (neflibata-feng/MyArxiv-Agent, 126 stars), Preprint Search on bioRxiv (LigphiDonk/Oh-my--paper, 739 stars), Systematic Literature Review Builder (bytedance/deer-flow, 84k stars) and Paper Research on arXiv (XiaomiMiMo/MiMo-Code, 14k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Webconf 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.