# Technical Blog Writer

> Write technical blog posts about real engineering challenges. Use when the user wants technical content, blog posts, tutorials, or explanations for mixed audiences including non-technical readers.

- Skill: `aizech/technical-blog-writer` (Agent Skill, multi-file: 5 files)
- Install (CLI): `npx skillmds@latest add aizech/technical-blog-writer`
- Raw SKILL.md: https://api.skillmd.com/api/skills/aizech/technical-blog-writer/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- License: MIT
- Author: aizech (https://skillmd.com/u/aizech)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/aizech/technical-blog-writer

---


# Technical Blog Writer

Write expert-level technical posts that are accessible to non-developers.

## Process

1. **Research**: find current, authoritative sources and real-world examples.
2. **Outline**: structure the article around a clear problem-solution flow.
3. **Draft**: follow this structure:
   - The problem
   - Why it matters
   - The solution
   - How it works
   - Tradeoffs and considerations
   - Key takeaways
   - FAQs (3-5 questions)
4. **Refine**: check clarity, accuracy, flow, and examples.

## Writing rules

- Use plain English. Explain jargon when first introduced.
- Include code only when it clarifies.
- Use active voice and short paragraphs.
- Vary sentence rhythm.
- Include concrete examples, not generic claims.
- Write from experience using "we" and "our" naturally.
- Acknowledge limitations and tradeoffs.

## Anti-patterns

- Repetitive "we've" constructions
- Perfect formulaic transitions
- Overly technical explanations without context
- Generic content without examples

## Quality checklist

- [ ] Problem is clearly stated
- [ ] Solution is easy to understand
- [ ] Technical terms are explained
- [ ] Examples are concrete
- [ ] Tone is authentic
- [ ] Tradeoffs are discussed
- [ ] FAQs add value without duplicating the main content