mcpbeat

Blog Writer

google/blog-writer

Blog post writing skill with structure templates and style guidelines. Guides the agent through writing well-structured, engaging technical blog posts with proper formatting, section flow, and reader engagement techniques.

616 tokens
context cost
the whole folder, loaded on every use
2
files
instructions only
0
copies elsewhere
how many repositories repackaged it
10025
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/google/adk-samples --skill blog-writer

What comes with it

1 204 bytes besides the instruction
references/style-guide.md

The instruction itself

5 sections, as written by the author

Blog Writer Instructions

When asked to write a blog post, follow these steps:

Step 1: Structure

Use load_skill_resource to read references/style-guide.md for the writing style rules.

Step 2: Outline First

Before writing, create a brief outline with:

  • Hook: Opening that grabs attention (question, bold claim, or relatable problem)
  • Context: Why this topic matters now
  • Core sections: 3-5 sections that build on each other
  • Takeaway: What the reader walks away knowing

Step 3: Write Each Section

For each section:

  • Start with a clear subheading (H2)
  • Lead with the key point, then support it
  • Include code examples where relevant (use fenced code blocks with language tags)
  • Keep paragraphs to 2-3 sentences
  • Use bullet lists for steps or comparisons

Step 4: Polish

  • Add transition sentences between sections
  • Ensure consistent tone throughout
  • Verify all code examples are complete and runnable
  • End with a clear call-to-action or next steps

How to use it

Copy the folder

Take google/blog-writer from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.