Agent skill

every-style-editor

This skill should be used when reviewing or editing copy to ensure adherence to Every's style guide. It provides a systematic line-by-line review process for grammar, punctuation, mechanics, and style guide compliance.

Stars 20
Forks 6

Install this agent skill to your Project

npx add-skill https://github.com/petekp/claude-code-setup/tree/main/skills/every-style-editor

SKILL.md

Every Style Editor

This skill provides a systematic approach to reviewing copy against Every's comprehensive style guide. It transforms Claude into a meticulous line editor and proofreader specializing in grammar, mechanics, and style guide compliance.

When to Use This Skill

Use this skill when:

  • Reviewing articles, blog posts, newsletters, or any written content
  • Ensuring copy follows Every's specific style conventions
  • Providing feedback on grammar, punctuation, and mechanics
  • Flagging deviations from the Every style guide
  • Preparing clean copy for human editorial review

Skill Overview

This skill enables performing a comprehensive review of written content in four phases:

  1. Initial Assessment - Understanding context and document type
  2. Detailed Line Edit - Checking every sentence for compliance
  3. Mechanical Review - Verifying formatting and consistency
  4. Recommendations - Providing actionable improvement suggestions

How to Use This Skill

Step 1: Initial Assessment

Begin by reading the entire piece to understand:

  • Document type (article, knowledge base entry, social post, etc.)
  • Target audience
  • Overall tone and voice
  • Content context

Step 2: Detailed Line Edit

Review each paragraph systematically, checking for:

  • Sentence structure and grammar correctness
  • Punctuation usage (commas, semicolons, em dashes, etc.)
  • Capitalization rules (especially job titles, headlines)
  • Word choice and usage (overused words, passive voice)
  • Adherence to Every style guide rules

Reference the complete style guide at references/EVERY_WRITE_STYLE.md for specific rules when in doubt.

Step 3: Mechanical Review

Verify:

  • Spacing and formatting consistency
  • Style choices applied uniformly throughout
  • Special elements (lists, quotes, citations)
  • Proper use of italics and formatting
  • Number formatting (numerals vs. spelled out)
  • Link formatting and descriptions

Step 4: Output Results

Present findings using this structure:

DOCUMENT REVIEW SUMMARY
=====================
Document Type: [type]
Word Count: [approximate]
Overall Assessment: [brief overview]

ERRORS FOUND: [total number]

DETAILED CORRECTIONS
===================

[For each error found:]

**Location**: [Paragraph #, Sentence #]
**Issue Type**: [Grammar/Punctuation/Mechanics/Style Guide]
**Original**: "[exact text with error]"
**Correction**: "[corrected text]"
**Rule Reference**: [Specific style guide rule violated]
**Explanation**: [Brief explanation of why this is an error]

---

RECURRING ISSUES
===============
[List patterns of errors that appear multiple times]

STYLE GUIDE COMPLIANCE CHECKLIST
==============================
✓ [Rule followed correctly]
✗ [Rule violated - with count of violations]

FINAL RECOMMENDATIONS
===================
[2-3 actionable suggestions for improving the draft]

Style Guide Reference

The complete Every style guide is at references/EVERY_WRITE_STYLE.md. Key areas to focus on:

  • Quick Rules: Title case for headlines, sentence case elsewhere
  • Tone: Active voice, avoid overused words (actually, very, just), be specific
  • Numbers: Spell out one through nine; use numerals for 10+
  • Punctuation: Oxford commas, em dashes without spaces, proper quotation mark usage
  • Capitalization: Lowercase job titles, company as singular (it), teams as plural (they)
  • Emphasis: Italics only (no bold for emphasis)
  • Links: 2-4 words, don't say "click here"

Key Principles

  • Be specific: Always quote the exact text with the error
  • Reference rules: Cite the specific style guide rule for each correction
  • Maintain voice: Preserve the author's voice while correcting errors
  • Prioritize clarity: Focus on changes that improve readability
  • Be constructive: Frame feedback to help writers improve
  • Flag ambiguous cases: When style guide doesn't address an issue, explain options and recommend the clearest choice

Common Areas to Focus On

Based on Every's style guide, pay special attention to:

  • Punctuation (comma usage, semicolons, apostrophes, quotation marks)
  • Capitalization (proper nouns, titles, sentence starts)
  • Numbers (when to spell out vs. use numerals)
  • Passive voice (replace with active whenever possible)
  • Overused words (actually, very, just)
  • Lists (parallel structure, punctuation, capitalization)
  • Hyphenation (compound adjectives, except adverbs)
  • Word usage (fewer vs. less, they vs. them)
  • Company references (singular "it", teams as plural "they")
  • Job title capitalization

Expand your agent's capabilities with these related and highly-rated skills.

petekp/claude-code-setup

ubiquitous-language

Extract a DDD-style ubiquitous language glossary from the current conversation, flagging ambiguities and proposing canonical terms. Saves to UBIQUITOUS_LANGUAGE.md. Use when user wants to define domain terms, build a glossary, harden terminology, create a ubiquitous language, or mentions "domain model" or "DDD".

20 6
Explore
petekp/claude-code-setup

manage-codex

Autonomous Codex batch orchestrator. Use for "/manage-codex", "manage codex", "use codex", "dispatch to codex", or long-running Codex work.

20 6
Explore
petekp/claude-code-setup

seo-audit

When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," "SEO health check," "my traffic dropped," "lost rankings," "not showing up in Google," "site isn't ranking," "Google update hit me," "page speed," "core web vitals," "crawl errors," or "indexing issues." Use this even if the user just says something vague like "my SEO is bad" or "help with SEO" — start with an audit. For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema-markup. For AI search optimization, see ai-seo.

20 6
Explore
petekp/claude-code-setup

capture-learning

Analyze recent conversation context and capture learnings to project knowledge files (for project-specific insights) or skills/commands/subagents (for cross-project patterns). Use when the user asks to "capture this learning", "update the docs with this", "remember this for next time", "document this issue", "add this to CLAUDE.md", "save this knowledge", or "update project knowledge". Also triggers after resolving build/setup issues, discovering non-obvious patterns, or completing debugging sessions with valuable insights.

20 6
Explore
petekp/claude-code-setup

agent-changelog

Compile an agent-optimized changelog by cross-referencing git history with plans and documentation. Use when asked to "update changelog", "compile history", "document project evolution", or proactively after major milestones, architectural changes, or when stale/deprecated information is detected that could confuse coding agents.

20 6
Explore
petekp/claude-code-setup

swift-apps

Build, refactor, review, and debug native Apple-platform software in Swift. Use when working on `.swift` files, SwiftUI views, Observation-based state, `@Bindable` and binding flow, SwiftData-backed UI, scenes and windows, search/navigation structures, UIKit/AppKit interop, Liquid Glass adoption, macOS-native UX, or SwiftUI performance/accessibility. Trigger on requests to create or polish iOS, iPadOS, macOS, or visionOS features; clean up SwiftUI view structure; diagnose jank or invalidation storms; review app quality; or make a feature feel like a good Apple-platform citizen.

20 6
Explore

Didn't find tool you were looking for?

Be as detailed as possible for better results