---
title: "Building a Claude Code Blog Skill"
description: "Building a Claude Code blog skill - how I turned my own blog workflow, from banned words to Vale linting and PRs, into a skill our marketing team can run."
url: https://www.joekarlsson.com/blog/building-a-claude-code-blog-skill-what-i-learned-systematizing-content-creation/
---

Oct 24, 2025 | 5 min read | [AI](https://www.joekarlsson.com/blog/category/ai/)

# Building a Claude Code Blog Skill: What I Learned Systematizing Content Creation

![Compositors setting type at wooden type cases](https://www.joekarlsson.com/images/blog/building-a-claude-code-blog-skill-what-i-learned-systematizing-content-creation/thumb-3595dc72.still.webp)

**Blog** Building a Claude Code blog skill - how I turned my own blog workflow, from banned words to Vale linting and PRs, into a skill our marketing team can run.

**TL;DR** I built a Claude Code slash command that turns blog post creation into a repeatable, enforceable workflow with brand voice checks, Vale linting, image generation, and automatic PR submission. It unblocked our marketing team from depending on me as the content quality bottleneck.

On this page

1.  [Codifying What I Was Already Doing](https://www.joekarlsson.com/blog/building-a-claude-code-blog-skill-what-i-learned-systematizing-content-creation/#codifying-what-i-was-already-doing)
2.  [Making Standards Executable](https://www.joekarlsson.com/blog/building-a-claude-code-blog-skill-what-i-learned-systematizing-content-creation/#making-standards-executable)
3.  [The Part I Didn’t Expect](https://www.joekarlsson.com/blog/building-a-claude-code-blog-skill-what-i-learned-systematizing-content-creation/#the-part-i-didnt-expect)
4.  [What’s Working, What Isn’t](https://www.joekarlsson.com/blog/building-a-claude-code-blog-skill-what-i-learned-systematizing-content-creation/#whats-working-what-isnt)
5.  [Where This Goes Next](https://www.joekarlsson.com/blog/building-a-claude-code-blog-skill-what-i-learned-systematizing-content-creation/#where-this-goes-next)

I live in the terminal. Like, I mean it.

**[1](https://www.joekarlsson.com/blog/building-a-claude-code-blog-skill-what-i-learned-systematizing-content-creation/#mn-w-1)**

[Breaking up with Claude Code](https://www.joekarlsson.com/blog/breaking-up-with-claude-code/): Later I tried OpenCode with open models in its place. It wasn’t a one-to-one swap.

As a developer advocate, it’s where I spend most of my time - running commands, testing code, writing docs. Over the past few months, Claude Code became my primary interface for getting work done [1](https://www.joekarlsson.com/blog/building-a-claude-code-blog-skill-what-i-learned-systematizing-content-creation/#mn-1), and not just for coding: content creation, documentation, the constant stream of blog posts that come with DevRel.

That created a weird problem.

I got good at using AI tools. But it was still a personal, one-off workflow. Every blog post started with me crafting the perfect prompt, tweaking the output, running linting checks, formatting everything manually. It worked, but it didn’t scale. Our marketing team needed to produce more content, hit more keywords, maintain consistency… and they couldn’t all live in my head.

_Diagram: A paper-collage animation on a black field: index cards pile onto a black-and-white phrenology bust, a pink card-catalog drawer lands beside it, the cards fly from the head into the drawer, and two hands reach in for them under the words Out of my head_

**[2](https://www.joekarlsson.com/blog/building-a-claude-code-blog-skill-what-i-learned-systematizing-content-creation/#mn-w-2)** Create a skill when you keep pasting the same instructions, checklist, or multi-step procedure into chat, or when a section of CLAUDE.md has grown into a procedure rather than a fact.[Claude Code's docs on skills](https://code.claude.com/docs/en/skills)

So I built a Claude Code skill to systematize it [2](https://www.joekarlsson.com/blog/building-a-claude-code-blog-skill-what-i-learned-systematizing-content-creation/#mn-2).

**[2](https://www.joekarlsson.com/blog/building-a-claude-code-blog-skill-what-i-learned-systematizing-content-creation/#mn-w-2)** Create a skill when you keep pasting the same instructions, checklist, or multi-step procedure into chat, or when a section of CLAUDE.md has grown into a procedure rather than a fact.[Claude Code's docs on skills](https://code.claude.com/docs/en/skills)

## Codifying What I Was Already Doing

The blog skill started as a way to encode my own process. I’d open Claude Code, start a conversation about a blog topic, go back and forth on structure, check for banned words, run Vale linting, generate images, submit a PR. Efficient for me, completely opaque to anyone else.

Then I realized I could encode all those standards - brand voice, banned words, style requirements, SEO checklists - into a reusable workflow: an executable skill that enforces them automatically.

What the skill does:

-   **Research the topic** - searches existing posts, docs, sources
    
-   **Create an outline** - structured with SEO and LLM citation optimization
    
-   **Checkpoint 1** - show the outline, get approval before drafting
    
-   **Write the draft** - following brand voice, with banned word checks
    
-   **Checkpoint 2** - review the draft before finalizing
    
-   **Vale linting** - enforce style consistency, must pass with 0 errors
    
-   **Generate images** - Python script creates header and thumbnail
    
-   **Submit PR** - ready for review  
    

The skill is a single slash command: /blog “topic”. That’s it.

## Making Standards Executable

Here’s how we enforce brand voice - this is from the actual skill file:

```text
Banned Words:
opt, dive, unlock, unleash, intricate, utilization, transformative,  alignment, proactive, scalable, delve, landscape, evolving, nuanced,  paradigm, comprehensive, holistic, synergy, pivotal, robust, empower,  enables, transforms, solution, optimized

Banned Phrases:
- "In today's world," "at the end of the day," "best practices"
- "Game-changer," "paradigm shift," "breakthrough technology"
- "Seamless integration," "effortless setup," "works like magic"
- "Enterprise-grade" (without defining), "industry-leading"
```

**[3](https://www.joekarlsson.com/blog/building-a-claude-code-blog-skill-what-i-learned-systematizing-content-creation/#mn-w-3)** Vale brings code-like linting to prose. Turn a team’s style guide, a house voice, or a journal’s author guidelines into checks that run in your editor and alongside your code.[Vale's homepage](https://vale.sh/)

When the skill generates a draft, it checks against these rules. Before creating a PR, it runs Vale linting [3](https://www.joekarlsson.com/blog/building-a-claude-code-blog-skill-what-i-learned-systematizing-content-creation/#mn-3), and it must pass with 0 errors. If banned words slip through, Vale catches them. Technical terms need backticks for formatting? Vale flags them.

**[3](https://www.joekarlsson.com/blog/building-a-claude-code-blog-skill-what-i-learned-systematizing-content-creation/#mn-w-3)** Vale brings code-like linting to prose. Turn a team’s style guide, a house voice, or a journal’s author guidelines into checks that run in your editor and alongside your code.[Vale's homepage](https://vale.sh/)

What used to require me reviewing every piece of content now happens automatically. The skill enforces consistency I couldn’t maintain manually across a team.

## **The Part I Didn’t Expect**

We rolled this out to the marketing team a week ago. (A few months later it had grown into a whole repo of skills the team runs; I wrote up [how my personal skills repo became internal tooling](https://www.joekarlsson.com/blog/my-personal-claude-code-skills-repo-accidentally-became-internal-tooling/) Apr 7, 2026**My Personal Claude Code Skills Repo Accidentally Became Internal Tooling** .)

They adopted it fast.

Giving this tool to the team replaced one of my primary functions: being the bottleneck for content quality and technical accuracy. And that’s freeing me up to do what I actually want to do: developer outreach, building relationships, experimenting with new approaches to advocacy.

_Diagram: A paper-collage animation on a black field: a black-and-white glass bottle lands in the middle, handwritten draft pages cram into it, a cork in full color plugs the narrow neck, then the cork pops off and the drafts spill out to both sides under the words I was the bottleneck_

We’re covering more keywords, faster. Blog posts ship with consistent voice and style. SEO optimization, FAQ sections, internal links, quotable statistics - are baked into the workflow instead of being an afterthought. The team can focus on research and strategy rather than fighting with formatting and style checks.

**[4](https://www.joekarlsson.com/blog/building-a-claude-code-blog-skill-what-i-learned-systematizing-content-creation/#mn-w-4)**

[What I Learned When I Could Finally Prove My Work Mattered](https://www.joekarlsson.com/blog/proving-my-work-mattered/): More content was the easy number to show. Whether any of it turned into customers took CRM data, and I wrote up what that data showed.

We don’t have metrics yet (it’s been three weeks), but we’re already producing more content than we were before [4](https://www.joekarlsson.com/blog/building-a-claude-code-blog-skill-what-i-learned-systematizing-content-creation/#mn-4).

## What’s Working, What Isn’t

AI tools are most powerful when they’re systematic. One-off prompts are useful. Codified workflows are different. The skill isn’t “use AI to write a blog post,” it’s “here’s our exact process, automated and enforceable.”

Quality controls matter. Without checkpoints and linting, AI output drifts. We have two approval gates (outline and draft) and automated linting before anything ships. This keeps quality high without manual review of every detail.

Approval gates add latency, though. Too many of them and you’re back to the slow, review-gated world you were trying to escape. The goal is kilns, not gates - feedback that improves the work, not gates that just add time. If you’re thinking about where the line is between “enough review” and “too much process,” I wrote about this directly in [Ship the Ugly Pot](https://www.joekarlsson.com/blog/ship-the-ugly-pot/) Sep 11, 2026**Ship the Ugly Pot** .

This doesn’t replace judgment. It can’t replace deep technical knowledge, understanding our audience, knowing when to break the rules. It handles structure, consistency, grunt work. Humans handle the hard stuff: knowing what to say, how to say it, when to bend the rules.

## Where This Goes Next

I’m not afraid of AI replacing developer advocacy work. I’m more worried about being too slow to adapt.

The industry is still figuring out what AI-assisted DevRel looks like. We’re in the crystallization phase - experimenting, sharing what works, discarding what doesn’t. I’m already thinking about the next iteration: using skills to personalize developer onboarding, create custom documentation paths, generate context-aware code examples.

The terminal has always been where I do my best work. Claude Code is one of several dev tools I use daily - I keep a full list on my [uses page](https://www.joekarlsson.com/uses/), and the reasoning behind it in my [2026 development setup](https://www.joekarlsson.com/blog/my-development-setup-2026/) Sep 30, 2026**My Development Setup in 2026** .

Now it’s where I build tools that let the whole team do theirs.

If you’re in DevRel or developer marketing: start small, build workflows, share what you learn. I’ve argued before that you should treat your project’s content like code, and this skill is the next step of that idea. We’re all defining what this looks like together.

## Works on My Machine

Get the next post by email. My newsletter covers homelab builds, AI tools and open source, and it goes out when I have something to say.

It’s free, and you can unsubscribe anytime. You’ll get an email to confirm first.

![Joe Karlsson at his desk, chin on hand, with a microphone in front of him](https://www.joekarlsson.com/images/about/collage/studio.webp)

Joe  
Karlsson

Technology is better when it's weird and it's yours. Everything I write about runs in my house.

[More about me →](https://www.joekarlsson.com/about/)

[Bluesky](https://bsky.app/profile/joekarlsson.com) | [LinkedIn](https://www.linkedin.com/in/joekarlsson/) | [GitHub](https://github.com/JoeKarlsson)
