Skillzwave Logo
Skillzwave

every-style-editor

3146 stars 266 forks
83
B

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.

Marketplace

Third-Party Agent Skill: Review the code before installing. Agent skills execute in your AI assistant's environment and can access your files. Learn more about security

Installation for Agentic Skill

View all platforms →
skilz install EveryInc/compound-engineering-plugin/every-style-editor
skilz install EveryInc/compound-engineering-plugin/every-style-editor --agent opencode
skilz install EveryInc/compound-engineering-plugin/every-style-editor --agent codex
skilz install EveryInc/compound-engineering-plugin/every-style-editor --agent gemini

First time? Install Skilz: pip install skilz

Works with 22+ AI coding assistants

Cursor, Aider, Copilot, Windsurf, Qwen, Kimi, and more...

View All Agents
Download Agent Skill ZIP

Extract and copy to ~/.claude/skills/ then restart Claude Desktop

1. Clone the repository:
git clone https://github.com/EveryInc/compound-engineering-plugin
2. Copy the agent skill directory:
cp -r compound-engineering-plugin/plugins/compound-engineering/skills/every-style-editor ~/.claude/skills/
View on GitHub

Need detailed installation help? Check our platform-specific guides:

Claude Desktop Guide Claude Code Guide Troubleshooting

Related Agentic Skills

mastering-github-cli

by SpillwaveSolutions

GitHub CLI (gh) command reference for repository search, code discovery, CI/CD monitoring, workflow authoring, and automation. Triggers on "gh" com...

100
TECHgithub
Marketplace

mastering-github-cli

by SpillwaveSolutions

GitHub CLI (gh) command reference for repository search, code discovery, CI/CD monitoring, workflow authoring, and automation. Triggers on "gh" com...

100
TECHgithub
Marketplace

signal-intel

by gtmagents

Use when consolidating intent, product usage, and third-party signals to prioritize ABM actions.

91
github
Marketplace

meal-prep-efficiency-guru

by sandraschi

Expert in batch cooking, meal planning, food storage, and efficient kitchen workflows

88
github
Marketplace

Agentic Skill Details

Owner
EveryInc (GitHub)
Repository
compound-engineering-plugin
Stars
3146
Forks
266
Type
Non-Technical
Meta-Domain
development
Primary Domain
github
Market Score
83
Agentic Skill Grades →

Agent Skill Grade

B
Score: 83/100 Click to see breakdown

Score Breakdown

Spec Compliance
11/15
PDA Architecture
26/30
Ease of Use
21/25
Writing Style
7/10
Utility
17/20
Modifiers: +1

Areas to Improve

  • Description needs trigger phrases
  • Missing TOC in large reference
  • Mixed voice in SKILL.md

Recommendations

  • Add trigger phrases to description for discoverability
  • Add table of contents for files over 100 lines

Graded: 2026-01-05

Developer Feedback

I took a look at your every-style-editor skill and wanted to share some thoughts.

Links:

The TL;DR

You're at 83/100, which puts you solidly in B territory - good fundamentals with some polish work to do. Your Progressive Disclosure Architecture is your strongest area (26/30), meaning you've nailed the token-efficient layering between your main SKILL.md and the comprehensive EVERY_WRITE_STYLE.md reference. The gaps are mostly around metadata and consistency rather than core design.

What's Working Well

  • Excellent layering strategy - Your 135-line SKILL.md efficiently summarizes workflow while delegating the full 530-line style guide to a reference file. That's exactly how PDA should work.
  • Solid structured output - The template with line-by-line checklist gives users clear direction on what to deliver. The examples in your reference file make it actionable.
  • Practical problem-solving - You're addressing a real need (consistent editorial review), and your style guide rules are thorough enough to actually guide someone through edits.

The Big One: Description Needs Trigger Phrases

This is the main opportunity holding you back. Your frontmatter description says "This skill should be used when reviewing or editing copy..." but it's missing the explicit trigger phrases that help discoverability.

Why it matters: When someone asks Claude "review this for style", the system needs to know this skill exists. Right now, it's relying on fuzzy matching instead of direct keywords.

The fix: Update your SKILL.md frontmatter description to include triggers like:

"Use when asked to review style, perform l...

Browse Category

More development Agentic Skills

Report Security Issue

Found a security vulnerability in this agent skill?