technical-article-writer

Write technical articles and blog posts for developer audiences through a phase-gated workflow.

Updated May 23, 2026
One-click install
npx skills add https://github.com/Oatse/CWE-Automation --skill technical-article-writer-oatse
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: technical-article-writer
Source: https://github.com/Oatse/CWE-Automation/tree/main/.agents/skills/technical-article-writer
Command: npx skills add https://github.com/Oatse/CWE-Automation --skill technical-article-writer-oatse

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Technical articles often fail due to structural problems like buried ledes, weak openings, and mixed content types rather than bad ideas. This Skill guides you through a disciplined pipeline from idea sharpening to final draft so your content resonates with developer audiences. ## Core Features & Use Cases - Phase-Gated Workflow: Moves through intake interview, title generation, hook writing, body structuring, drafting, humanizing, image suggestions, and title finalization, asking clarifying questions before writing anything. - Structural Frameworks: Provides 8 content type templates (Bug Hunt, We Rewrote It in X, How We Built It, Lessons Learned, Trends, Benchmark, Tutorial, Explainer), 10 hook types, and 6 copywriting frameworks (PAS, AIDA, BAB, FAB, PASTOR, 4Us). - Use Case: You want to write about migrating your database from MongoDB to PostgreSQL. The Skill interviews you about audience and thesis, generates 10 ranked title variants, structures the article as a migration story with a 'what went wrong' section, and drafts the full piece with image placement suggestions. ## Quick Start Ask the assistant to help you write a technical blog post about your topic and answer its intake questions about audience, content type, and thesis.

Frequently Asked Questions about technical-article-writer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a technical blog post that developers actually read?

Start by sharpening your idea with a specific thesis, target audience, and content type before drafting. Lead with a strong hook, use one idea per section, show code examples before explanations, and avoid burying the lede or using generic preambles.

How to structure a debugging story or bug hunt article?

Use the Bug Hunt template: symptom, first hypothesis, investigation with dead ends, the revelation of the root cause, the fix, and a generalizable lesson. Build tension with plausible-but-wrong hypotheses before revealing the real cause.

What makes a good title for a technical article?

Aim for 7-12 words with specificity over cleverness, including tool or language names and concrete numbers. Avoid superlatives like 'ultimate' or 'complete', and generate at least 10 variants using different hook strategies before choosing.

When should I not use this article writing workflow?

Do not use it for platform-specific optimization, newsletter strategy, or ghostwriting voice matching, as these are explicitly out of scope. It is designed for long-form technical content for developer audiences, not marketing copy or social media posts.

Why does my technical article feel disjointed or lose readers?

The most common cause is mixing content types, such as a tutorial drifting into theoretical explanation, which the Diataxis framework diagnoses. Other causes include walls of unannotated code, momentum-killing transitions, and missing motivation for why the reader should care.