blog_writer

Generate technical blog posts with problem-first hooks and code explanations.

2|2|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/onmyway133/skills --skill blog-writer-onmyway133
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: blog_writer
Source: https://github.com/onmyway133/skills/tree/main/skills/blog-writer
Command: npx skills add https://github.com/onmyway133/skills --skill blog-writer-onmyway133

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you write clear, engaging, and structured technical blog posts and documentation that effectively explain complex topics and code.

Core Features & Use Cases

  • Structured Writing: Provides templates and guidance for article flow, from problem identification to conclusion.
  • Engaging Hooks: Offers strategies for captivating introductions that grab reader attention.
  • Code Explanation: Guides on how to present code examples with clear intent and breakdowns.
  • Tone & Voice: Advises on maintaining an accessible, professional, and collaborative tone.
  • Use Case: You need to write a tutorial on a new Swift feature. This Skill will help you structure the article, introduce the concept with a relatable problem, present code snippets effectively, and conclude with actionable advice.

Quick Start

Use the blog_writer skill to draft an article about Swift concurrency, starting with a problem-focused hook and including code examples.

Frequently Asked Questions about blog_writer

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

FAQPage Schema
How do I write technical blog posts that keep readers engaged?

To write engaging technical blog posts, start with a problem-first hook, introduce intent before showing code, and build progressive complexity so readers follow along easily. Maintain an accessible, professional tone throughout the article.

What is the best way to structure a coding tutorial with code examples?

The best way to structure a coding tutorial is to present code-first explanations with clear intent, progressive complexity, and actionable conclusions. Open with a relatable problem, layer details gradually, and close with practical advice.

Can I use this approach to draft documentation for a new programming feature?

Yes, you can draft documentation for a new programming feature by applying a problem-first opening and progressive complexity. This approach ensures your technical content remains engaging while guiding readers from basic concepts to advanced implementation.

How do I explain complex code clearly in a technical article?

To explain complex code clearly in a technical article, state the intent behind the code before presenting the snippet, then break down the logic step by step. This code-first explanation method ensures readers grasp the purpose before the implementation.

What should a technical writing introduction include to capture attention?

A technical writing introduction should include a problem-first hook that identifies a relatable issue the reader faces. This engaging strategy grabs attention immediately and establishes relevance before introducing progressive technical complexity.