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.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionevery-style-editorExecute the skills CLI command in your project's root directory to begin installation:
Fetches every-style-editor from everyinc/compound-engineering-plugin and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate every-style-editor. Access via /every-style-editor in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
13.4K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
13.4K
stars
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 style guide at references/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 at references/EVERY_WRITE_STYLE.md. Key areas to focus on:
Based on Every's style guide, pay special attention to:
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
every-style-editor reduced setup friction for our internal harness; good balance of opinion and flexibility.
every-style-editor reduced setup friction for our internal harness; good balance of opinion and flexibility.
I recommend every-style-editor for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
I recommend every-style-editor for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Useful defaults in every-style-editor — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Useful defaults in every-style-editor — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
every-style-editor has been reliable in day-to-day use. Documentation quality is above average for community skills.
every-style-editor has been reliable in day-to-day use. Documentation quality is above average for community skills.
every-style-editor is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
every-style-editor reduced setup friction for our internal harness; good balance of opinion and flexibility.
showing 1-10 of 32