blog-post-creator

Create new blog posts with proper frontmatter, structure, and ScottInk voice. Use when writing blog posts or starting technical articles.

⭐55stars🔀11forks📁View on GitHub🕐Updated Jan 3, 2026⬇️2downloads

When & Why to Use This Skill

The Blog Post Creator is a specialized Claude skill designed to automate the generation of high-quality technical blog posts and articles. It ensures consistent formatting by automatically generating proper markdown frontmatter and adhering to a structured narrative flow (Opening, Investigation, Solution, and Results). This skill is particularly effective for developers and writers who need to maintain a specific brand voice—the 'ScottInk' style—which emphasizes a conversational, code-first approach using British English conventions.

Use Cases

  • 1. Technical Article Drafting: Quickly initialize new technical posts with pre-configured metadata and a proven structural framework to overcome writer's block.
  • 2. Brand Voice Standardization: Ensure all content produced follows specific stylistic guidelines, such as first-person perspective, British English spelling, and a self-deprecating, conversational tone.
  • 3. Automated Content Organization: Streamline the workflow of creating, naming (kebab-case), and saving blog files directly into the project's directory structure using integrated file tools.
  • 4. Code-Centric Storytelling: Transform technical solutions and code snippets into engaging narratives that focus on the 'how' and 'why' of the development process.
nameblog-post-creator
descriptionCreate new blog posts with proper frontmatter, structure, and ScottInk voice. Use when writing blog posts or starting technical articles.
allowed-toolsRead, Write, Edit, Glob

Blog Post Creator

Create new blog posts with proper frontmatter, markdown structure, and adherence to the ScottInk voice guidelines.

Quick Start

Create a new post in posts/ with this frontmatter:

---
title: 'Your Post Title Here'
date: YYYY-MM-DD
published: false
---

Always set published: false initially.

Core Structure

Use this flow for all posts:

  1. Opening - Hook reader, set context (problem/motivation)
  2. Investigation - Show your process
  3. Solution - Code-first with working examples
  4. Results - Learnings, metrics, takeaways

ScottInk Voice Essentials

  • First-person - "I did...", "I found..."
  • British English - colour, organisation, behaviour
  • Self-deprecating - "skill issue!", "Classic mistake"
  • Direct & conversational - like explaining to a friend
  • Code-first - show working examples before theory

File Location

Save to posts/ with kebab-case: my-post-title.md

References

For detailed guidelines, examples, and complete style guide: