One-click install
npx skills add https://github.com/sylvanding/omelette --skill every-style-editor-sylvanding
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: every-style-editor
Source: https://github.com/sylvanding/omelette/tree/main/.claude/skills/every-style-editor
Command: npx skills add https://github.com/sylvanding/omelette --skill every-style-editor-sylvanding

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Content created for Every often suffers from inconsistent application of the organization's detailed style guide, leading to formatting errors, tone mismatches, and excessive editorial revision time. This Skill eliminates that friction by providing a structured, repeatable review process that catches compliance issues before content is published.

Core Features & Use Cases

  • Systematic Four-Phase Review: Performs initial assessment, detailed line edit, mechanical review, and actionable recommendation generation for all content types.
  • Integrated Style Guide Reference: Accesses the full Every style guide to resolve ambiguous rule questions and ensure accurate, consistent corrections.
  • Use Case: An editor working on a new Every blog post can use this Skill to catch inconsistent number formatting, incorrect job title capitalization, and tone deviations in seconds, rather than manually cross-referencing every style rule.

Quick Start

Use the every-style-editor skill to review the attached draft newsletter for compliance with Every's style guide and provide a detailed list of corrections and recommendations.

Frequently Asked Questions about every-style-editor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce a style guide for consistent copy editing?

To enforce a style guide for consistent copy, use a systematic editorial review process that performs line editing, mechanical checks, and grammar correction to ensure compliance with specific formatting and tone rules.

What is the best way to proofread newsletters for style rule compliance?

Proofreading newsletters for style rule compliance involves an initial assessment followed by a detailed line edit and mechanical review, generating actionable correction recommendations to resolve formatting errors and tone mismatches.

Can I automate editorial review for blog posts and internal knowledge base entries?

Yes, automating editorial review for blog posts and internal knowledge base entries is possible by accessing an integrated style guide reference to resolve ambiguous rule questions and catch compliance issues before publication.

Does content compliance checking work for number formatting and job title capitalization?

Content compliance checking works effectively for number formatting and job title capitalization by systematically cross-referencing the text against detailed organizational style guidelines during the mechanical review phase.

What are the limitations of automated line editing for organizational content?

Automated line editing for organizational content is limited to resolving grammar, punctuation, mechanics, and style rule compliance based on the provided style guide, requiring human judgment for broader tone deviations.