Avoid AI Writing
conorbronsdon/avoid-ai-writing
Audit and rewrite content to remove AI writing patterns ("AI-isms").
A skill your agent uses when revising a PVLDB paper's prose, covering the page-one contract for systems readers, scoping performance claims to measured regimes, stating design trade-offs instead of…
Install Vldb Writing Style
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill vldb-writing-style -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills vldb-writing-style --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-writing-style .claude/skills/vldb-writing-style && 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-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/VLDB-Skills/skills/vldb-writing-style into .claude/skills/vldb-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vldb-writing-style", 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-writing-styleType 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-writing-style -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills vldb-writing-style --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-writing-style .agents/skills/vldb-writing-style && 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-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/VLDB-Skills/skills/vldb-writing-style into .agents/skills/vldb-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vldb-writing-style", 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-writing-style -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills vldb-writing-style --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-writing-style .cursor/skills/vldb-writing-style && 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-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/VLDB-Skills/skills/vldb-writing-style into .cursor/skills/vldb-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vldb-writing-style", 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-writing-style--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-writing-style -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills vldb-writing-style --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-writing-style .gemini/skills/vldb-writing-style && 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-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/VLDB-Skills/skills/vldb-writing-style into .gemini/skills/vldb-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vldb-writing-style", 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-writing-styleInstalls 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-writing-style -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-writing-style .github/skills/vldb-writing-style && 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-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/VLDB-Skills/skills/vldb-writing-style into .github/skills/vldb-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vldb-writing-style", 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-writing-style -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-writing-style --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-writing-style .opencode/skills/vldb-writing-style && 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-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/VLDB-Skills/skills/vldb-writing-style into .opencode/skills/vldb-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vldb-writing-style", 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-writing-style- GitHub stars
- 1.2k
- Token cost
- ~920 tokens
- SKILL.md length
- 386 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when revising a PVLDB paper's prose, covering the page-one contract for systems readers, scoping performance claims to measured regimes, stating design trade-offs instead of…
- Works in 4 steps: The workload that breaks current systems… → The design decision — the bet your… → What was built — real system, extension… → …
- Revising a PVLDB papers prose
- SKILL.md covers The page-one contract, Claim scoping table, Trade-off candor and Budget and terminology…, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Vldb Writing Style is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when revising a PVLDB paper's prose, covering the page-one contract for systems readers, scoping performance claims to measured regimes, stating design trade-offs instead of hiding them, terminology and notation discipline across a 12-page budget, and the tone VLDB's builder-reviewers reward.
Its SKILL.md is about 920 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 Writing & Content, covering Brand voice and tone. 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
- Revising a PVLDB papers prose
- Covering the page-one contract for systems readers
- Scoping performance claims to measured regimes
- Stating design trade-offs instead of hiding them
Example prompts
- “/vldb-writing-style”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- The workload that breaks current systems — concrete, not "growing data
- The design decision — the bet your system makes that others do not.
- What was built — real system, extension of a named engine, or
- The headline measurement, scoped — metric, scale, baseline, hardware
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 Writing Style loads about 920 tokens when it runs. Until then it costs about 79 tokens; SKILL.md has 386 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). 386 words, ~920 tokens.
Download SKILL.mdSave it as
.claude/skills/vldb-writing-style/SKILL.md (or your agent's skills folder).- name
- vldb-writing-style
- description
- Use when revising a PVLDB paper's prose, covering the page-one contract for systems readers, scoping performance claims to measured regimes, stating design trade-offs instead of hiding them, terminology and notation discipline across a 12-page budget, and the tone VLDB's builder-reviewers reward.
VLDB Writing Style
Use this during revision passes. The PVLDB reader is a systems builder deciding, inside the first page, whether your design decision is worth their evening. Style at this venue is not ornament — it is claim hygiene.
The page-one contract
By the end of page one the reader must know:
- The workload that breaks current systems — concrete, not "growing data volumes."
- The design decision — the bet your system makes that others do not.
- What was built — real system, extension of a named engine, or simulation; readers calibrate trust to this immediately.
- The headline measurement, scoped — metric, scale, baseline, hardware class, all in one sentence.
A running example introduced early and reused through design and evaluation sections is the genre's most effective device; pick one query, one tenant, one failure trace and let it carry the mechanism.
Claim scoping table
| Unscoped (review bait) | Scoped (survives) |
|---|---|
| "significantly faster than X" | "2.1x median speedup over X (v3.4, tuned per §6.1) on workload W at 1TB" |
| "scales to large clusters" | "near-linear to 64 nodes; efficiency drops to 71% at 128 (Fig. 9)" |
| "negligible overhead" | "adds 3-5% CPU on write-heavy YCSB-A; worst case 11% at 99% writes" |
| "state-of-the-art performance" | delete; name the systems and the regime |
Every superlative either gains a number, a workload, and a baseline — or dies.
Show full SKILL.md (166 more words)Show less
Trade-off candor
Systems reviewers assume every design pays somewhere. A paper that never says what its mechanism costs reads as unmeasured, not as flawless.
- State the price of the design in the introduction (memory, write path latency, generality) and point to the section that measures it.
- Put the loss cases in the main evaluation, not a footnote: the workload where the baseline wins is your credibility purchase.
- Prefer "we chose A over B because C, accepting cost D" over passive descriptions that hide the decision.
Budget and terminology discipline
- One name per concept for all 12 pages: a "segment" on page 3 cannot become a "chunk" on page 9. Builder-readers parse terminology as architecture.
- Architecture figure by page 3; reviewers reconstruct systems visually.
- Since references are uncapped but appendices are not, spend prose on mechanism and measurement, and let citations carry the history compactly.
- Single-blind means writing "we extend our earlier system [12]" is fine — clarity about lineage beats coy third-person contortions.
Self-edit sweep
grep-worthy passes before submission:
"significant" -> replace with the number or delete
"novel" -> the contribution list should prove it instead
"to the best of our knowledge" -> keep at most one, verified
"very large" -> state the size
passive "was designed" -> name the decision and its reason
every Figure N -> referenced in text, at least one sentence of readingOutput format
[Page-one contract] met / missing elements listed
[Unscoped claims] <count, worst three quoted>
[Trade-off candor] price stated in intro? loss cases in eval?
[Terminology drift] <concept -> competing names found>
[Running example] present / absent (suggested candidate)
[Edit order] <highest-leverage rewrites first>© 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-writing-style of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Vldb Writing Style 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 Writing Style this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~920 | Automated safety check: Pass | MIT | |
| Avoid AI Writingconorbronsdon/avoid-ai-writing | 4.9k | 3 repos | ~8.1k | Automated safety check: Pass | MIT | |
| BrandOhh-889/skyroc | 795 | 13 repos | ~733 | Automated safety check: Pass | MIT | |
| Khazix WeChat Article WriterKKKKhazix/khazix-skills | 21k | 1 repos | ~2.9k | Automated safety check: Pass | MIT | |
| Writing Guidelinesvercel-labs/agent-skills | 32k | 7 repos | ~309 | Automated safety check: Pass | None | |
| Unslop AI Writing Cleanuptheclaymethod/unslop | 518 | — | ~1.7k | Automated safety check: Pass | MIT |
Similar skills
Brand
Ohh-889/skyroc
Brand voice, visual identity, messaging frameworks, asset management, brand consistency.
Khazix WeChat Article Writer
KKKKhazix/khazix-skills
Writes long-form WeChat official account articles in the personal style of the Khazix account, from briefs, links, PDFs or rough notes, with a topic quality check.
- Official
Writing Guidelines
vercel-labs/agent-skills
Review docs/prose for Writing Guidelines compliance. An agent skill from vercel-labs/agent-skills.
Unslop AI Writing Cleanup
theclaymethod/unslop
Removes AI writing tells from prose through an audit-first flow, routing to a two-pass rewrite, a report-only cleanup, voice teaching or mimicry depending on the sub-command used.
UX Writing
content-designer/ux-writing-skill
Applies UX writing practice to interface copy such as buttons, errors, forms and onboarding, using four quality standards and accessibility guidance.
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 Writing Style
What does Vldb Writing Style do?
A skill your agent uses when revising a PVLDB paper's prose, covering the page-one contract for systems readers, scoping performance claims to measured regimes, stating design trade-offs instead of…. Vldb Writing Style is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when revising a PVLDB paper's prose, covering the page-one contract for systems readers, scoping performance claims to measured regimes, stating design trade-offs instead of hiding them, terminology and notation discipline across a 12-page budget, and the tone VLDB's builder-reviewers reward.
When should I use Vldb Writing Style?
Vldb Writing Style fits situations like: revising a PVLDB papers prose; covering the page-one contract for systems readers; scoping performance claims to measured regimes; stating design trade-offs instead of hiding them.
How do I install Vldb Writing Style in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill vldb-writing-style -a claude-code`. Or copy the skill folder (VLDB-Skills/skills/vldb-writing-style in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/vldb-writing-style in your project. Claude Code loads it when a task matches its description.
How do I install Vldb Writing Style in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill vldb-writing-style -a codex`. Or copy the skill folder (VLDB-Skills/skills/vldb-writing-style in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/vldb-writing-style in your project. Codex loads it when a task matches its description.
Can I use Vldb Writing Style 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-writing-style -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-writing-style, .gemini/skills/vldb-writing-style, .github/skills/vldb-writing-style and .opencode/skills/vldb-writing-style in your project.
What does Vldb Writing Style need to run?
SKILL.md names no scripts, command-line tools or credentials: Vldb Writing Style is instructions for the agent only.
Does Vldb Writing Style 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 Writing Style 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 Writing Style use?
Vldb Writing Style 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 Writing Style use?
About 920 tokens (SKILL.md is roughly 3.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Vldb Writing Style?
Skills that share tags, products or a category with Vldb Writing Style: Avoid AI Writing (conorbronsdon/avoid-ai-writing, 4.9k stars), Brand (Ohh-889/skyroc, 795 stars), Khazix WeChat Article Writer (KKKKhazix/khazix-skills, 21k stars) and Writing Guidelines (vercel-labs/agent-skills, 32k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Vldb Writing Style?
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.