impactful-writing
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.
tenequm · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add tenequm/skills --skill impactful-writing技能说明
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.4" categories: "creative, knowledge" topics: "writing, editing, storytelling, clarity, copywriting" openclaw: homepage: https://github.com/tenequm/skills/tree/main/skills/impactful-writing emoji: "✍️"
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
- Define the core message in one sentence
- Open with a hook (question, fact, or story)
- Structure with headings for scannability
- Use short sentences (15-20 words average)
- Close with clear takeaway or call-to-action
Editing Existing Content
- Read aloud to identify awkward passages
- Cut word count by 10-30% without losing meaning
- Convert passive to active voice
- Replace jargon with simple words
- 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 | alth |