skills/every-style-editor/SKILL.md
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.
npx skillsauth add ratacat/claude-skills every-style-editorInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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.
Use this skill when:
This skill enables performing a comprehensive review of written content in four phases:
Begin by reading the entire piece to understand:
Review each paragraph systematically, checking for:
Reference the complete EVERY_WRITE_STYLE.md for specific rules when in doubt.
Verify:
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]
The complete Every style guide is included in EVERY_WRITE_STYLE.md. Key areas to focus on:
Based on Every's style guide, pay special attention to:
tools
Build and test iOS apps on simulator using XcodeBuildMCP
development
Produces concise, clear documentation by applying Elements of Style principles. Use when writing or improving any technical documentation (READMEs, guides, API docs, architecture docs). Not for code comments.
testing
Use when user asks to create, write, edit, or test a skill. Also use when documenting reusable techniques, patterns, or workflows for future Claude instances.
testing
Execute work plans efficiently while maintaining quality and finishing features