Avoid AI Writing
conorbronsdon/avoid-ai-writing
Audit and rewrite content to remove AI writing patterns ("AI-isms").
Review docs/prose for Writing Guidelines compliance. An agent skill from vercel-labs/agent-skills.
Install Writing Guidelines
$ npx skills add vercel-labs/agent-skills --skill writing-guidelines -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install vercel-labs/agent-skills writing-guidelines --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/vercel-labs/agent-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/writing-guidelines .claude/skills/writing-guidelines && 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 "writing-guidelines" agent skill from https://github.com/vercel-labs/agent-skills/tree/main/skills/writing-guidelines into .claude/skills/writing-guidelines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-guidelines", 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/vercel-labs/agent-skills/tree/main/skills/writing-guidelinesType 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 vercel-labs/agent-skills --skill writing-guidelines -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install vercel-labs/agent-skills writing-guidelines --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vercel-labs/agent-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/writing-guidelines .agents/skills/writing-guidelines && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "writing-guidelines" agent skill from https://github.com/vercel-labs/agent-skills/tree/main/skills/writing-guidelines into .agents/skills/writing-guidelines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-guidelines", 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 vercel-labs/agent-skills --skill writing-guidelines -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install vercel-labs/agent-skills writing-guidelines --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vercel-labs/agent-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/writing-guidelines .cursor/skills/writing-guidelines && 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 "writing-guidelines" agent skill from https://github.com/vercel-labs/agent-skills/tree/main/skills/writing-guidelines into .cursor/skills/writing-guidelines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-guidelines", 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/vercel-labs/agent-skills.git --path skills/writing-guidelines--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 vercel-labs/agent-skills --skill writing-guidelines -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install vercel-labs/agent-skills writing-guidelines --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vercel-labs/agent-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/writing-guidelines .gemini/skills/writing-guidelines && 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 "writing-guidelines" agent skill from https://github.com/vercel-labs/agent-skills/tree/main/skills/writing-guidelines into .gemini/skills/writing-guidelines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-guidelines", 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 vercel-labs/agent-skills writing-guidelinesInstalls 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 vercel-labs/agent-skills --skill writing-guidelines -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/vercel-labs/agent-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/writing-guidelines .github/skills/writing-guidelines && 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 "writing-guidelines" agent skill from https://github.com/vercel-labs/agent-skills/tree/main/skills/writing-guidelines into .github/skills/writing-guidelines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-guidelines", 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 vercel-labs/agent-skills --skill writing-guidelines -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install vercel-labs/agent-skills writing-guidelines --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vercel-labs/agent-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/writing-guidelines .opencode/skills/writing-guidelines && 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 "writing-guidelines" agent skill from https://github.com/vercel-labs/agent-skills/tree/main/skills/writing-guidelines into .opencode/skills/writing-guidelines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-guidelines", 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
writing-guidelines- GitHub stars
- 32k
- Used in
- 7 other repos
- Token cost
- ~309 tokens
- SKILL.md length
- 127 words
- Files
- 1
- Skills in repo
- 4
- Repo updated
- First seen
- Licence
- None found
At a glance
Review docs/prose for Writing Guidelines compliance. An agent skill from vercel-labs/agent-skills.
- Works in 4 steps: Fetch the latest guidelines from the… → Read the specified files (or prompt user… → Check against all rules in the fetched… → …
- Asked to review my docs
- SKILL.md covers How It Works, Guidelines Source and Usage
- Reaches raw.githubusercontent.com
What it does
Writing Guidelines is an agent skill from vercel-labs/agent-skills, published by the product's own GitHub organization. Review docs/prose for Writing Guidelines compliance. Use when asked to "review my docs", "check writing style", "audit prose", "review docs voice and tone", or "check this page against the writing handbook".
Its SKILL.md is about 310 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: Vercel's official collection of agent skills.
When your agent uses it
- Asked to review my docs
- Check writing style
- Review docs voice and tone
- Check this page against the writing handbook
Example prompts
- “review my docs”
- “check writing style”
- “audit prose”
- “/writing-guidelines”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Fetch the latest guidelines from the source URL below
- Read the specified files (or prompt user for files/pattern)
- Check against all rules in the fetched guidelines
- Output findings in the terse file:line format
What it can do on your machine
Read from SKILL.md and the folder at commit 063bee9. 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
Hosts in commands or code, which the agent is likely to contact:
raw.githubusercontent.com
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
Writing Guidelines loads about 309 tokens when it runs. Until then it costs about 57 tokens; SKILL.md has 127 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
Without a licence we can't republish the file, so here is its outline and opening line. It has 127 words (~309 tokens).
“Review files for compliance with Writing Guidelines.”
- name
- writing-guidelines
- metadata.author
- vercel
- metadata.version
- 1.0.0
- metadata.argument-hint
- <file-or-pattern>
Files
Just SKILL.md in skills/writing-guidelines of vercel-labs/agent-skills.
Open the folder on GitHubat commit 063bee9
Used in 7 other repositories
We found 8 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 7 other GitHub owners. This page covers the copy in vercel-labs/agent-skills, which our catalogue first saw on October 7, 2026.
- BodhiSearch/BodhiApp.agents/skills/writing-guidelines.claude/skills/writing-guidelines
- VladSez/easy-invoice-pdf.agents/skills/writing-guidelines
- robotostudio/turbo-start-sanity.agents/skills/writing-guidelines
- millionco/react-doctor.agents/skills/writing-guidelines
- fujioky/reach.agents/skills/writing-guidelines
- aiskillstore/marketplaceskills/vercel-labs/writing-guidelines
- nexu-io/open-designskills/writing-guidelines
Compare with similar skills
Writing Guidelines 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 |
|---|---|---|---|---|---|---|
| Writing Guidelines this skillvercel-labs/agent-skills | 32k | 7 repos | ~309 | Automated safety check: Pass | None | |
| 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 | |
| Unslop AI Writing Cleanuptheclaymethod/unslop | 516 | — | ~1.7k | Automated safety check: Pass | MIT | |
| UX Writingcontent-designer/ux-writing-skill | 224 | 1 repos | ~3.8k | 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.
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.
Brand Voice Guide
luongnv89/claude-howto
Ensure all communication matches brand voice and tone guidelines. Use when creating marketing copy, customer communications, public-facing content, or when…
More from vercel-labs/agent-skills
- Official
Vercel Optimize Audit
vercel-labs/agent-skills
Runs a metrics-first audit of a deployed Vercel project, gating investigations on real signals to produce ranked, citation-backed cost and performance recommendations.
- Official
Deploy to Vercel
vercel-labs/agent-skills
Deploys applications to Vercel as previews by default, picking a deploy method from the project's link state, git remote and team.
- Official
Vercel CLI With Tokens
vercel-labs/agent-skills
Deploys and manages Vercel projects through the CLI using an access token from the environment or a .env file instead of interactive login.
Related
Categories
Questions about Writing Guidelines
What does Writing Guidelines do?
Review docs/prose for Writing Guidelines compliance. An agent skill from vercel-labs/agent-skills. Writing Guidelines is an agent skill from vercel-labs/agent-skills, published by the product's own GitHub organization. Review docs/prose for Writing Guidelines compliance.
When should I use Writing Guidelines?
Writing Guidelines fits situations like: asked to review my docs; check writing style; review docs voice and tone; check this page against the writing handbook.
How do I install Writing Guidelines in Claude Code?
Run `npx skills add vercel-labs/agent-skills --skill writing-guidelines -a claude-code`. Or copy the skill folder (skills/writing-guidelines in vercel-labs/agent-skills) into .claude/skills/writing-guidelines in your project. Claude Code loads it when a task matches its description.
How do I install Writing Guidelines in Codex?
Run `npx skills add vercel-labs/agent-skills --skill writing-guidelines -a codex`. Or copy the skill folder (skills/writing-guidelines in vercel-labs/agent-skills) into .agents/skills/writing-guidelines in your project. Codex loads it when a task matches its description.
Can I use Writing Guidelines 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 vercel-labs/agent-skills --skill writing-guidelines -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/writing-guidelines, .gemini/skills/writing-guidelines, .github/skills/writing-guidelines and .opencode/skills/writing-guidelines in your project.
What does Writing Guidelines need to run?
SKILL.md names no scripts, command-line tools or credentials: Writing Guidelines is instructions for the agent only.
Does Writing Guidelines access the network?
SKILL.md names 1 domain. In commands or code: raw.githubusercontent.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Is Writing Guidelines 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 Writing Guidelines use?
No licence was found for Writing Guidelines or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does Writing Guidelines use?
About 309 tokens (SKILL.md is roughly 1.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 Writing Guidelines?
Skills that share tags, products or a category with Writing Guidelines: 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 Unslop AI Writing Cleanup (theclaymethod/unslop, 516 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Writing Guidelines?
vercel-labs (a GitHub organization, an official publisher) maintains it in vercel-labs/agent-skills, which has 32,103 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on August 28, 2026.
Source: vercel-labs/agent-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.