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.

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./python/agents/agent-skills-tutorial/app/skills/blog-writer/SKILL.md

Quality

Content

86%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is a lean, well-organized instruction skill with a clear multi-step workflow and an appropriately offloaded one-level-deep reference. The only gaps are the absence of a worked example and an explicit verify-fix-retry loop, which are minor for a non-destructive writing task.

Dimension	Reasoning	Score
Conciseness	The body is lean and efficient with no over-explanation of concepts Claude already knows; every line is direct, actionable instruction and each token earns its place, matching anchor 5.	5 / 5
Actionability	Concrete, executable guidance (load_skill_resource to read references/style-guide.md, a 4-part outline template, 5 numbered writing rules, a polish checklist) with only a minor gap: no worked example outline or sample section, matching anchor 4 rather than the fully-exampled anchor 5.	4 / 5
Workflow Clarity	A clear 4-step sequence (Structure, Outline, Write, Polish) with a verify checkpoint ('Verify all code examples are complete and runnable'), but it lacks an explicit fix-and-retry feedback loop on that verification, matching anchor 4 rather than anchor 5.	4 / 5
Progressive Disclosure	A concise overview with a well-signaled, verified one-level-deep reference (references/style-guide.md, which exists and is self-contained), with content appropriately split between inline workflow and the separate style guide; the under-50-line simple-skill exception applies, matching anchor 5.	5 / 5
	Total	18 / 20 Passed

Description

53%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description clearly conveys the skill's purpose and domain but lacks explicit trigger ('when to use') guidance and leans on output qualities rather than enumerated concrete actions. Its keyword coverage is reasonable but narrow, with some overlap risk against generic writing skills.

Suggestions

Add an explicit 'Use when...' clause naming concrete triggers, e.g. 'Use when the user asks to write a blog post, article, or technical write-up, or mentions blog content or post formatting.'

Reframe output qualities as concrete actions the skill performs, e.g. 'Drafts, outlines, and polishes technical blog posts' instead of 'Guides the agent through writing...with proper formatting'.

Broaden trigger terms with synonyms users actually say ('article', 'write-up', 'blog content', 'post') to improve keyword coverage and reduce conflict with general writing skills.

Dimension	Reasoning	Score
Specificity	Names the domain and lists concrete concerns ('structure templates', 'style guidelines', 'proper formatting', 'section flow', 'reader engagement techniques'), but the action verbs are limited to 'writing'/'Guides the agent through writing' while the rest are output qualities rather than distinct actions, matching anchor 3.	3 / 5
Completeness	It clearly states the 'what' (writing well-structured technical blog posts) but provides no 'Use when...' clause or equivalent trigger guidance, which the rubric caps at 3.	3 / 5
Trigger Term Quality	Includes natural phrases ('blog post writing', 'technical blog posts') but these are one concept with modifiers, missing common synonyms like 'article', 'write-up', or 'content', matching anchor 3 rather than the multi-keyword anchor 4.	3 / 5
Distinctiveness Conflict Risk	'Blog post writing' and 'technical blog posts' form a fairly distinct niche with only minor overlap risk against a general article or technical-writing skill, matching anchor 4 but not the fully-distinct anchor 5.	4 / 5
	Total	13 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: google/adk-samples
Path: python/agents/agent-skills-tutorial/app/skills/blog-writer/SKILL.md
Commit: 629310b

Reviewed: 5 minutes ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.