qe-technical-writing

Installation
SKILL.md

Technical Writing

<default_to_action> When writing technical content:

  1. LEAD with value (what will reader learn/gain?)
  2. SHOW, don't tell (specific examples, code, numbers)
  3. STRUCTURE for scanning (headers, bold, short paragraphs)
  4. CUT ruthlessly (every sentence must earn its place)
  5. BE honest about trade-offs

Blog Post Structure:

# Title (specific promise)

## Opening (2-3 paragraphs)
- Hook: The problem or insight
- Context: Why this matters
- Promise: What they'll learn
Related skills
Installs
46
GitHub Stars
348
First Seen
Feb 27, 2026