Index of every page on this site: llms.txt
All skills
google avatar

/blog-writer

@ead8d7f
by googlegoogle/adk-recipes11k stars
2,961
Run it yourself

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.

  • 2 files
  • 2.4 KB
  • Updated 2 months ago
  • GitHub
Use this Skill: https://skilld.dev/gh/google/adk-recipes/blog-writer

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈59 tokens for metadata: the name and description. ≈250 when used: this file. ≈301 more on demand in 1 file.

Description uses 2.9% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈236 characters, or 2.9%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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:

  1. Start with a clear subheading (H2)
  2. Lead with the key point, then support it
  3. Include code examples where relevant (use fenced code blocks with language tags)
  4. Keep paragraphs to 2-3 sentences
  5. 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

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No third-party reports yet.

Signed by skilld at ead8d7f. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 2 days ago.

Activeupdated 2 months ago

README badge

README badge for google/adk-recipes/blog-writer