agentleFS
GoogleKnown publishergoogle/adk-samples/contrib/python/agent-skills-tutorial/app/skills/blog-writer/SKILL.md

blog-writer

Skill11k starsChanged 44 days agoApache-2.0View on GitHub

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.

32 other projects use a version of this.

Trending

More talk lately.about the whole repository

Dec 2025: 1 mentionJan 2026: 1 mentionFeb 2026: 2 mentionsMar 2026: 0 mentionsApr 2026: 0 mentionsMay 2026: 1 mentionJun 2026: 1 mentionJul 2026: 2 mentionsAug 2026: 0 mentionsSep 2026: 4 mentionsOct 2026: 4 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the google/adk-samples repository that our weekly crawl found. There is no adoption data for this file yet.

Most recently taken up by

Who's talking about google/adk-samples

The biggest 5 of 32 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 32

Talked about on GitHub, Bluesky, Hacker News and Stack Overflow (32 times).

On GitHub · 23

18 more on GitHub

On Bluesky · 4

Used with

Projects with it also use aminer-data-search, auto-target-tracker and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • dav-niu474Skill

    aminer-data-search

    使用 AMiner 开放平台 API 进行学术数据查询与分析。当用户需要查询学者信息、论文详情、机构数据、期刊内容或专利信息时使用此 skill。 触发场景:提到 AMiner、学术数据查询、查论文/学者/机构/期刊/专利、学术问答搜索、引用分析、科研机构分析、学者画像、论文引用链、期刊投稿分析等。 支持 6 大组合工作流(学者全景分析、论文深度挖掘、机构研究力分析、期刊论文监控、学术智能问答、专利链分析)以及 28 个独立 API 的直接调用。 即使用户只说"帮我查一下 XXX 学者"或"找找关于 XXX 的论文",也应主动使用此 skill。

    Also in 4 projects that use this

  • dav-niu474Skill

    auto-target-tracker

    自动目标进度追踪器。在对话中检测到目标相关图片(笔记、进度、截图、记录)时,自动调用 VLM 识别关键信息并记录到目标日记。适用于学习管理、健身追踪、工作进度、习惯养成、创作记录等所有目标管理场景。

    Also in 4 projects that use this

  • Liang-MHSkill

    stock_analysis

    获取 A 股、基金和港股的实时行情和技术分析数据

    Also in 4 projects that use this

  • +9 more from dav-niu474

The file

We split this skill into the rules it gives an agent

9 rules. 0 are common, 8 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 29 edited versions we read keep these.

  • 8

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

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

    line 8
  2. Very specific:

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

    line 11
  3. Distinctive:

    Before writing, create a brief outline with:

    line 14
  4. Distinctive:

    Start with a clear subheading (H2)

    line 22
  5. Distinctive:

    Keep paragraphs to 2-3 sentences

    line 25
  6. Distinctive:

    Use bullet lists for steps or comparisons

    line 26
  7. Distinctive:

    Add transition sentences between sections

    line 29
  8. Distinctive:

    Ensure consistent tone throughout

    line 30
  9. Distinctive:

    Verify all code examples are complete and runnable

    line 31

“Common” is measured: kept by at least 6 in 10 of the 29 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.