Production Audit
affaan-m/ECC
Local-evidence production readiness audit for shipped apps, pre-launch reviews, post-merge checks, and "what breaks in prod?" questions without sending repo data to an external audit service.
A skill your agent uses when auditing a PVLDB submission before a monthly deadline, covering the mandatory abstract on the 25th, the CMT window, the 1st-of-month 5:00 PM Pacific cutoff, category and…
MITAuto-check passed
Install Vldb Submission
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill vldb-submission -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills vldb-submission --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-submission .claude/skills/vldb-submission && 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-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/VLDB-Skills/skills/vldb-submission into .claude/skills/vldb-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vldb-submission", 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-submissionType 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-submission -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills vldb-submission --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-submission .agents/skills/vldb-submission && 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-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/VLDB-Skills/skills/vldb-submission into .agents/skills/vldb-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vldb-submission", 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-submission -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills vldb-submission --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-submission .cursor/skills/vldb-submission && 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-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/VLDB-Skills/skills/vldb-submission into .cursor/skills/vldb-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vldb-submission", 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-submission--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-submission -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills vldb-submission --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-submission .gemini/skills/vldb-submission && 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-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/VLDB-Skills/skills/vldb-submission into .gemini/skills/vldb-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vldb-submission", 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-submissionInstalls 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-submission -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-submission .github/skills/vldb-submission && 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-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/VLDB-Skills/skills/vldb-submission into .github/skills/vldb-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vldb-submission", 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-submission -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-submission --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-submission .opencode/skills/vldb-submission && 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-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/VLDB-Skills/skills/vldb-submission into .opencode/skills/vldb-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vldb-submission", 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-submission- GitHub stars
- 1.2k
- Token cost
- ~998 tokens
- SKILL.md length
- 415 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when auditing a PVLDB submission before a monthly deadline, covering the mandatory abstract on the 25th, the CMT window, the 1st-of-month 5:00 PM Pacific cutoff, category and…
- Works in 3 steps: 20th of the prior month — CMT opens for… → 25th of the prior month — mandatory… → 1st of the month, 5:00 PM Pacific Time —…
- Auditing a PVLDB submission before a monthly deadline
- SKILL.md covers The three clocks of one deadline, Category and budget check, Identity and caps and Pre-deadline audit sequence, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Vldb Submission is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when auditing a PVLDB submission before a monthly deadline, covering the mandatory abstract on the 25th, the CMT window, the 1st-of-month 5:00 PM Pacific cutoff, category and page-budget choice, single-blind cover-page requirements, the per-month and per-year author caps, and desk-reject hazards specific to VLDB.
Its SKILL.md is about 1000 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
- Auditing a PVLDB submission before a monthly deadline
- Covering the mandatory abstract on the 25th
- The 1st-of-month 5:00 PM Pacific cutoff
- Category and page-budget choice
Example prompts
- “/vldb-submission”
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- 20th of the prior month — CMT opens for the cycle.
- 25th of the prior month — mandatory abstract (title, authors, abstract,
- 1st of the month, 5:00 PM Pacific Time — full paper due. This is a
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 Submission loads about 998 tokens when it runs. Until then it costs about 84 tokens; SKILL.md has 415 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). 415 words, ~998 tokens.
Download SKILL.mdSave it as
.claude/skills/vldb-submission/SKILL.md (or your agent's skills folder).- name
- vldb-submission
- description
- Use when auditing a PVLDB submission before a monthly deadline, covering the mandatory abstract on the 25th, the CMT window, the 1st-of-month 5:00 PM Pacific cutoff, category and page-budget choice, single-blind cover-page requirements, the per-month and per-year author caps, and desk-reject hazards specific to VLDB.
VLDB Submission
Run this in the two weeks before a PVLDB monthly deadline. VLDB research papers enter through PVLDB (Proceedings of the VLDB Endowment), and the volume's own guidelines page — not the conference site's summary — is the governing document. Everything dated below was checked 2026-07-08; reopen the live volume page first.
The three clocks of one deadline
PVLDB splits a single submission across three dates, and missing the first one kills the cycle quietly:
- 20th of the prior month — CMT opens for the cycle.
- 25th of the prior month — mandatory abstract (title, authors, abstract, subject areas) registered in CMT. No abstract, no paper slot.
- 1st of the month, 5:00 PM Pacific Time — full paper due. This is a Pacific-clock deadline, not AoE; for most of the world it lands in the middle of the night before the date your calendar shows. No extensions.
Category and budget check
Pick the category deliberately — reviewers calibrate expectations to it:
| Category (VLDB 2026 cycle) | Body budget | What reviewers expect |
|---|---|---|
| Regular Research | 12 pp + refs | New technique with systems evidence |
| Experiment, Analysis & Benchmark | 12 pp + refs | Rigorous study; reproducibility evaluation is mandatory |
| Scalable Data Science | 8 pp + refs | Data-science pipeline at scale, practice-forward |
| Vision | 6 pp + refs | Agenda-setting argument, less evidence |
References are uncapped, but appendices and acknowledgements count inside the budget. Category continuation and budgets for the volume you target: confirm on the live page (待核实 for Vol 20 beyond the sources in the source map).
Show full SKILL.md (170 more words)Show less
Identity and caps
- PVLDB review is single-blind: author names and affiliations belong on the paper. Do not strip them the way SIGMOD or ML venues require — an anonymous PVLDB submission is a formatting error, not a virtue. Reconfirm the wording on the live guidelines before submission.
- Count coauthor load before promising a submission: Vol 20 caps each author at two papers per month and twelve per year.
- Declare conflicts accurately in CMT; the review board assignment runs on them.
Pre-deadline audit sequence
[ ] Live volume identified (Vol 20 on 2026-07-08) and its guidelines reopened
[ ] Abstract registered in CMT before the 25th, title/author list final
[ ] Category chosen; page budget measured with appendix included
[ ] Volume template applied unmodified; fonts legible at print size
[ ] Author names and affiliations present (single-blind), conflicts declared
[ ] Caps checked for every author, not just the lead
[ ] Artifact URL decided: include now or forfeit the availability signal
[ ] Deadline converted to your local time from 5:00 PM PT on the 1stWhat draws a desk rejection here
- Overrunning the category budget or squeezing with template edits.
- Submitting to a closed cycle because the abstract step was missed.
- A cover page missing authors, or CMT metadata contradicting the PDF.
- Blowing an author's cap — the excess paper, not the earliest, is at risk.
One month's miss costs exactly one month — the next cycle opens on the 20th. Submitting a half-ready paper to "make this month" wastes a cap slot and burns the one revision the process will ever offer.
Output format
[Cycle] <volume / month targeted>
[Abstract stage] registered / at risk / missed
[Category + budget] <category, pages used vs. limit>
[Identity check] single-blind cover page complete / issues
[Cap status] <per-author counts vs. month and year caps>
[Blocking fixes] <ordered, with owner>© 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-submission of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Vldb Submission 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 Submission this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~998 | Automated safety check: Pass | MIT | |
| Production Auditaffaan-m/ECC | 277k | 1 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Aims Auditalirezarezvani/claude-skills | 28k | — | ~1.3k | Automated safety check: Pass | MIT | |
| Geo Auditsickn33/agentic-awesome-skills | 47k | 1 repos | ~3.4k | Automated safety check: Notes | MIT | |
| OmniRoute Audit and Policy CLIdiegosouzapw/OmniRoute | 75k | — | ~733 | Automated safety check: Pass | MIT | |
| Audit Preparationsickn33/agentic-awesome-skills | 47k | 1 repos | ~5.3k | Automated safety check: Pass | MIT |
Similar skills
Aims Audit
alirezarezvani/claude-skills
/cs:aims-audit <scope — ISO/IEC 42001 AIMS internal-audit 6-question forcing interrogation.
Geo Audit
sickn33/agentic-awesome-skills
Full website GEO+SEO audit with parallel subagent delegation.
OmniRoute Audit and Policy CLI
diegosouzapw/OmniRoute
Command reference for omniroute's audit, logs, policy and telemetry commands: search and export audit trails, manage access policies and review request history for compliance work.
Audit Preparation
sickn33/agentic-awesome-skills
Audit preparation register: required document, period covered, request and receipt dates, preparer and reviewer, auditor queries and adjustments.
Qms Audit Expert
davila7/claude-code-templates
Senior QMS Audit Expert for internal and external quality management system auditing.
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 Submission
What does Vldb Submission do?
A skill your agent uses when auditing a PVLDB submission before a monthly deadline, covering the mandatory abstract on the 25th, the CMT window, the 1st-of-month 5:00 PM Pacific cutoff, category and…. Vldb Submission is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when auditing a PVLDB submission before a monthly deadline, covering the mandatory abstract on the 25th, the CMT window, the 1st-of-month 5:00 PM Pacific cutoff, category and page-budget choice, single-blind cover-page requirements, the per-month and per-year author caps, and desk-reject hazards specific to VLDB.
When should I use Vldb Submission?
Vldb Submission fits situations like: auditing a PVLDB submission before a monthly deadline; covering the mandatory abstract on the 25th; the 1st-of-month 5:00 PM Pacific cutoff; category and page-budget choice.
How do I install Vldb Submission in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill vldb-submission -a claude-code`. Or copy the skill folder (VLDB-Skills/skills/vldb-submission in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/vldb-submission in your project. Claude Code loads it when a task matches its description.
How do I install Vldb Submission in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill vldb-submission -a codex`. Or copy the skill folder (VLDB-Skills/skills/vldb-submission in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/vldb-submission in your project. Codex loads it when a task matches its description.
Can I use Vldb Submission 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-submission -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-submission, .gemini/skills/vldb-submission, .github/skills/vldb-submission and .opencode/skills/vldb-submission in your project.
What does Vldb Submission need to run?
SKILL.md names no scripts, command-line tools or credentials: Vldb Submission is instructions for the agent only.
Does Vldb Submission 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 Submission 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 Submission use?
Vldb Submission 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 Submission use?
About 998 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 Submission?
Skills that share tags, products or a category with Vldb Submission: Production Audit (affaan-m/ECC, 277k stars), Aims Audit (alirezarezvani/claude-skills, 28k stars), Geo Audit (sickn33/agentic-awesome-skills, 47k stars) and OmniRoute Audit and Policy CLI (diegosouzapw/OmniRoute, 75k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Vldb Submission?
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.