playbooks

home / skills / kriscard / kriscard-claude-plugins / blog-writer

blog-writer skill

/plugins/content/skills/blog-writer

This skill helps transform scattered technical notes into polished blog posts by guiding structure, voice, and SEO-ready writing.

npx playbooks add skill kriscard/kriscard-claude-plugins --skill blog-writer

Review the files below or copy the command above to add this skill to your agents.

Files (5)
SKILL.md
2.7 KB
---
name: blog-writer
description: >-
  Transforms scattered notes and ideas into polished technical blog posts with SEO
  optimization. Make sure to use this skill whenever the user wants to write a blog
  post, has rough notes to turn into an article, mentions blog writing, technical
  writing, or publishing content — even if they just say "I have some thoughts I
  want to write up."
---

# Developer Blog Writer

Transform unstructured thoughts into polished technical blog posts.

## Reference Files

Load these before writing:

| File | Purpose |
|------|---------|
| `references/voice-tone.md` | Writing voice and style guide |
| `references/story-circle.md` | Narrative framework for posts |
| `references/post-templates.md` | Starter structures by post type |
| `references/seo-checklist.md` | Pre-publish SEO checks |

## Process

### 1. Receive the Brain Dump

Accept whatever is provided:
- Scattered thoughts and ideas
- Technical points to cover
- Code snippets or commands
- Conclusions or takeaways

Don't require organization. The mess is the input.

### 2. Load Voice Guide

Read `references/voice-tone.md` for writing style:
- Professional-casual tone
- First-person, inclusive language ("we", "us")
- Show the journey, not just the destination

### 3. Identify Post Type

| Type | Use When |
|------|----------|
| Tutorial | Step-by-step instructions |
| Project Showcase | Sharing what you built |
| Opinion | Your take on a topic |
| TIL | Quick, focused insight |
| Comparison | X vs Y analysis |

### 4. Check for Story Potential

Read `references/story-circle.md` and look for:
- Journey from confusion to clarity
- Problem you solved
- Something learned the hard way
- Perspective shift

### 5. Organize & Write

**Opening:** Hook with problem, question, or motivation. No "In this post, I will..."

**Body:**
- Vary paragraph length
- Include specific details
- Show actual code
- Be honest about what didn't work

**Ending:**
- Tie back to opening
- Actionable takeaway
- Forward-looking ("Stay tuned for...")

### 6. Review & Optimize

**Voice check:**
- Does it sound like a developer talking to peers?
- Is there a clear thread from start to finish?

**SEO check** (from `references/seo-checklist.md`):
- [ ] Primary keyword in title and first paragraph
- [ ] Meta description (150-160 chars)
- [ ] URL slug is short and clean
- [ ] 2-3 internal/external links
- [ ] Code blocks specify language

## Quick Voice Reference

### Do:
- Write like explaining to a smart colleague
- Admit uncertainty or mistakes
- Use specific examples with real details
- Show what you tried, not just what worked

### Don't:
- Use corporate or marketing speak
- Over-explain basic concepts
- Start with "In this post..." or "As we all know..."
- Force humor or excessive emojis

Overview

This skill transforms scattered notes, code snippets, and rough ideas into polished technical blog posts tailored for developer audiences. It focuses on narrative-driven, first-person writing that shows the journey, practical details, and reproducible code. Use it only for blog-style articles, not for formal documentation, specs, or talks.

How this skill works

It ingests raw brain dumps—notes, commands, code, and conclusions—without requiring prior organization, then identifies the best post type (tutorial, showcase, opinion, TIL, or comparison). The skill applies a developer-focused voice guide and a story framework to surface conflict, learning, and takeaways. Finally it generates a structured draft with a strong opening hook, practical body containing runnable code, and a concise, actionable ending, plus basic SEO suggestions.

When to use it

  • You have scattered ideas, terminal commands, or half-written notes for a blog post.
  • You want a narrative-focused technical article that shows how you solved a problem.
  • You need a draft that includes runnable code examples and honest post-mortems.
  • You want a quick conversion of a brain dump into a publishable outline or first draft.
  • You need SEO-aware blog content (title, slug, meta description) for a technical audience.

Best practices

  • Provide raw inputs: logs, commands, snippets, and short notes—no need to pre-organize.
  • Specify desired post type (tutorial, showcase, opinion, TIL, comparison) if you have one.
  • Point out any must-cover details (libraries, versions, constraints, audience level).
  • Ask for draft iterations: outline → full draft → SEO polish for best results.
  • Keep expectations clear: this produces a blog draft, not formal docs or slides.

Example use cases

  • Turn a weekend hack’s notes and terminal history into a project showcase post with setup and lessons learned.
  • Convert a troubleshooting session into a tutorial with step-by-step repro and fixes.
  • Draft an opinion piece from a set of bullet points and references arguing for a tooling choice.
  • Produce a short TIL entry from a single insight and minimal context.
  • Create a comparison post scaffold when you list pros/cons and a few benchmark notes.

FAQ

Can this produce final, publish-ready HTML?

It produces a polished markdown-ready draft with SEO suggestions and code blocks; final formatting and CMS-specific checks should be done in your publishing tool.

Will it preserve sensitive code or credentials?

It keeps whatever you provide. Remove secrets or sensitive data before ingesting to avoid leaking credentials.