Skill: tenequm/impactful-writing (version 0.1.1)

--- name: impactful-writing description: Write clear, emotionally resonant, and well-structured content that readers remember and act upon. Use when writing or editing any text—Twitter posts, articles, documentation, emails, comments, updates—for maximum clarity, engagement, and impact. metadata: version: "0.1.1" --- # Impactful Writing ## Overview Transform any content into clear, memorable, and actionable text using research-backed principles that work across all platforms and contexts. This skill synthesizes 50+ years of readability research, neuroscience of memory, and platform engagement studies into practical techniques. **Core insight**: The same psychological principles drive engagement everywhere—clarity reduces cognitive load, specificity creates memory, and structure enables scanning. Master these universal patterns and apply them to any writing context. ## When to Use This Skill - Writing or editing Twitter/X posts, threads, or social content - Creating blog posts, Medium articles, or long-form content - Drafting documentation, README files, or technical writing - Composing emails, Slack messages, or professional communication - Writing GitHub comments, PR descriptions, or code reviews - Creating update messages, announcements, or change logs - Editing any existing content for clarity and impact ## Universal Writing Principles These evidence-based principles work across all platforms and contexts. ### 1. Clarity Through Simplicity **Sentence length determines comprehension:** - 14 words: 90%+ reader comprehension - 25 words: Difficulty begins - 43 words: <10% comprehension **Target: 15-20 words average, 25 words maximum per sentence.** **Word choice matters:** - Simple words process 76% faster than jargon - Active voice processes 15-20% faster than passive - Concrete beats abstract (activates sensory brain regions) ### 2. Structure for Scanning **79% of readers scan rather than read.** Design for this reality: - Front-load key information (inverted pyramid) - Use descriptive headings every 3-4 paragraphs - Keep paragraphs to 3-5 sentences maximum - Use bullet points for 3+ related items - Optimal line length: 50-75 characters ### 3. Emotional Resonance **Stories trigger oxytocin release**, enabling empathy and memory formation: - Open with a hook (question, surprising fact, brief story) - Use sensory, concrete language - Create curiosity gaps (specific questions readers want answered) - Close with memorable takeaways (recency effect) ### 4. Specificity Over Abstraction Specific details outperform vague statements: - "45% increase" beats "significant growth" - "in 5 minutes" beats "quickly" - "10 ways" beats "several ways" - Concrete examples beat abstract explanations ## Quick Start Workflow ### Writing New Content 1. **Define the core message** in one sentence 2. **Open with a hook** (question, fact, or story) 3. **Structure with headings** for scannability 4. **Use short sentences** (15-20 words average) 5. **Close with clear takeaway** or call-to-action ### Editing Existing Content 1. **Read aloud** to identify awkward passages 2. **Cut word count** by 10-30% without losing meaning 3. **Convert passive to active** voice 4. **Replace jargon** with simple words 5. **Add structure** (headings, bullets, white space) ## Platform-Specific Guidance ### Twitter/X Posts - **Optimal length**: 71-100 characters for engagement - **Hook in first line**: Must capture in 3 seconds - **Use numbers**: "10 lessons" outperforms "lessons learned" - **Thread structure**: Each tweet must stand alone AND connect Example transformation: ``` Before: "I learned a lot from this experience and want to share some thoughts" After: "5 hard lessons from shipping 10,000 lines of code in 48 hours:" ``` ### Blog Posts / Articles - **Optimal reading time**: 7-10 minutes - **Headings**: Every 300-500 words - **First paragraph**: Must deliver the promise - **Conclusion**: Summarize key points, provide clear next step ### Technical Documentation - **Lead with the goal**: What will the reader accomplish? - **Show, don't tell**: Working code examples beat explanations - **Progressive disclosure**: Basic → Advanced - **Consistent terminology**: One term per concept ### Professional Communication (Email/Slack) - **Subject lines**: Specific over clever ("Q4 Report Draft" > "Quick update") - **One topic per message**: Increases response rate - **Front-load action items**: Don't bury the ask - **Keep to half-page maximum**: Longer = lower read rate ### GitHub Comments / PR Descriptions - **Start with context**: What problem does this solve? - **Use bullet lists**: For changes, decisions, trade-offs - **Include "why"**: Reasoning > description - **Be direct but kind**: Critique code, not people ## The Revision Checklist Use this checklist for any content revision: ``` Clarity Pass: - [ ] Average sentence length < 20 words - [ ] No sentence > 30 words - [ ] Passive voice < 10% of sentences - [ ] Jargon replaced with simple alternatives Structure Pass: - [ ] Opening hook captures attention - [ ] Key message in first paragraph - [ ] Headings every 3-4 paragraphs (for longer content) - [ ] Bullet points for lists of 3+ items - [ ] Clear call-to-action or takeaway at end Conciseness Pass: - [ ] Removed "very," "really," "quite," "just" - [ ] Replaced multi-word phrases with single words - [ ] Deleted redundant explanations - [ ] Cut 10-30% from original word count ``` ## Word Reduction Patterns Common phrases to simplify: | Wordy | Concise | |-------|---------| | due to the fact that | because | | in order to | to | | at this point in time | now | | in the event that | if | | with regard to | about | | a large number of | many | | in spite of the fact that | although | | for the purpose of | to | Complex words to simplify: | Complex | Simple | |---------|--------| | utilize | use | | commence | start | | terminate | end | | demonstrate | show | | facilitate | help | | subsequent | later | | approximately | about | | endeavor | try | ## Hook Patterns That Work ### Question Hook Opens with a question the reader wants answered: ``` "What if everything you knew about productivity was wrong?" ``` ### Statistic Hook Opens with surprising data: ``` "90% of visitors who read your headline also read your CTA—yet most writers spend 10x more time on body copy." ``` ### Story Hook Opens with a brief narrative: ``` "At 3 AM, with the deploy failing for the sixth time, I realized the bug wasn't in the code." ``` ### Declarative Hook Opens with a bold statement: ``` "Most advice about writing is wrong. Here's what actually works." ``` ### Contradiction Hook Challenges an assumption: ``` "The best writers don't write more. They delete more." ``` ## Memory and Impact Principles Content that sticks follows these patterns: ### Serial Position Effect - **First items**: ~70% recall (primacy) - **Last items**: ~60% recall (recency) - **Middle items**: ~40% recall **Implication**: Put most important points first and last. ### Prediction Errors Violated expectations create distinctive memories: ``` Before: "The meeting went exactly as planned." After: "The meeting started with our CEO apologizing. In 15 years, I'd never seen that." ``` ### Sensory Language Activates multiple brain regions: ``` Before: "The code was messy." After: "The code sprawled like tangled Christmas lights—one pull and everything breaks." ``` ## Common Anti-Patterns ### Over-Explaining **Problem**: Explaining what readers already know **Fix**: Assume intelligence, provide only new information ### Buried Lede **Problem**: Key point in paragraph 3 **Fix**: Move conclusion to opening, support with details ### Wall of Text **Problem**: Dense paragraphs without visual breaks **Fix**: Add headings, bullets, white space ### Passive Avoidance **Problem**: "Mistakes were made" (who made them?) **Fix**: "The team missed the deadline" (clear ownership) ### Jargon Cascade **Problem**: "We synergized cross-functional paradigms" **Fix**: "We got the teams to work together" ## Proven Content Frameworks ### AIDA (Attention → Interest → Desire → Action) Classic persuasion structure that works for any content with a goal: ``` Attention: "Most developers waste 3 hours/day on preventable bugs." Interest: "Static analysis catches 85% of these before they ship." Desire: "Teams using this approach ship 2x faster with fewer incidents." Action: "Add this one-line config to your CI pipeline." ``` ### PAS (Problem → Agitate → Solution) Effective for blog posts, landing pages, and persuasive content: ``` Problem: "Your documentation is outdated the moment you write it." Agitate: "New devs waste days. Senior devs answer the same questions. Nobody trusts the docs." Solution: "Generate docs from code comments. Always current, always trusted." ``` ### BAB (Before → After → Bridge) Transformation narrative that creates emotional resonance: ``` Before: "I spent 6 hours debugging a production issue." After: "Now I catch these problems before they deploy." Bridge: "Here's the monitoring setup that changed everything." ``` ### 1-2-3 Structure For instructional content—simple, scannable, actionable: ``` 1. The Problem: What's wrong and why it matters 2. The Solution: What to do about it 3. The How: Specific steps to implement ``` ## Detailed References For deeper guidance on specific topics: - **[references/clarity-science.md](references/clarity-science.md)**: Research on readability, cognitive load, and plain language with specific metrics - **[references/emotional-impact.md](references/emotional-impact.md)**: Neuroscience of storytelling, memory, and persuasion - **[references/structure-patterns.md](references/structure-patterns.md)**: Eye-tracking research, scanning patterns, and formatting - **[references/revision-frameworks.md](references/revision-frameworks.md)**: Professional editing processes and before/after examples ## Quick Reference: The CLEAR Framework **C** - Concise: Cut 10-30% without losing meaning **L** - Lead with value: Key point in first sentence **E** - Evidence-based: Specific data beats vague claims **A** - Active voice: Subject-verb-object structure **R** - Reader-focused: What do they need to know? ## Validation: Content Quality Check After writing, verify: 1. **Core message test**: Can you state it in one sentence? 2. **So what test**: After each paragraph, can you answer "so what"? 3. **Grandmother test**: Would a non-expert understand the main point? 4. **Action test**: Does the reader know what to do next? 5. **Cut test**: Can you remove any sentence without losing meaning? If any test fails, revise that section.


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)