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.

64

Quality

76%

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

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 body is a lean, well-sequenced five-phase methodology with unusually concrete numeric guidance and correct one-level-deep use of its single reference file. It could reach full marks on actionability and workflow clarity with a small example of the expected output and an explicit feedback loop after the Phase 5 quality check.

DimensionReasoningScore

Conciseness

The 36-line body is lean and directive throughout — checklists with specific counts and numbers, no explanations of concepts Claude already knows, and no padding; every token earns its place, matching the anchor 5 example of a tight, competent-assuming skill.

5 / 5

Actionability

Guidance is highly concrete with specific numbers ("3-5 key questions", "1500-2500 words", "1-2%, never forced", "150-160 chars"), and as an instruction-only skill absence of code is not penalized — but there are no examples or templates of outputs, leaving minor gaps versus fully copy-paste-ready guidance.

4 / 5

Workflow Clarity

A clear five-phase sequence with a Phase 5 quality-check checklist serving as a validation checkpoint; it falls short of anchor 5 because the check is terminal with no feedback loop (no "if it fails, fix and re-check" recovery guidance).

4 / 5

Progressive Disclosure

The body is a concise overview and the single bundle file is well signaled — "Read references/seo-guidelines.md for detailed SEO rules using load_skill_resource" — one level deep, matching the actual bundle structure where references/seo-guidelines.md exists (46 lines of SEO rules).

5 / 5

Total

18

/

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 does a solid job stating what the skill does through four concrete, domain-specific actions in third person, but it entirely lacks a "Use when..." trigger clause, which caps completeness and weakens discoverability. Natural keyword coverage is good though a few common synonyms (keyword research, blog post) are absent.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to write or SEO-optimize a blog post, article, or landing page, or requests keyword or competitive research."

Include common user phrasings and synonyms such as "keyword research", "blog post", and "article writing" to improve trigger term coverage.

Tighten the closing claim ("ranks well and provides genuine value to readers") into another concrete capability, such as naming the deliverables produced (SEO briefs, optimized drafts, meta descriptions).

DimensionReasoningScore

Specificity

Lists several concrete actions — "topic research, keyword identification, competitive analysis, and writing SEO-optimized content" — but coverage has minor gaps (no output formats or deliverable types) and "ranks well and provides genuine value to readers" is soft, so it is not the comprehensive anchor 5.

4 / 5

Completeness

The "what" is clearly stated (research methodology plus writing SEO-optimized content), but there is no "Use when..." clause or equivalent trigger guidance; per the judging guidelines a missing when-clause caps completeness at 3.

3 / 5

Trigger Term Quality

Good natural keyword coverage ("content research", "SEO writing", "keyword identification", "competitive analysis") that users would plausibly say, but a few common phrasings are missing ("keyword research", "blog post", "article writing"), fitting between anchors 3 and 4 — noticeably above the midpoint.

4 / 5

Distinctiveness Conflict Risk

The SEO content-writing niche is fairly distinct with specific triggers, though it carries minor overlap risk with general writing or copywriting skills — mostly distinct rather than a clear isolated niche.

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.

Validation — 16 / 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.