Gec Literature Positioning
franklee16/academic-research-skills
A skill your agent uses when positioning a Global Environmental Change (GEC) manuscript against the relevant literatures.
A skill your agent uses when positioning a PVLDB submission against prior literature, covering the deep database canon back to the 1980s VLDB proceedings, the SIGMOD/ICDE/CIDR neighborhood…
Install Vldb Related Work
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill vldb-related-work -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills vldb-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/VLDB-Skills/skills/vldb-related-work .claude/skills/vldb-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 "vldb-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/VLDB-Skills/skills/vldb-related-work into .claude/skills/vldb-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vldb-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/VLDB-Skills/skills/vldb-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 vldb-related-work -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills vldb-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/VLDB-Skills/skills/vldb-related-work .agents/skills/vldb-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 "vldb-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/VLDB-Skills/skills/vldb-related-work into .agents/skills/vldb-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vldb-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 vldb-related-work -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills vldb-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/VLDB-Skills/skills/vldb-related-work .cursor/skills/vldb-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 "vldb-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/VLDB-Skills/skills/vldb-related-work into .cursor/skills/vldb-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vldb-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 VLDB-Skills/skills/vldb-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 vldb-related-work -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills vldb-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/VLDB-Skills/skills/vldb-related-work .gemini/skills/vldb-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 "vldb-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/VLDB-Skills/skills/vldb-related-work into .gemini/skills/vldb-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vldb-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 vldb-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 vldb-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/VLDB-Skills/skills/vldb-related-work .github/skills/vldb-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 "vldb-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/VLDB-Skills/skills/vldb-related-work into .github/skills/vldb-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vldb-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 vldb-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 vldb-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/VLDB-Skills/skills/vldb-related-work .opencode/skills/vldb-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 "vldb-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/VLDB-Skills/skills/vldb-related-work into .opencode/skills/vldb-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vldb-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
vldb-related-work- GitHub stars
- 1.2k
- Token cost
- ~1k tokens
- SKILL.md length
- 427 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 PVLDB submission against prior literature, covering the deep database canon back to the 1980s VLDB proceedings, the SIGMOD/ICDE/CIDR neighborhood…
- Works in 3 steps: The deep canon (1975-2000) —… → The modern venue ring — PVLDB itself,… → Running code — features shipped in…
- Positioning a PVLDB submission against prior literature
- SKILL.md covers The reinvention audit, Lane coverage check, Concurrency on a rolling… and Extended versions and overlap, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Vldb Related Work is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when positioning a PVLDB submission against prior literature, covering the deep database canon back to the 1980s VLDB proceedings, the SIGMOD/ICDE/CIDR neighborhood, concurrent work under rolling monthly deadlines, industrial and open-source systems as citable prior art, and overlap declarations for extended versions.
Its SKILL.md is about 1k 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, Intellectual property 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
- Positioning a PVLDB submission against prior literature
- Covering the deep database canon back to the 1980s VLDB proceedings
- The SIGMOD/ICDE/CIDR neighborhood
- Concurrent work under rolling monthly deadlines
Example prompts
- “/vldb-related-work”
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- The deep canon (1975-2000) — partitioning, replication, buffering,
- The modern venue ring — PVLDB itself, SIGMOD/PACMMOD, ICDE, EDBT,
- Running code — features shipped in PostgreSQL, RocksDB, DuckDB, Spark,
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
Vldb Related Work loads about 1k tokens when it runs. Until then it costs about 85 tokens; SKILL.md has 427 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). 427 words, ~1,011 tokens.
Download SKILL.mdSave it as
.claude/skills/vldb-related-work/SKILL.md (or your agent's skills folder).- name
- vldb-related-work
- description
- Use when positioning a PVLDB submission against prior literature, covering the deep database canon back to the 1980s VLDB proceedings, the SIGMOD/ICDE/CIDR neighborhood, concurrent work under rolling monthly deadlines, industrial and open-source systems as citable prior art, and overlap declarations for extended versions.
VLDB Related Work
Use this to pressure-test novelty before writing the contribution list. The database field has forty-plus years of proceedings and a reviewer pool with long memories; the classic VLDB rejection is not "compared badly" but "reinvented, without knowing it."
The reinvention audit
Before claiming a technique is new, sweep three strata:
- The deep canon (1975-2000) — partitioning, replication, buffering, adaptive query processing, and materialization ideas recur under new hardware. Search old VLDB/SIGMOD proceedings and TODS for the mechanism, not today's terminology for it.
- The modern venue ring — PVLDB itself, SIGMOD/PACMMOD, ICDE, EDBT, CIDR, plus the systems conferences (SOSP/OSDI, NSDI, EuroSys) where storage and dataflow work also lands.
- Running code — features shipped in PostgreSQL, RocksDB, DuckDB, Spark, or the cloud warehouses count as prior art whether or not a paper exists. Citing a system's documentation is normal here; pretending an implemented idea is unpublished is a rejection with a hyperlink.
If the mechanism existed, the honest contribution is the delta: new hardware assumptions, new scale, new workload class, or the first measured comparison.
Lane coverage check
| Literature lane | The reviewer question it answers |
|---|---|
| Classic DB canon | Did they know this was tried in 1994? |
| Current PVLDB/SIGMOD/ICDE | Is the nearest recent method compared or distinguished? |
| Systems venues | Is the OS/distributed-systems version of this idea acknowledged? |
| Industrial systems & open source | Does a shipping engine already do it? |
| Theory (PODS/ICDT) | Are known bounds or hardness results respected? |
A related-work section drawing on only one lane signals a half-searched field.
Show full SKILL.md (178 more words)Show less
Concurrency on a rolling calendar
Monthly deadlines mean near-neighbors surface during your review window.
- Sweep arXiv and the latest PVLDB issues in the week before your abstract registration; issues appear monthly, not annually.
- Work published after your submission date is concurrent: acknowledge it in the revision or camera-ready neutrally, without priority anxiety.
- If a concurrent paper lands mid-revision, address it in the change document factually — the same board is likely reviewing both.
Extended versions and overlap
- Prior workshop or demo versions: declare them and state the delta; a PVLDB research paper must carry substantial new content over them (exact overlap thresholds: 待核实 on the live volume guidelines).
- Do not hold the same work under review at PVLDB and another venue simultaneously; rolling cadence makes "just try both" tempting and detectable — the communities share a review pool.
- The later journal expansion (The VLDB Journal, TODS) is the sanctioned lane for outgrowing the 12 pages.
Writing the positioning paragraphs
Per nearest neighbor (3-5 of them):
[Name + venue + year] does <mechanism> under <assumption>.
We differ in <assumption/scale/workload>, which matters because <consequence>.
Compared in §<eval section> / not comparable because <honest reason>.Group remaining citations by problem, one clause of contrast each. A citation without a contrast is bibliography, not positioning.
Output format
[Reinvention audit] clean / hits found (mechanism, source, year)
[Lane coverage] <lanes with gaps>
[Nearest neighbors] <3-5, each with the distinguishing assumption>
[Concurrent-work watch] <items surfaced this month>
[Overlap declarations] <prior versions and their deltas>
[Novelty sentence] <one sentence a skeptical builder would accept>© 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 VLDB-Skills/skills/vldb-related-work of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Vldb 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 |
|---|---|---|---|---|---|---|
| Vldb Related Work this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1k | Automated safety check: Pass | MIT | |
| Gec Literature Positioningfranklee16/academic-research-skills | 223 | 1 repos | ~855 | Automated safety check: Pass | None | |
| Jpsp Literature Positioningfranklee16/academic-research-skills | 223 | 1 repos | ~850 | Automated safety check: Pass | None | |
| Rje Literature Positioningfranklee16/academic-research-skills | 223 | 1 repos | ~720 | Automated safety check: Pass | None | |
| Icml Related Workfranklee16/academic-research-skills | 223 | 1 repos | ~402 | Automated safety check: Pass | None | |
| NeuroarxivUditAkhourii/neuroarxiv | 433 | — | ~3.1k | Automated safety check: Pass | MIT |
Similar skills
Jpsp Literature Positioning
franklee16/academic-research-skills
A skill your agent uses when positioning a Journal of Personality and Social Psychology (JPSP) manuscript against the literatures its section's readers expect, building the long-format introduction…
Rje Literature Positioning
franklee16/academic-research-skills
A skill your agent uses to position a manuscript against the industrial-organization frontier for The RAND Journal of Economics (RJE) — staking the contribution against prior IO work without a…
Icml Related Work
franklee16/academic-research-skills
A skill your agent uses when positioning an ICML submission against close ML literature, concurrent ICML submissions, recent public papers, workshop papers, ICLR/AISTATS/NeurIPS neighbors, and prior…
Neuroarxiv
UditAkhourii/neuroarxiv
Grounds a coding agent's architecture decisions in real arXiv prior art before it builds something new.
Deltasci Ground
boheling/deltasci
The grounding layer for AI-assisted research: scan the real prior art around an idea, gauge how crowded or open the gap is, and verify every citation against the source of truth.
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 Vldb Related Work
What does Vldb Related Work do?
A skill your agent uses when positioning a PVLDB submission against prior literature, covering the deep database canon back to the 1980s VLDB proceedings, the SIGMOD/ICDE/CIDR neighborhood…. Vldb Related Work is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when positioning a PVLDB submission against prior literature, covering the deep database canon back to the 1980s VLDB proceedings, the SIGMOD/ICDE/CIDR neighborhood, concurrent work under rolling monthly deadlines, industrial and open-source systems as citable prior art, and overlap declarations for extended versions.
When should I use Vldb Related Work?
Vldb Related Work fits situations like: positioning a PVLDB submission against prior literature; covering the deep database canon back to the 1980s VLDB proceedings; the SIGMOD/ICDE/CIDR neighborhood; concurrent work under rolling monthly deadlines.
How do I install Vldb Related Work in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill vldb-related-work -a claude-code`. Or copy the skill folder (VLDB-Skills/skills/vldb-related-work in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/vldb-related-work in your project. Claude Code loads it when a task matches its description.
How do I install Vldb Related Work in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill vldb-related-work -a codex`. Or copy the skill folder (VLDB-Skills/skills/vldb-related-work in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/vldb-related-work in your project. Codex loads it when a task matches its description.
Can I use Vldb 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 vldb-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/vldb-related-work, .gemini/skills/vldb-related-work, .github/skills/vldb-related-work and .opencode/skills/vldb-related-work in your project.
What does Vldb Related Work need to run?
SKILL.md names no scripts, command-line tools or credentials: Vldb Related Work is instructions for the agent only.
Does Vldb 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 Vldb 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 Vldb Related Work use?
Vldb 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 Vldb Related Work use?
About 1k tokens (SKILL.md is roughly 4k 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 Vldb Related Work?
Skills that share tags, products or a category with Vldb Related Work: Gec Literature Positioning (franklee16/academic-research-skills, 223 stars), Jpsp Literature Positioning (franklee16/academic-research-skills, 223 stars), Rje Literature Positioning (franklee16/academic-research-skills, 223 stars) and Icml Related Work (franklee16/academic-research-skills, 223 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Vldb 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.