CtrlK
BlogDocsLog inGet started
Tessl Logo

content-research-writer

Content research and SEO writing methodology. Guides the agent through topic research, keyword identification, competitive analysis, and writing SEO-optimized content that ranks well and provides genuine value to readers.

63

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./python/agents/agent-skills-tutorial/app/skills/content-research-writer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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 body is a concise, well-structured, instruction-only methodology with clear phase sequencing and a working quality-check validation step, plus one properly signaled reference file. It is strong overall, with room only for sharper intermediate checkpoints and tighter deduplication against the SEO reference.

DimensionReasoningScore

Conciseness

The body is lean and efficient — short numbered lists and bullets, no concept padding, and no over-explanation of SEO basics, assuming Claude's competence throughout.

5 / 5

Actionability

Provides concrete, specific guidance ('1500-2500 words for tutorials', 'at least 2-3 code examples per tutorial', 'Meta description draft (150-160 chars)') with only minor gaps such as 'competitive analysis' being named but not detailed in Phase 1.

4 / 5

Workflow Clarity

Five clearly sequenced phases with a terminal Quality Check serving as a validation checkpoint; no destructive/batch cap applies, but intermediate checkpoints are implicit rather than explicit.

4 / 5

Progressive Disclosure

A single well-signaled one-level reference ('Read references/seo-guidelines.md ... using load_skill_resource') that resolves to a real file, with only minor overlap between the inlined Phase 3 bullets and the reference file.

4 / 5

Total

17

/

20

Passed

Description

66%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 concrete actions with good natural keywords, but lacks an explicit 'when to use' trigger clause, which limits its completeness. Overall it is specific and distinctive but would benefit from explicit usage triggers.

Suggestions

Add a 'Use when...' clause specifying natural trigger phrases (e.g., 'Use when writing blog posts, articles, or any SEO-optimized content, or when the user asks for keyword research or content that ranks on Google').

Include natural user variations like 'blog post', 'article', and 'rank on Google' alongside the existing keyword set.

Drop the benefit-style trailing claim ('ranks well and provides genuine value to readers') in favor of more concrete actions to push specificity toward 5.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions ('topic research, keyword identification, competitive analysis, and writing SEO-optimized content'), but the trailing benefit phrasing ('ranks well and provides genuine value') keeps it just short of fully comprehensive.

4 / 5

Completeness

Clearly states what the skill does, but offers no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric.

3 / 5

Trigger Term Quality

Good natural-term coverage ('content research', 'SEO writing', 'keyword', 'SEO-optimized content'), but misses common variations users actually say like 'blog post', 'article', or 'rank on Google'.

4 / 5

Distinctiveness Conflict Risk

Targets a clear content/SEO-writing niche distinct from document or code skills, with only minor overlap risk against general writing assistance.

4 / 5

Total

15

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
google/adk-samples
Reviewed

Table of Contents

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.