every-style-check
Check text against Every's editorial style guide and return a checklist of style violations. Use when someone asks to check, review, or validate text against Every's style guide, or when editing content for Every. Returns only violations—does not auto-fix.
Security Vetted
Reviewed by AI agents and approved by humans.
Skill Instructions
# Every Style Check ## Overview Check text against Every's comprehensive editorial style guide and return a structured checklist of violations. This skill identifies style issues but does not automatically fix them—allowing you to make corrections in your own document editor. ## How to Use When someone provides text and asks to check it against Every's style guide: 1. Load the complete style guide from `references/every-style-guide.md` 2. Review the text carefully against all rules in the style guide 3. Return ONLY violations in the specified checklist format ## Output Format Return violations in this exact format: ``` ## Style Violations Found - [ ] **[RULE CATEGORY]:** [Specific issue] → [How to fix] - Location: "[quoted text from draft]" - [ ] **[RULE CATEGORY]:** [Specific issue] → [How to fix] - Location: "[quoted text from draft]" ``` **If no violations found:** Respond with "No style violations found." **Do NOT include:** - Praise for what's done well - Summaries of the text - General feedback - Explanations beyond the violation → fix format ## Rule Categories Reference the complete style guide in `references/every-style-guide.md` for all rules. Key categories include: - Names and People - Linking and Sources - Organizations, Publications, and Acronyms (including company name spellings) - Capitalization - Clarity and Pronoun Reference - Punctuation - Numbers (including "per" spelled out) - Formatting - Images and Captions - Lists - Specific Words and Phrases (including "versus" spelled out) - Quotes - Every-Specific Rules - Dates and Times - Geography ## Example Usage **User:** "Check this draft against Every's style guide: [text]" **Response:** ``` ## Style Violations Found - [ ] **Names and People:** First mention of person's name not bolded → Bold the full name - Location: "Dan Shipper is the CEO" - [ ] **Linking and Sources:** Study mentioned without link → Add hyperlink to source - Location: "A study found that..." - [ ] **Capitalization:** Subheading uses title case → Change to sentence case - Location: "Prompting Belongs In The Business School" - [ ] **Numbers:** Slash used instead of "per" → Spell out "per" - Location: "$20/month" - [ ] **Specific Words and Phrases:** "vs." used instead of "versus" → Spell out "versus" - Location: "AI vs. human" - [ ] **Organizations:** Company name misspelled → Use correct capitalization - Location: "Github" should be "GitHub" ``` ## Important Notes - Always read the complete style guide from `references/every-style-guide.md` before checking text - Be thorough—check against all rules, not just common violations - Quote the exact text from the draft that violates the rule - Provide clear, actionable fix instructions - Maintain consistent formatting in the checklist output - Pay special attention to company name spellings (GitHub, YouTube, LinkedIn, etc.) - Check for slashes that should be "per" ($20/month → $20 per month) - Check for "vs." that should be "versus"