Deepseek Reason
ruvnet/ruflo
Reasoning-mode completion against DeepSeek's deepseek-reasoner model (R1) via /v1/chat/completions.
A skill your agent uses when reasoning about how PVLDB reviewing actually works, covering the rolling monthly pipeline, the roughly six-week review turnaround, the accept/revise/reject outcome…
MITAuto-check passed
Install Vldb Review Process
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill vldb-review-process -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills vldb-review-process --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-review-process .claude/skills/vldb-review-process && 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-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/VLDB-Skills/skills/vldb-review-process into .claude/skills/vldb-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vldb-review-process", 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-review-processType 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-review-process -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills vldb-review-process --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-review-process .agents/skills/vldb-review-process && 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-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/VLDB-Skills/skills/vldb-review-process into .agents/skills/vldb-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vldb-review-process", 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-review-process -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills vldb-review-process --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-review-process .cursor/skills/vldb-review-process && 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-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/VLDB-Skills/skills/vldb-review-process into .cursor/skills/vldb-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vldb-review-process", 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-review-process--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-review-process -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills vldb-review-process --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-review-process .gemini/skills/vldb-review-process && 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-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/VLDB-Skills/skills/vldb-review-process into .gemini/skills/vldb-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vldb-review-process", 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-review-processInstalls 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-review-process -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-review-process .github/skills/vldb-review-process && 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-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/VLDB-Skills/skills/vldb-review-process into .github/skills/vldb-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vldb-review-process", 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-review-process -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-review-process --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-review-process .opencode/skills/vldb-review-process && 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-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/VLDB-Skills/skills/vldb-review-process into .opencode/skills/vldb-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vldb-review-process", 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-review-process- GitHub stars
- 1.2k
- Token cost
- ~1k tokens
- SKILL.md length
- 419 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when reasoning about how PVLDB reviewing actually works, covering the rolling monthly pipeline, the roughly six-week review turnaround, the accept/revise/reject outcome…
- Reasoning about how PVLDB reviewing actually works
- SKILL.md covers The pipeline at a glance, What each outcome means here, Who is reading and Reading reviews on the monthly…, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Covering the rolling monthly pipeline
What it does
Vldb Review Process is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when reasoning about how PVLDB reviewing actually works, covering the rolling monthly pipeline, the roughly six-week review turnaround, the accept/revise/reject outcome space, the one-shot revision's odds, single-blind dynamics, the volume review board, and how a VLDB decision differs from batch-deadline venues.
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.
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
- Reasoning about how PVLDB reviewing actually works
- Covering the rolling monthly pipeline
- The roughly six-week review turnaround
- The accept/revise/reject outcome space
Example prompts
- “/vldb-review-process”
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 Review Process loads about 1k tokens when it runs. Until then it costs about 84 tokens; SKILL.md has 419 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). 419 words, ~1,048 tokens.
Download SKILL.mdSave it as
.claude/skills/vldb-review-process/SKILL.md (or your agent's skills folder).- name
- vldb-review-process
- description
- Use when reasoning about how PVLDB reviewing actually works, covering the rolling monthly pipeline, the roughly six-week review turnaround, the accept/revise/reject outcome space, the one-shot revision's odds, single-blind dynamics, the volume review board, and how a VLDB decision differs from batch-deadline venues.
VLDB Review Process
Use this to set expectations after (or before) a PVLDB submission. The process is a journal pipeline wearing a conference badge: a standing review board for the volume, decisions on a monthly cadence, and a revision outcome with teeth. Details below were verified 2026-07-08 for Vols 19/20; the live guidelines page governs.
The pipeline at a glance
25th: abstract -> 1st: paper (5PM PT) -> ~15th next month: reviews + verdict
|
accept ---------------- 3 outcomes ---------------- reject
|
revise (one-shot)
|
up to 3 months -> revised paper -> same reviewers
|
accept or rejectRoughly six weeks from deadline to decision is the structural promise of the rolling model — competitive with any CS venue — and the price is that there is no rebuttal stage: your first chance to talk back is the revision, if offered.
What each outcome means here
| Outcome | Practical meaning | Your move |
|---|---|---|
| Accept | Publication in an upcoming monthly issue; conference slot at the matching VLDB | Camera-ready discipline (vldb-camera-ready) |
| Revise | Reviewers believe a specific, listed set of fixes could flip them | Requirement ledger + three-month plan (vldb-author-response) |
| Reject | The paper as framed did not convince this panel | Rework before any re-entry; check current re-submission rules (待核实 whether an embargo applies) |
A revise verdict is genuinely positive signal — the board spends its future reviewing time only on papers it considers rescuable.
Who is reading
- The volume operates with Editors-in-Chief (who double as the conference PC chairs — Vol 20: Boehm and Hose per secondary sources) atop a standing review board assembled for the volume.
- Expect builder-reviewers: people who wrote storage engines, optimizers, and the baselines you measured. Implementation hand-waving and untuned competitors are caught by lived experience, not by checklists.
- Review is single-blind: reviewers see your names. Track records cut both ways — a known group gets less benefit of the doubt for overclaiming, not more.
Show full SKILL.md (149 more words)Show less
Reading reviews on the monthly clock
- The verdict letter's required-changes list is the only text that matters for a revise; reviewer musings outside it are advisory.
- For a reject, extract the decision reason (novelty vs. evidence vs. fit) before touching the draft — rolling venues tempt authors into resubmitting cosmetically-edited papers at machine-gun pace, and review boards notice.
- Timing tactics around "easier months" are folklore; the board is standing and the bar does not oscillate. Pick the month your evidence is ready.
Contrast with batch venues
At a batch-deadline conference a rejection costs a year and a rebuttal is a 480-word ritual; at PVLDB a rejection costs a rework cycle, and the revision is a real second review with new evidence allowed. Optimize accordingly: at this venue, holding a submission until the weakest experiment is fixed is cheap, and burning the revision on a preventable flaw is expensive.
Output format
[Stage] pre-submission / under review / revise / rejected / accepted
[Clock position] <deadline used, expected decision date>
[Outcome analysis] <required-changes list or decision reason>
[Panel model] <likely reviewer profile for this topic>
[Next move] <hold, revise per ledger, rework, or camera-ready>
[Rules to reverify] <re-submission terms, current escalation channel>© 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-review-process of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Vldb Review Process 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 Review Process this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1k | Automated safety check: Pass | MIT | |
| Deepseek Reasonruvnet/ruflo | 74k | — | ~626 | Automated safety check: Notes | MIT | |
| Ejentum Reasoning Harnesssickn33/agentic-awesome-skills | 47k | 1 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Nowait Reasoning Optimizerdavila7/claude-code-templates | 33k | 2 repos | ~1.2k | Automated safety check: Pass | MIT | |
| ActualizeNeoLabHQ/context-engineering-kit | 1.8k | — | ~932 | Automated safety check: Pass | GPL-3.0 | |
| Recall Reasoningparcadei/Continuous-Claude-v3 | 3.9k | 1 repos | ~758 | Automated safety check: Pass | MIT |
Similar skills
Ejentum Reasoning Harness
sickn33/agentic-awesome-skills
MCP server exposing four cognitive harness modes (reasoning, code, anti-deception, memory).
Nowait Reasoning Optimizer
davila7/claude-code-templates
Implements the NOWAIT technique for efficient reasoning in R1-style LLMs.
Actualize
NeoLabHQ/context-engineering-kit
Reconcile the project's FPF state with recent repository changes
Recall Reasoning
parcadei/Continuous-Claude-v3
Search past reasoning for relevant decisions and approaches. An agent skill from parcadei/Continuous-Claude-v3.
- Official
Nv Reason Cxr
NVIDIA/skills
Used for command-shape or live NV-Reason-CXR chest X-ray reasoning smoke tests.
More from brycewang-stanford/Awesome-Journal-Skills
All 2,387 skills in this repoAaag Data Analysis
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running and reporting the analysis for an Annals of the American Association of Geographers manuscript — spatial statistics and modeling, remote-sensing accuracy, or…
Aaag Literature Positioning
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when positioning an Annals of the American Association of Geographers manuscript in the literature — engaging geographic scholarship across the relevant area and the…
Aaag Rebuttal
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when responding to an Annals of the American Association of Geographers decision letter (major/minor revision) — building a point-by-point response to the subject editor and…
Aaag Research Design
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when defending the research design of an Annals of the American Association of Geographers manuscript — spatial/quantitative analysis and GIScience, remote-sensing and…
Aaag Review Process
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when you need to understand how the Annals of the American Association of Geographers evaluates a manuscript — double-anonymous review routed through a subject editor by…
Aaag Submission
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running the final pre-submission preflight for the Annals of the American Association of Geographers via ScholarOne Manuscripts — area/article-type selection…
Questions about Vldb Review Process
What does Vldb Review Process do?
A skill your agent uses when reasoning about how PVLDB reviewing actually works, covering the rolling monthly pipeline, the roughly six-week review turnaround, the accept/revise/reject outcome…. Vldb Review Process is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when reasoning about how PVLDB reviewing actually works, covering the rolling monthly pipeline, the roughly six-week review turnaround, the accept/revise/reject outcome space, the one-shot revision's odds, single-blind dynamics, the volume review board, and how a VLDB decision differs from batch-deadline venues.
When should I use Vldb Review Process?
Vldb Review Process fits situations like: reasoning about how PVLDB reviewing actually works; covering the rolling monthly pipeline; the roughly six-week review turnaround; the accept/revise/reject outcome space.
How do I install Vldb Review Process in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill vldb-review-process -a claude-code`. Or copy the skill folder (VLDB-Skills/skills/vldb-review-process in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/vldb-review-process in your project. Claude Code loads it when a task matches its description.
How do I install Vldb Review Process in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill vldb-review-process -a codex`. Or copy the skill folder (VLDB-Skills/skills/vldb-review-process in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/vldb-review-process in your project. Codex loads it when a task matches its description.
Can I use Vldb Review Process 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-review-process -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-review-process, .gemini/skills/vldb-review-process, .github/skills/vldb-review-process and .opencode/skills/vldb-review-process in your project.
What does Vldb Review Process need to run?
SKILL.md names no scripts, command-line tools or credentials: Vldb Review Process is instructions for the agent only.
Does Vldb Review Process 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 Review Process 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 Review Process use?
Vldb Review Process 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 Review Process use?
About 1k tokens (SKILL.md is roughly 4.2k 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 Review Process?
Skills that share tags, products or a category with Vldb Review Process: Deepseek Reason (ruvnet/ruflo, 74k stars), Ejentum Reasoning Harness (sickn33/agentic-awesome-skills, 47k stars), Nowait Reasoning Optimizer (davila7/claude-code-templates, 33k stars) and Actualize (NeoLabHQ/context-engineering-kit, 1.8k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Vldb Review Process?
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.