Technical Writing

Turns corporate speak and vague claims into concrete technical content backed by real examples. Built around a simple framework: lead with value, show don't tell, cut ruthlessly. Comes with before/after transformations, an editing checklist, and audience-specific guidance for devs versus leadership. The quick reference card is genuinely useful, like "Bug detection: 12→47 per sprint" instead of "We improved testing." Integrates with qe-quality-analyzer for doc generation and review. The core insight is right: you're not writing to impress, you're helping people solve problems you've already solved. Works for blog posts, API docs, tutorials, anything technical that needs clarity over cleverness.

skills.sh installs: 205
GitHub stars: 524
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add proffesor-for-testing/agentic-qe --skill technical-writing --agent claude-code

Installs into .claude/skills of the current project.

Files

Technical Writing

<default_to_action> When writing technical content:

LEAD with value (what will reader learn/gain?)
SHOW, don't tell (specific examples, code, and numbers you measured or can source)
STRUCTURE for scanning (headers, bold, short paragraphs)
CUT ruthlessly (every sentence must earn its place)
BE honest about trade-offs
NEVER invent figures: every number, duration, and date traces to a source (tracker, benchmark, PR, release note). Missing a number? Write [number?] and ask, or describe what changed without one.

Blog Post Structure:

# Title (specific promise)

## Opening (2-3 paragraphs)
- Hook: The problem or insight
- Context: Why this matters
- Promise: What they'll learn

## Body (3-5 sections)
- One clear idea per section
- Support with examples/code/data

## Closing
- Key takeaway (1-2 sentences)
- Action reader can take

Before/After: ❌ "We implemented a comprehensive testing strategy..." ✅ "We moved exploratory testing into sprint planning. QE now pairs with devs during story refinement." </default_to_action>