How do I install the Google Blog Style skill?

Run npx skillmds@latest add danicat/google-blog-style in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Google Blog Style safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: executes scripts. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Google Blog Style?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Google Blog Style free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under Apache-2.

Who published Google Blog Style?

danicat (@danicat) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Google Blog Style by danicat — Agent Skill

Name: Google Blog Style
Rating: 4.5 (4 reviews)
Author: danicat

Google Blog Style

Style guide, legal compliance standards, and validation workflow for the Google Developers Blog. Enforces technical readability targets (Fog Index 12–15), professional tone, inclusive language, legal compliance, and style linting via Vale and Speedgrapher. Activate when drafting, editing, reviewing, or validating technical blog posts and articles for the Google Developers Blog.

danicat Updated Sep 22, 2026

File contents

Google Blog Style Guide

Use this skill to strictly focus on drafting, editing, and validating technical blog posts, articles, and reviews for official Google Developer blogs.

Core Mandates

Readability First: Target a Gunning Fog Index between 12 and 15 (Professional/Technical).
Deterministic Tooling: Run the validation scripts to ensure code safety and legal compliance.
Inclusive Language: Avoid niche jargon unless it is widely understood globally. See references/style_guide/jargon.md.
Legal Safety: Do not make unsubstantiated claims or discuss future roadmaps. Follow references/legal_guidelines.md.

Workflow: Strict Plan-Validate-Execute

1. Plan

Before writing:

Define Goals: Identify the key takeaway and target audience.
Consult Guides:
- references/writing_guide.md (Tone and Structure).
- references/nomenclature_tags.md (Correct tagging).
Outline: Use assets/template.md as a structural starting point.
Style Guide Search: Always use grep_search progressively within references/style_guide/ to confirm specific formatting or brand rules before making assumptions.

2. Execute

Write: Focus on clarity, enthusiasm, and technical accuracy.
- Use sentence case for all headings.
- Adhere to rules found via grep_search in references/style_guide/.
Modularize: Keep SKILL.md brief by putting detailed docs in the references/ folder.
Refine: Ensure the call to action is clear and all placeholder links use example.com.

3. Validate (Mandatory)

GOTCHA: If the speedgrapher MCP server is available, you MUST use Speedgrapher's tools and skills (speedgrapher.vale, speedgrapher.fog, speedgrapher.slop) to validate drafts instead of the custom local scripts.

If speedgrapher is unavailable, use the following validation scripts:

All-in-One Validation: Run node scripts/validate_all.cjs <path-to-draft> to run style linting, fog checks, and legal checks in one step, outputting a concise Markdown report.
Standalone Checks:
- Linting: node scripts/lint_style.cjs <path-to-draft> (Uses Vale).
- Readability: Run node scripts/fog.cjs <path-to-draft>.
- Sanitization: node scripts/sanitize_blog.cjs <path-to-draft>.
Legal Review: Manually check against references/legal_guidelines.md.

Resources

Template: assets/template.md
Validation: scripts/validate_all.cjs
Guides:
- references/writing_guide.md
- references/legal_guidelines.md (CRITICAL)
- references/style_guide/ (Comprehensive style reference)
- references/nomenclature_tags.md

---name: google-blog-styledescription: Style guide, legal compliance standards, and validation workflow for the Google Developers Blog. Enforces technical readability targets (Fog Index 12–15), professional tone, inclusive language, legal compliance, and style linting via Vale and Speedgrapher. Activate when drafting, editing, reviewing, or validating technical blog posts and articles for the Google Developers Blog.license: Apache-2.0---# Google Blog Style GuideUse this skill to strictly focus on drafting, editing, and validating technical blog posts, articles, and reviews for official Google Developer blogs.## Core Mandates1. **Readability First**: Target a Gunning Fog Index between **12 and 15** (Professional/Technical).2. **Deterministic Tooling**: Run the validation scripts to ensure code safety and legal compliance.3. **Inclusive Language**: Avoid niche jargon unless it is widely understood globally. See `references/style_guide/jargon.md`.4. **Legal Safety**: Do not make unsubstantiated claims or discuss future roadmaps. Follow `references/legal_guidelines.md`.## Workflow: Strict Plan-Validate-Execute### 1. Plan**Before writing:**1. **Define Goals**: Identify the key takeaway and target audience.2. **Consult Guides**: - `references/writing_guide.md` (Tone and Structure). - `references/nomenclature_tags.md` (Correct tagging).3. **Outline**: Use `assets/template.md` as a structural starting point.4. **Style Guide Search**: Always use `grep_search` progressively within `references/style_guide/` to confirm specific formatting or brand rules before making assumptions.### 2. Execute1. **Write**: Focus on clarity, enthusiasm, and technical accuracy. - Use sentence case for all headings. - Adhere to rules found via `grep_search` in `references/style_guide/`.2. **Modularize**: Keep `SKILL.md` brief by putting detailed docs in the `references/` folder.3. **Refine**: Ensure the call to action is clear and all placeholder links use `example.com`.### 3. Validate (Mandatory)> **GOTCHA:** If the `speedgrapher` MCP server is available, you MUST use Speedgrapher's tools and skills (`speedgrapher.vale`, `speedgrapher.fog`, `speedgrapher.slop`) to validate drafts instead of the custom local scripts.If `speedgrapher` is unavailable, use the following validation scripts:1. **All-in-One Validation**: Run `node scripts/validate_all.cjs <path-to-draft>` to run style linting, fog checks, and legal checks in one step, outputting a concise Markdown report.2. **Standalone Checks**: - **Linting**: `node scripts/lint_style.cjs <path-to-draft>` (Uses Vale). - **Readability**: Run `node scripts/fog.cjs <path-to-draft>`. - **Sanitization**: `node scripts/sanitize_blog.cjs <path-to-draft>`.3. **Legal Review**: Manually check against `references/legal_guidelines.md`.## Resources- **Template**: `assets/template.md`- **Validation**: `scripts/validate_all.cjs`- **Guides**: - `references/writing_guide.md` - `references/legal_guidelines.md` (CRITICAL) - `references/style_guide/` (Comprehensive style reference) - `references/nomenclature_tags.md`

Frequently asked questions