Stats
Actions
Tags
From business-skills
Generates a polished, publication-ready tech blog post in Markdown from user-provided topic, content draft, and optional reference links or file attachments. Use this skill whenever the user wants to write, draft, or produce a tech blog post, article, tutorial, how-to guide, tool comparison, or release notes — even if they only say "write a post about X" or "turn my notes into a blog post". Trigger also when the user provides rough notes, bullet points, or a messy draft and asks to clean it up into a publishable article. The skill fetches linked URLs and extracts curated code snippets from official docs or repositories when available.
How this skill is triggered — by the user, by Claude, or both
Slash command
/business-skills:tech-blog-writerThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Transforms raw user input — a topic, a content draft, and optional links or attachments — into
Transforms raw user input — a topic, a content draft, and optional links or attachments — into a complete, well-structured tech blog post written in Markdown, ready for static site generators (Astro, Next.js, Hugo, Jekyll) or any Markdown-based CMS.
A single, self-contained .md file that:
## main sections and ### subsections| Input | Required | Description |
|---|---|---|
topic | ✅ | The subject or working title of the post |
content_draft | ✅ | Raw notes, bullet points, or rough prose |
links | ✴️ | URLs to related posts, docs, GitHub repos, official references |
attachments | ✴️ | Uploaded files (code files, markdown, PDFs, images) |
Follow these three steps in order.
topic and content_draft provided by the user.web_fetch tool to retrieve the page content.⚠️ Could not fetch
<url>— skipping this reference and continuing.
Evaluate whether the draft contains enough substance to write a quality post.
Minimum bar to proceed:
If the draft falls short, ask targeted follow-up questions before writing. Ask all missing questions in a single message — do not spread them across multiple turns. Examples:
Repeat this loop until the minimum bar is met. Once it is, proceed to Step 3.
Produce the full Markdown blog post using the output structure defined below. Write the finished Markdown to a file named:
[date]-[topic-slug]-post.md
in the current working directory (or one the user has indicated). Use kebab-case for the slug
(e.g. 2026-03-16-getting-started-with-astro-post.md).
After writing the file, tell the user:
---
layout: post
navigation: true
title: "Post Title"
description: "One-sentence summary for SEO and previews."
date: YYYY-MM-DD # replace with today's date, e.g. 2026-03-16
tags: [tag1, tag2, tag3]
categories: [category1, category2]
author: "michael"
class: post-template
subclass: post
---
## Introduction
Hook the reader in 2–3 sentences. State the problem being solved or the thing being learned.
Briefly mention what the post covers.
---
## Section title
Body content. Use `##` for main sections and `###` for subsections.
### Subsection (if needed)
...
## Code examples
Use the appropriate code block style:
- **Fenced blocks** for language-specific code:
```language
// code here
Shell/terminal blocks for CLI commands:
npm install example-package
Diff blocks for showing changes:
- old line
+ new line
Inline code for short references within prose: use backticks.
💡 Tip: Use callout blockquotes to highlight important notes or warnings.
Summarise the key points. Include a call-to-action: link to docs, suggest next steps, or invite comments.
References:
---
## Code inclusion rules
- Include **key snippets only** — the minimal code needed to understand or replicate the concept.
- Prefer complete, runnable examples over fragments when the source provides them.
- Always specify the language identifier on fenced blocks (` ```js `, ` ```python `, etc.).
- If code is taken from an external source, add a comment attribution:
```js
// Source: https://example.com/docs/getting-started
Before finalising, verify:
date field uses YYYY-MM-DD format and reflects today's datetags array contains 3–6 relevant, lowercase tags## sections have meaningful, sentence-case headings> 💡) is present[topic-slug]-post.md in kebab-caseIn scope:
Out of scope:
Guides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.
npx claudepluginhub mikamboo/agent-skills --plugin business-skills