skill-creator
This skill provides guidance for creating effective skills.
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.
$ npx -y skills add robertguss/claude-code-toolkit --skill every-style-editor --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/every-style-editorContext preview
The summary Claude sees to decide when to auto-load this skill.
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.
name: 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.
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:
1. **Initial Assessment** - Understanding context and document type 2. **Detailed Line Edit** - Checking every sentence for compliance 3. **Mechanical Review** - Verifying formatting and consistency 4. **Recommendations** - Providing actionable improvement suggestions
Begin by reading the entire piece to understand:
Review each paragraph systematically, checking for:
Reference the complete [EVERY_WRITE_STYLE.md](./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 included in [EVERY_WRITE_STYLE.md](./references/EVERY_WRITE_STYLE.md). Key areas to focus on:
Based on Every's style guide, pay special attention to:
Extend Claude Code with specialized workflows, automatic formatting, and better defaults. Skills give Claude domain expertise—brainstorming methods, documentation generation, book writing pipelines.
Repo: robertguss/claude-code-toolkit
This skill provides guidance for creating effective skills.
This skill should be used when writing in the distinctive style of David Heinemeier Hansson (DHH). It applies when creating blog posts, technical articles,…
This skill should be used when writing technical content in the style of Hunt/Thomas (The Pragmatic Programmer) and Joel Spolsky (Joel on Software). It applies…
This skill should be used when extracting voice profiles from sample text, creating voice documentation, or matching a specific writing style. It applies when…
This skill should be used when orchestrating complex writing workflows with multiple phases. It provides two-agent orchestration patterns, the two-gate content…
A collaborative brainstorming system designed for multi-session ideation projects that span days or weeks.