Every Style Editor
Line-edit articles, newsletters, and docs so copy matches Every’s style guide before human editors or publish.
Overview
Every Style Editor is an agent skill most often used in Grow (also Build/docs) that reviews and edits copy line-by-line for Every style-guide compliance.
Install
npx skills add https://github.com/everyinc/compound-engineering-plugin --skill every-style-editorWhat is this skill?
- Four-phase review: initial assessment, line edit, mechanical check, actionable recommendations
- Systematic grammar, punctuation, and Every style-guide compliance on every sentence
- Flags deviations and prepares clean copy for human editorial handoff
- Works across articles, blog posts, newsletters, social posts, and KB entries
- Transforms the agent into a dedicated line editor and proofreader
- Four-phase review workflow: assessment, line edit, mechanical review, recommendations
Adoption & trust: 513 installs on skills.sh; 20.5k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You have draft copy that must match a strict house style, but manual proofreading is slow and easy to miss punctuation and convention errors.
Who is it for?
Solo founders shipping newsletters, blogs, or product docs who already follow Every’s style conventions and want repeatable editorial QA.
Skip if: Teams that do not use Every’s style guide, purely technical API reference with no prose voice, or one-off casual chat with no publication bar.
When should I use this skill?
Reviewing or editing copy to ensure adherence to Every's style guide; articles, blog posts, newsletters, or preparing clean copy for human editorial review.
What do I get? / Deliverables
You get a structured editorial pass with flagged deviations and recommendations so clean copy is ready for human review or publish.
- Line-by-line style and grammar findings
- Mechanical consistency notes
- Actionable editorial recommendations
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Polishing written assets sits in Grow/content, where lifecycle messaging and editorial quality compound distribution. Content subphase covers newsletters, blogs, and knowledge-base copy—the document types named in the skill.
Where it fits
Run a full four-phase pass on a weekly newsletter before scheduling in your ESP.
Align a knowledge-base article with Every mechanics and punctuation rules before merge.
Tighten launch announcement copy for style consistency across blog and social variants.
How it compares
Use instead of asking the model to “proofread” without a named checklist—this skill encodes Every’s guide as a systematic review ritual.
Common Questions / FAQ
Who is every-style-editor for?
Writers, indie founders, and small marketing or docs teams who publish under Every’s style guide and want agent-assisted line editing before humans sign off.
When should I use every-style-editor?
In Grow/content when polishing newsletters and blogs; in Build/docs when tightening knowledge-base or product copy; anytime you are reviewing articles or social posts for grammar and style compliance.
Is every-style-editor safe to install?
It is editorial review logic over text you provide—review the Security Audits panel on this Prism page and avoid pasting secrets into documents you send for review.
SKILL.md
READMESKILL.md - Every Style Editor
# 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 - **Prioriti