Blog Writer Agent Skill
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.
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/google/adk-samples --skill blog-writerWhat comes with it
1 204 bytes besides the instructionThe instruction itself
5 sections, as written by the authorBlog 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
Other skills for the same job
different authors, same section of the catalogue
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
Use when implementing any feature or bugfix, before writing implementation code
Use when you have a spec or requirements for a multi-step task, before touching code
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Use when writing or improving README files. Not all READMEs are the same — provides templates and guidance matched to your audience and project type.
| Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, negative parallelisms, and excessive conjunctive phrases.
Official Opentrons Protocol API for OT-2 and Flex robots. Use when writing protocols specifically for Opentrons hardware with full access to Protocol API v2 features. Best for production Opentrons protocols, official API compatibility. For multi-vendor automation or broader equipment control use pylabrobot.
How to use it
Take google/blog-writer from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
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.