/writing
Enforce direct, concise prose style and catch writing slop. Use when writing or editing PR descriptions, issue bodies, commit messages, documentation, Slack messages, or any human-facing text. Also use when asked to clean up, rewrite, or "de-AI" existing text.
$ npx -y skills add bendrucker/claude --skill writing --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/writing
Context preview
The summary Claude sees to decide when to auto-load this skill.
Enforce direct, concise prose style and catch writing slop. Use when writing or editing PR descriptions, issue bodies, commit messages, documentation, Slack messages, or any human-facing text. Also use when asked to clean up, rewrite, or "de-AI" existing text.
SKILL.md
writing.SKILL.mdname: writing:writing
description: >-
Enforce direct, concise prose style and catch writing slop. Use when writing or editing PR descriptions,
issue bodies, commit messages, documentation, Slack messages, or any human-facing text.
Also use when asked to clean up, rewrite, or "de-AI" existing text.
Writing
Patterns to Avoid
The hook enforces these automatically. Specific vocabulary and marketing-verb lists live in [`wordlists/`](../../wordlists/).
Structure
- Never use spaced em dashes (` — `).
- Avoid "not just X, but also Y" parallelism. Simplify.
- Don't join independent clauses with em dashes, semicolons, or hyphens. Write two sentences. Swapping one connector for another is not a fix. A rare semicolon is fine only when the clauses genuinely can't stand alone.
- Don't structure bullets as `- **path/to/file**: description`.
- Use `####` headers instead of `**Label:**` for labeled subsections.
- Headings name the topic in a couple of words. No verbs, no `Topic: clause`, no sentence-shaped headings. Move the explanation into the body.
Word Choice
- Don't replace "is"/"are" with "serves as" or "stands as".
- Don't write "reaching for X." Use "use X" or "prefer X over Y."
- Don't write "dig into" / "dive into." Name what you're looking at.
- Hedging verbs ("looks like", "appears to", "seems to") are vague. State directly or name the uncertainty.
PR and Review Prose
- Active voice. Not "X is added" but "Adds X."
- Not "Tests cover X" but "Added tests covering X."
- No trailing hedge adverbs ("regardless.", "nonetheless.").
- No cross-sentence negation ("It isn't X. It is Y."). Combine or drop the negation.
Outbound Email and Messages
- Don't write human-facing email in a punchy journalistic cadence: dramatic one-sentence paragraphs, rhetorical question then answer ("The result? X."), or escalating triads. Match the sender's plain voice.
Voice
Direct, conversational. Every sentence should teach something new. Cut words that restate the obvious.
- Substance over filenames or implementation details
- Shorter sentences over compound constructions
Read more
name: writing:writing description: >- Enforce direct, concise prose style and catch writing slop. Use when writing or editing PR descriptions, issue bodies, commit messages, documentation, Slack messages, or any human-facing text. Also use when asked to clean up, rewrite, or "de-AI" existing text.
Writing
Patterns to Avoid
The hook enforces these automatically. Specific vocabulary and marketing-verb lists live in [`wordlists/`](../../wordlists/).
Structure
- Never use spaced em dashes (` — `).
- Avoid "not just X, but also Y" parallelism. Simplify.
- Don't join independent clauses with em dashes, semicolons, or hyphens. Write two sentences. Swapping one connector for another is not a fix. A rare semicolon is fine only when the clauses genuinely can't stand alone.
- Don't structure bullets as `- **path/to/file**: description`.
- Use `####` headers instead of `**Label:**` for labeled subsections.
- Headings name the topic in a couple of words. No verbs, no `Topic: clause`, no sentence-shaped headings. Move the explanation into the body.
Word Choice
- Don't replace "is"/"are" with "serves as" or "stands as".
- Don't write "reaching for X." Use "use X" or "prefer X over Y."
- Don't write "dig into" / "dive into." Name what you're looking at.
- Hedging verbs ("looks like", "appears to", "seems to") are vague. State directly or name the uncertainty.
PR and Review Prose
- Active voice. Not "X is added" but "Adds X."
- Not "Tests cover X" but "Added tests covering X."
- No trailing hedge adverbs ("regardless.", "nonetheless.").
- No cross-sentence negation ("It isn't X. It is Y."). Combine or drop the negation.
Outbound Email and Messages
- Don't write human-facing email in a punchy journalistic cadence: dramatic one-sentence paragraphs, rhetorical question then answer ("The result? X."), or escalating triads. Match the sender's plain voice.
Voice
Direct, conversational. Every sentence should teach something new. Cut words that restate the obvious.
- Substance over filenames or implementation details
- Shorter sentences over compound constructions
My personal plugin marketplace for Claude Code, Anthropic's AI coding assistant.
Repo: bendrucker/claude
Other skills on bendrucker-claude.
- /agent-ideas
Harvest agent-tooling ideas from prominent developers.
Open skill - /cleye
Type-safe CLI argument parsing with cleye, the standard parser for this repo's Bun scripts. Use when writing or editing any script that takes arguments (flags, positional parameters, subcommands, --help) instead of reading existing scripts for the pattern.
Open skill - /coverage
Measure Bun test coverage and close gaps on a specific file. Use when adding or editing tests, when asked about coverage, or when the PostToolUse coverage hook reports uncovered lines.
Open skill - /activity
Report real device usage from ActivityWatch. Covers per-app time, window titles, and active vs idle spans. Use when asked "what apps did I use", "how long was I in X", "what did I work on today", "how much was I active vs idle", or to mine usage patterns for automation.
Open skill - /history
Report shell history from atuin's local capture. Covers what commands ran, when, where, and how they exited. Use when asked "what commands did I run", "what was I working on in the terminal", "have I ever run X", "how do I usually invoke X", or about recent shell activity,
Open skill - /bun
Bun runtime patterns. Use when running bun commands, working with package.json/bun.lock, writing TypeScript scripts under Bun, or developing Claude Code plugins.
Open skill

