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.
Install / Use
npx skills add Microck/ordinary-claude-skills --skill every-style-editorInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Content & MediaSupported Platforms
Our assessment of every-style-editor
every-style-editor scores 83/100 on our quality scale, 901st of 1,187 Content & Media skills we index.
Its SKILL.md is 4.7 KB long, well organised into 11 sections with 1 code example: a solid amount of guidance for an agent.
It has 399 GitHub stars, a meaningful sign that others use it.
Maintenance, license and trust
- The repository was last updated 30 days ago, so every-style-editor is actively maintained.
- No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
- Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
every-style-editor compared with similar skills
All 4 of these similar skills score higher than every-style-editor; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| every-style-editor (this skill)by Microck | 83 | 399 | 30d ago | SKILL.md |
| siyuanby siyuan-note | 100 | 46.6k | today | MCP Server |
| algorithmic-artby anthropics | 100 | 177.9k | 14d ago | SKILL.md |
| pptxby anthropics | 100 | 177.9k | 14d ago | SKILL.md |
| designby nextlevelbuilder | 100 | 130.2k | 15d ago | SKILL.md |
Frequently asked questions
- How do I install every-style-editor?
- Run
npx skills add Microck/ordinary-claude-skills --skill every-style-editor. The install tabs above show the steps for each supported agent. - Which AI agents does every-style-editor work with?
- It is written for Claude Code, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is every-style-editor safe to use?
- It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is every-style-editor still maintained?
- The repository was last updated 30 days ago, so every-style-editor is actively maintained.
Skill content
View source on GitHubname: every-style-editor description: 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.
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:
- Initial Assessment - Understanding context and document type
- Detailed Line Edit - Checking every sentence for compliance
- Mechanical Review - Verifying formatting and consistency
- 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 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
- 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
Related Skills
siyuan
46.6kAn open-source, privacy-first, self-hosted knowledge workspace where humans and AI agents work together 开源、隐私优先、自托管的知识工作空间,让人与智能体在此协作
algorithmic-art
177.9kCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems.
pptx
177.9kUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an em…
design
130.2kComprehensive design skill: brand identity, design tokens, UI styling, logo generation (55 styles, Gemini, Atlas Cloud, or MuAPI AI), corporate identity program (50 deliverables, CIP mockups), HTML presentations (Chart.js), banner design (22 styles, social/ads/web/print), icon design (15 styles, SVG…
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
