technical-blog-writing

Sterne1

Forks0

Aktualisiert9. Februar 2026 um 16:48

A comprehensive guide and toolkit for writing high-quality, popular technical blog posts for Zenn and Qiita.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

Quelle

mashharuki

mashharuki/claude-code-sample

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

Technische RedakteureKunst, Design, Unterhaltung, Sport und Medien·SOC 27-3042

Datei-Explorer

7 Dateien

SKILL.md

readonly

name	Technical Blog Writing
description	A comprehensive guide and toolkit for writing high-quality, popular technical blog posts for Zenn and Qiita.

Technical Blog Writing Skill

This skill is designed to help you write technical blog posts that are not only informative but also engaging and widely read on platforms like Zenn and Qiita.

🧠 Mindset: The "Future Self" & "Reader-First"

Write for your future self: If you stumbled upon this problem again in 6 months, what would you want to read?
Reader-First: Respect the reader's time. Give them the value (the "Aha!" moment) as quickly as possible.
Continuity: A good article is a "snapshot" of your learning journey. It doesn't have to be perfect, but it must be honest and helpful.

✍️ Workflow

1. Topic & Persona

Who is this for? (e.g., "Beginners to React", "Senior Backend Engineers struggling with scaling")
What problem does it solve? Be specific. "How to fix Error X" is better than "About Error X".

2. Outlining (The "Skeleton" Method)

Start with the Conclusion (What will the reader take away?).
Draft the Introduction (Hook the reader, state the problem, promise the solution).
List the Headings (The steps to get from Problem to Solution).
Tip: Use the view_file tool to read the templates/ directory for ready-to-use structures.

3. Drafting

Fill in the sections.
Use Code Blocks generously. Ensure they are copy-paste ready.
Use Zenn/Qiita specific markdown (Alerts, Details) to make it readable. See resources/markdown_cheatsheet.md.

4. Polishing

Title is King: Spend 50% of your time on the title. See resources/active_title_patterns.md.
Eye-catching OGP: If possible, create a simple but clear OGP image.

🚀 Viral Checklist

Before publishing, check these points:

Title: Does it contain specific keywords, numbers, or a strong benefit? (e.g., "3 ways to...", "Finally solved...")
Intro: Do you state the "Goal" and "Target Audience" in the first 10 lines?
Scannability: Can you understand the main points just by reading the headers?
Actionability: Can the reader immediately apply what they learned?
completeness: Did you include environment details (OS, versions) to prevent "works on my machine" issues?

📂 Resources

Templates - Ready-to-use markdown templates for different article types.
Title Patterns - Proven title formulas for high engagement.
Markdown Cheatsheet - Syntax guide for Zenn and Qiita.

Mehr aus diesem Repository

gleiches Repository

shipaton-strategist

mashharuki/claude-code-sample

RevenueCat主催のグローバルモバイルハッカソン「Shipaton」で入賞するための包括的戦略スキル。賞カテゴリ選定 → アイディア出し → 検証 → 要件定義 → 設計 → 開発計画 → グロース → ピッチ準備までを一気通貫で支援する。ユーザーが Shipaton / シップアトン / RevenueCat ハッカソン / shipaton.com / Devpost の RevenueCat Shipaton に言及したとき、「アプリをストア公開してマネタイズするハッカソン」「2ヶ月でアプリをリリースする」「RevenueCat SDKで課金を組み込むコンテスト」といった文脈が出たときは、アイディア出し・要件定義・設計・提出準備のどの段階の相談でも必ずこのスキルを使うこと。 Shipatonという単語が1回でも出たら、たとえ単純な質問に見えてもこのスキルを参照する。

2026-07-141

find-skills

mashharuki/claude-code-sample

Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.

2026-07-051

depitch-pitch-builder

mashharuki/claude-code-sample

DePitch Academy pitch BUILDER for Solana startups, DePitch is the #1 pitch academy of Solana. Use this skill ONLY when a builder wants to BUILD a pitch from scratch, structure a pitch deck, write a pitch script, or prepare an outline for a Colosseum/hackathon/VC/ICO/BD/Demo Day pitch on Solana. Trigger on: "build a pitch", "create a deck", "pitch deck outline", "pitch script", "structure my pitch", "help me pitch", "I have an idea I want to pitch", "I have a Colosseum pitch coming up", "demo day pitch", "hackathon pitch", "fundraising pitch on Solana", "Solana pitch", "ICO pitch", "build my Solana startup pitch". Do NOT trigger on requests to roast, review, critique, score, judge, or pressure-test an existing pitch.

2026-05-221

cfp-strategist

mashharuki/claude-code-sample

技術カンファレンス・勉強会のCFP（Call for Papers / プロポーザル）提出を戦略的にサポートするスキル。テーマ選定・CFP文章作成・レビューと改善の3フェーズを網羅し、採択率を劇的に向上させる。以下の状況で必ず使用すること: - ユーザーが「CFP」「プロポーザル」「登壇したい」「カンファレンスに応募」「スピーカー応募」「発表ネタ」と言ったとき - ユーザーが勉強会・技術イベントの応募文章を書こうとしているとき - 採択されるための文章の書き方や、何を書けばいいか迷っているとき - 既存のプロポーザルを見てほしい・改善したいというとき - 「カンファレンスで話したいが何を話せばいいかわからない」というとき

2026-05-161

proposal-writer

mashharuki/claude-code-sample

企画書・提案書の作成を包括的にサポートするスキル。ユーザーが企画書、提案書、事業計画書、イベント企画書、新規事業提案など「人を動かす文書」を作成したいとき、必ずこのスキルを使用する。このスキルは「企画書を書きたい」「提案書を作って」「新規事業の企画をまとめたい」「イベント企画書が必要」「社内提案をしたい」「プロジェクト提案書」「事業計画書」などのキーワードが含まれる場合に即座に起動する。また「何かアイデアをまとめたい」「上司に提案したい」「投資家向けの資料」なども該当する。ヒアリング → 構成案作成 → 企画書ドラフト → レビュー → 改善という5段階のプロセスで、説得力のある最高の企画書に仕上げる。

2026-05-141

ethglobal-strategist

mashharuki/claude-code-sample

ETH Global ハッカソン向けプロダクト戦略・アイデア創出・設計支援スキル。過去の ETH Global 受賞作品を徹底調査し、トレンド分析・アイデアブラッシュアップ・賞狙い戦略・技術設計まで一貫してサポートする。次のいずれかに当てはまる場合は必ずこのスキルを使用すること： - 「ETH Global」「ETHGlobal」「ethglobal」に関する質問 - Web3 / ブロックチェーンハッカソンのアイデア出し・戦略立案 - 過去の受賞プロジェクト・トレンドを調べたい - ハッカソン向けプロダクトをブラッシュアップしたい - どのスポンサー賞（prize）を狙うか相談したい - ハッカソンのデモ・ピッチ戦略を考えたい - 「ハッカソンアイデア」「ブロックチェーンハッカソン」「Web3 ハッカソン」を含む相談

2026-04-241

Technical Blog Writing Skill

This skill is designed to help you write technical blog posts that are not only informative but also engaging and widely read on platforms like Zenn and Qiita.

🧠 Mindset: The "Future Self" & "Reader-First"

Write for your future self: If you stumbled upon this problem again in 6 months, what would you want to read?

Reader-First: Respect the reader's time. Give them the value (the "Aha!" moment) as quickly as possible.

Continuity: A good article is a "snapshot" of your learning journey. It doesn't have to be perfect, but it must be honest and helpful.

✍️ Workflow

1. Topic & Persona

Who is this for? (e.g., "Beginners to React", "Senior Backend Engineers struggling with scaling")

What problem does it solve? Be specific. "How to fix Error X" is better than "About Error X".

2. Outlining (The "Skeleton" Method)

Start with the Conclusion (What will the reader take away?).

Draft the Introduction (Hook the reader, state the problem, promise the solution).

List the Headings (The steps to get from Problem to Solution).

Tip: Use the view_file tool to read the templates/ directory for ready-to-use structures.

3. Drafting

Fill in the sections.

Use Code Blocks generously. Ensure they are copy-paste ready.

Use Zenn/Qiita specific markdown (Alerts, Details) to make it readable. See resources/markdown_cheatsheet.md.

4. Polishing

Title is King: Spend 50% of your time on the title. See resources/active_title_patterns.md.

Eye-catching OGP: If possible, create a simple but clear OGP image.

🚀 Viral Checklist

Before publishing, check these points:

Title: Does it contain specific keywords, numbers, or a strong benefit? (e.g., "3 ways to...", "Finally solved...")

Intro: Do you state the "Goal" and "Target Audience" in the first 10 lines?

Scannability: Can you understand the main points just by reading the headers?

Actionability: Can the reader immediately apply what they learned?

completeness: Did you include environment details (OS, versions) to prevent "works on my machine" issues?

📂 Resources

Templates - Ready-to-use markdown templates for different article types.

Title Patterns - Proven title formulas for high engagement.

Markdown Cheatsheet - Syntax guide for Zenn and Qiita.