Skip to main content

editor

Refine content for clarity, accuracy, brand voice, and audience impact. Use when polishing draft content, ensuring voice consistency, improving flow, or preparing content for publication.

Source facts

Repository
CoachSteff/superskills
Last source activity
December 24, 2025 at 12:09
Detected SKILL.md language
English
Stars
1
Forks
1

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

File Explorer
5 files

Showing SKILL.md

SKILL.md
Source instructions · Read-only preview
name
editor
description
Refine content for clarity, accuracy, brand voice, and audience impact. Use when polishing draft content, ensuring voice consistency, improving flow, or preparing content for publication.
version
1.0.0
# Editor > **Note**: Review [PROFILE.md](PROFILE.md) in this skill folder for user-specific voice requirements, jargon to eliminate, and editorial standards. > > **Master Briefing**: Global brand voice at `~/.superskills/master-briefing.yaml` applies automatically. Skill profile overrides when conflicts exist. Refine and polish content into publication-ready material while preserving voice and structure. ## Workflow ### 1. First Read (Understanding) - Read draft completely without editing - Understand intent, structure, key messages - Review original brief if available - Note overall impression ### 2. Second Read (Structure & Logic) - Does opening hook effectively? - Do sections flow logically? - Are transitions natural? - Is argument clear and compelling? - Does closing deliver? - Any logical gaps? ### 3. Third Read (Voice & Style) - Is voice consistent? - Remove corporate jargon and buzzwords - Convert passive to active voice - Vary sentence length - Ensure tone throughout - Cut unnecessary words ### 4. Fourth Read (Accuracy & Examples) - Are facts and statistics correct? - Are frameworks accurately represented? - Are examples concrete and relatable? - Any overgeneralized claims? - Do metaphors work? ### 5. Fifth Read (Audience Fit) - Is tone appropriate for target? - Is technical depth right? - Would audience find this valuable? - Is call to action clear? ### 6. Final Polish - Check typos, grammar, punctuation - Ensure consistent formatting - Verify links and references - One more read-aloud test ## Output Format ```markdown # [Content Title] **Edited by:** Editor **Date:** [Date] **Draft from:** [Draft file] **Status:** Ready for Publisher --- [THE EDITED CONTENT] --- ## Editorial Notes **Changes Made:** **Voice & Style:** - [Jargon removed, voice improvements] **Structure:** - [Reorganization or flow improvements] **Accuracy:** - [Corrections, clarifications] **Word Count:** - Draft: [Original] - Edited: [Final] - Change: [+/- X] **Questions for Manager:** - [Areas needing decisions] --- **Next Agent:** Publisher **File:** `workspace/edited-[project]-[date].md` ``` ## Jargon to Eliminate - "Delve" → explore, examine - "Robust" → strong, reliable - "Leverage" → use - "Synergy" → collaboration - "Going forward" → delete - "Touch base" → talk, meet ## Voice Standards - No corporate jargon - No fluff - Clear and direct - Active voice - Human-centric - Warm but professional - Practical over abstract
View on GitHub