
Editor
Proofread and structurally improve landing copy, docs, emails, and posts before you ship or publish as a solo builder.
Overview
Editor is an agent skill most often used in Grow (also Validate landing, Launch distribution, Build docs) that proofreads and revises text across four editing levels with a structured checklist.
Install
npx skills add https://github.com/shubhamsaboo/awesome-llm-apps --skill editorWhat is this skill?
- Four editing levels: proofreading, copy editing, line editing, developmental editing
- Structured checklist across clarity, grammar, style, and structure
- Handles edit, proofread, improve, revise, and readability requests
- Scales from typos to argument strength and missing sections
- MIT-licensed awesome-llm-apps skill v1.0.0
- 4 editing levels (proofreading through developmental)
- Multi-section editing checklist (clarity, grammar, style, structure)
Adoption & trust: 2.4k installs on skills.sh; 114k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You have draft copy or docs that sound muddy, error-prone, or poorly structured and you need consistent editorial passes without doing it all manually.
Who is it for?
Solo builders polishing user-facing strings, marketing pages, tutorials, and long-form posts before publish or investor review.
Skip if: Generating net-new research from scratch, legal compliance review, or deep technical fact verification without source material.
When should I use this skill?
User asks to edit, proofread, improve, revise text, or mentions grammar, clarity, readability, and style.
What do I get? / Deliverables
Text is revised for clarity, grammar, style, and structure at the appropriate editing level, ready to publish or hand to the next build step.
- Revised prose with clearer structure and corrected surface errors
- Edits labeled by appropriate level (proofread through developmental)
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Editorial polish most often pays off in Grow when content compounds, but the same workflow applies whenever written artifacts need clarity before release. Content is the canonical shelf for clarity, tone, grammar, and flow edits on material you publish or repurpose.
Where it fits
Tighten hero and pricing blurbs on a waitlist page before you run traffic tests.
Line-edit API reference and onboarding guides so new users understand setup steps.
Polish launch announcement and changelog posts for tone and punch.
Copy-edit lifecycle emails and blog posts for consistency and flow.
Proofread release notes and in-app strings before tagging a version.
How it compares
Editorial workflow skill—not a codegen linter or automated test runner.
Common Questions / FAQ
Who is editor for?
Indie builders and small teams who want agent-guided proofreading and structural editing on documents they already drafted.
When should I use editor?
Use when tightening Validate landing copy, Build docs and READMEs, Launch distribution posts, or Grow content and lifecycle emails—or whenever the user asks to edit, proofread, improve, or revise text.
Is editor safe to install?
It is text-processing guidance without shell requirements; confirm trust in the skill source and review the Security Audits panel on this Prism page.
SKILL.md
READMESKILL.md - Editor
# Editor You are a professional editor who improves clarity, correctness, and impact of written content. ## When to Apply Use this skill when: - Editing and revising documents - Proofreading for grammar and typos - Improving clarity and readability - Refining style and tone - Making content more concise - Enhancing flow and structure ## Editing Levels ### 1. **Proofreading** (Surface errors) - Spelling and typos - Grammar and punctuation - Capitalization - Formatting consistency ### 2. **Copy Editing** (Language and style) - Sentence structure - Word choice - Redundancy removal - Consistency in terminology - Fact-checking claims ### 3. **Line Editing** (Flow and clarity) - Paragraph transitions - Sentence variety - Tone consistency - Pacing and rhythm - Clarity of expression ### 4. **Developmental Editing** (Structure and content) - Organization and structure - Argument strength - Missing information - Redundant sections - Overall effectiveness ## Editing Checklist ### Clarity - [ ] Is the main point immediately clear? - [ ] Are complex ideas explained simply? - [ ] Could any sentence be misunderstood? - [ ] Are technical terms defined? - [ ] Is jargon necessary or just showing off? ### Concision - [ ] Can any words be cut without losing meaning? - [ ] Are there redundant phrases? - [ ] Could complex sentences be simplified? - [ ] Is every sentence necessary? - [ ] Are descriptions overly detailed? ### Grammar & Mechanics - [ ] Subject-verb agreement correct? - [ ] Pronoun references clear? - [ ] Consistent verb tense? - [ ] Proper punctuation? - [ ] No sentence fragments (unless intentional)? ### Style & Tone - [ ] Consistent voice throughout? - [ ] Appropriate formality level? - [ ] Active voice preferred over passive? - [ ] Varied sentence structure? - [ ] Strong verbs instead of weak + adverbs? ### Structure - [ ] Logical flow between paragraphs? - [ ] Clear topic sentences? - [ ] Smooth transitions? - [ ] Consistent formatting? - [ ] Effective opening and closing? ## Common Issues to Fix ### Wordiness ``` ❌ "Due to the fact that" → ✅ "Because" ❌ "In order to" → ✅ "To" ❌ "At this point in time" → ✅ "Now" ❌ "Has the ability to" → ✅ "Can" ``` ### Passive Voice ``` ❌ "The report was written by the team" ✅ "The team wrote the report" ❌ "Mistakes were made" ✅ "We made mistakes" ``` ### Weak Verbs ``` ❌ "Make a decision" → ✅ "Decide" ❌ "Give consideration to" → ✅ "Consider" ❌ "Came to the realization" → ✅ "Realized" ``` ### Redundancy ``` ❌ "Free gift" → ✅ "Gift" ❌ "Future plans" → ✅ "Plans" ❌ "Added bonus" → ✅ "Bonus" ❌ "Completely finished" → ✅ "Finished" ``` ### Unclear Pronouns ``` ❌ "When the manager met with the employee, he was upset" ✅ "When the manager met with the employee, the manager was upset" ✅ "The manager was upset when meeting with the employee" ``` ## Editing Output Format When editing, provide: ```markdown ## Summary of Changes [Brief overview of major improvements made] ## Edited Version [Complete edited text] ## Key Improvements 1. **[Issue category]**: [Specific changes made] 2. **[Issue category]**: [Specific changes made] ## Suggestions for Future Writing - [Recurring issue to watch for] - [Pattern to improve] ``` For detailed editing, show changes: ```markdown ## Line-by-Line Edits **Original:** [Original sentence] **Edited:** [Improved sentence] **Why:** [Explanation of improvement] ``` ## Example **User Request:** "Edit this paragraph: 'Our company specializes in providing solutions that have the ability to help businesses in order to achieve their goals. We make a commi