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 1
Forks 1

Install this agent skill to your Project

npx add-skill https://github.com/nbbaier/compound-engineering-amp/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 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 included in 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.

nbbaier/compound-engineering-amp

compound-docs

Capture solved problems as categorized documentation with YAML frontmatter for fast lookup

1 1
Explore
nbbaier/compound-engineering-amp

file-todos

This skill should be used when managing the file-based todo tracking system in the todos/ directory. It provides workflows for creating todos, managing status and dependencies, conducting triage, and integrating with slash commands and code review processes.

1 1
Explore
nbbaier/compound-engineering-amp

dspy-ruby

This skill should be used when working with DSPy.rb, a Ruby framework for building type-safe, composable LLM applications. Use this when implementing predictable AI features, creating LLM signatures and modules, configuring language model providers (OpenAI, Anthropic, Gemini, Ollama), building agent systems with tools, optimizing prompts, or testing LLM-powered functionality in Ruby applications.

1 1
Explore
nbbaier/compound-engineering-amp

git-worktree

This skill manages Git worktrees for isolated parallel development. It handles creating, listing, switching, and cleaning up worktrees with a simple interactive interface, following KISS principles.

1 1
Explore
nbbaier/compound-engineering-amp

andrew-kane-gem-writer

This skill should be used when writing Ruby gems following Andrew Kane's proven patterns and philosophy. It applies when creating new Ruby gems, refactoring existing gems, designing gem APIs, or when clean, minimal, production-ready Ruby library code is needed. Triggers on requests like "create a gem", "write a Ruby library", "design a gem API", or mentions of Andrew Kane's style.

1 1
Explore
nbbaier/compound-engineering-amp

dhh-rails-style

This skill should be used when writing Ruby and Rails code in DHH's distinctive 37signals style. It applies when writing Ruby code, Rails applications, creating models, controllers, or any Ruby file. Triggers on Ruby/Rails code generation, refactoring requests, code review, or when the user mentions DHH, 37signals, Basecamp, HEY, or Campfire style. Embodies REST purity, fat models, thin controllers, Current attributes, Hotwire patterns, and the "clarity over cleverness" philosophy.

1 1
Explore

Didn't find tool you were looking for?

Be as detailed as possible for better results