Elements of Style
Write clearly and concisely by applying William Strunk Jr.'s "The Elements of Style" (1918; Strunk & White from 1959) to any English prose — PR descriptions, commit messages, READMEs, ADRs, design docs, tickets, release notes, emails, chat replies, UI copy, error messages, code comments, marketing pages. Covers the rules of usage (commas, independent clauses, dangling participles), the principles of composition (one topic per paragraph, active voice, positive form, definite concrete language, omit needless words, parallel form, related words together, emphatic word last), the misused-words lis
Install
/plugin marketplace add vnovakovits/claude-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add vnovakovits/claude-skills --skill elements-of-stylegit clone --depth 1 https://github.com/vnovakovits/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/plugins/engineering-practices/skills/elements-of-style ~/.claude/skills/elements-of-stylePersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# The Elements of Style (William Strunk Jr.) Strunk wrote a forty-page rulebook for his Cornell students in 1918 because he was tired of correcting the same faults in every essay. E. B. White expanded it in 1959 and it has been the standard short guide to plain English since. Its whole argument fits in one passage from the original: **"Vigorous writing is concise. A sentence should contain no unnecessary words, a paragraph no unnecessary sentences, for the same reason that a drawing should have no unnecessary lines and a machine no unnecessary parts."** The central test for any piece of prose: **can a busy reader get the point on the first pass, and is there nothing left they could skip without losing meaning?** ## Core Philosophy - **The reader's attention is the scarce resource.** Every needless word spends it. Write for the person who reads it once, quickly, on a phone, three weeks from now. - **Conciseness is a by-product of clarity, not a target.** Cut what carries no meaning; never cut what does. "Make it shorter" means "remove what the reader does not need", not "compress until it is cryptic". - **Definite beats vague, concrete beats abstract, active beats passive, positive beats negative.** Most of the rules below are instances of these four preferences.
Details
- Skill name
elements-of-style- Repository
- vnovakovits/claude-skills
- Path
plugins/engineering-practices/skills/elements-of-style/SKILL.md- License
- MIT
- Repo updated
- 16 November 2026
FAQ
What does the Elements of Style skill do?
Write clearly and concisely by applying William Strunk Jr.'s "The Elements of Style" (1918; Strunk & White from 1959) to any English prose — PR descriptions, commit messages, READMEs, ADRs, design docs, tickets, release notes, emails, chat replies, UI copy, error messages, code comments, marketing pages. Covers the rules of usage (commas, independent clauses, dangling participles), the principles of composition (one topic per paragraph, active voice, positive form, definite concrete language, omit needless words, parallel form, related words together, emphatic word last), the misused-words lis
How do I install the Elements of Style skill?
Claude Code plugin: /plugin marketplace add vnovakovits/claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Elements of Style popular?
It lives in vnovakovits/claude-skills, which has 5 GitHub stars and 2 forks.
Related skills
Accidental Cio
5vnovakovits/claude-skills
Apply Scott Millett's "The Accidental CIO — A Lean and Agile Playbook for IT Leaders" (Wiley, 2024) when designing or reviewing how a technology organisation decides, funds, governs and delivers work. Covers the five components of an adaptive IT operating model (organised, work, govern, talent, lead) and its four themes (outcomes over output, intrinsic motivation, being not doing agile, manage flow not people); matching method and governance to context via Cynefin and Wardley evolution; governance as demand management + funding + measurement + decision rights, shifting from project funding to
Agent Retro
5vnovakovits/claude-skills
Run a retrospective on a coding-agent session and improve the agent's environment, not the code. Combines Derby & Larsen's five-stage retrospective, Shigeo Shingo's poka-yoke (turn a mechanical mistake into a check that makes it impossible), and Matt Pocock's retro categories — navigation, automated checks, coding standards, steering files, tool economy, information access. Covers mining the session transcript for corrections, wrong turns and slow searches; deciding where each fix belongs (analyzer, hook, CI, reviewer standards, CLAUDE.md pointer, skill, doc or memory); the no-op test for stee
API Design
5vnovakovits/claude-skills
Design APIs that are clear, evolvable, and idiomatic to their protocol — covering REST (Fielding, Richardson Maturity Model, Massé), GraphQL, gRPC/protobuf, versioning strategies, pagination, error responses (RFC 7807 Problem Details), idempotency, authentication, documentation (OpenAPI), and the pragmatic trade-offs between RESTful purity and developer ergonomics. Use when designing a new endpoint, choosing between REST/GraphQL/gRPC, defining versioning, structuring error responses, deciding pagination strategy, or evaluating an existing API's evolvability.
Example Mapping
5vnovakovits/claude-skills
Apply Matt Wynne's Example Mapping — the four-colour discovery technique (yellow story, blue rules, green concrete examples, red questions) that breaks a story or spec into rules, hangs concrete examples under each rule, and surfaces open questions. Covers the 25-minute session, card conventions, shape-of-the-map diagnostics (a rule with no examples is under-specified; an example fitting no rule means a missing rule; a red-heavy map is not ready), AUDIT MODE for checking whether a written spec's examples cover its rules, building the map on Miro or as a document, and converting greens into acc
Documentation Standards
8Freddy-CHEN-ux/00_claude_skills
This skill should be used when the user asks about "documentation templates", "doc structure", "README format", "API documentation format", "how to write tutorials", "documentation checklist", or when the documentation-writer agent needs templates and workflows for specific documentation types. Provides Diataxis-based templates, checklists, and examples for 7 documentation types.
Feature Spec Writer
8Freddy-CHEN-ux/00_claude_skills
PM framework for writing product specs from insights. Use when translating analysis into actionable feature requirements.
Browse the most popular Claude skills, all writing & content skills, or write your own with the skills generator.