CtrlK
BlogDocsLog inGet started
Tessl Logo

seo-content-writer

Writes SEO-optimized content based on provided keywords and topic briefs. Creates engaging, comprehensive content following best practices. Use PROACTIVELY for content creation tasks.

39

Quality

38%

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 ./plugins/antigravity-bundle-seo-specialist/skills/seo-content-writer/SKILL.md

The canonical home for this skill is seo-content-writer in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

35%Scale 1-5

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

This skill reads as a generic SEO content writing checklist that mostly restates common knowledge Claude already possesses. It lacks concrete examples, executable templates, or specific demonstrations of keyword integration. The workflow is present but shallow, with no validation or quality verification steps despite the output involving content that should be checked against stated quality standards.

Suggestions

Add a concrete, worked example showing a topic brief input and the expected output (article excerpt, meta description, title variations) so Claude has a clear template to follow.

Remove or drastically condense the Focus Areas and E-E-A-T Elements sections, as these are standard SEO knowledge Claude already has—instead, focus on project-specific conventions or non-obvious patterns.

Add validation checkpoints to the workflow, such as 'Verify keyword density is 0.5-1.5% before finalizing' and 'Check reading level with a specific method/tool' to make quality standards actionable rather than aspirational.

Either provide the referenced `resources/implementation-playbook.md` bundle file or remove the reference and inline the most critical examples directly.

DimensionReasoningScore

Conciseness

The skill is noticeably verbose with many bullet-point lists that state obvious SEO concepts Claude already knows (e.g., 'write for humans while optimizing for search engines,' 'original, valuable content'). The generic preamble about when to use/not use the skill adds no value. Much of this is padding rather than novel instruction.

2 / 5

Actionability

The content provides high-level checklists and abstract guidance ('Analyze topic and target keywords,' 'Include supporting examples') but lacks any concrete, executable examples—no sample content, no specific keyword integration demonstrations, no template with actual text. It describes what to do without showing how.

2 / 5

Workflow Clarity

There is a numbered 7-step approach and a structured content creation framework (Introduction → Body → Conclusion), providing a rough sequence. However, there are no validation checkpoints, no feedback loops for quality checking, and no explicit verification steps for the output quality standards listed.

3 / 5

Progressive Disclosure

The skill references `resources/implementation-playbook.md` for detailed examples, which is a good signal for progressive disclosure. However, no bundle files exist to support this reference, and the main file inlines a lot of checklist content that could be better organized into separate reference files. The structure is adequate but not well-executed.

3 / 5

Total

10

/

20

Passed

Description

41%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 identifies its domain (SEO content writing) but lacks concrete specifics about what types of content it produces and what distinguishes it from general writing skills. The 'when' guidance is too broad ('content creation tasks') and the use of 'PROACTIVELY' adds no meaningful selection criteria. The description would benefit significantly from listing specific content types and more precise trigger conditions.

Suggestions

List specific content types produced, e.g., 'Writes SEO-optimized blog posts, landing pages, meta descriptions, and product descriptions based on provided keywords and topic briefs.'

Replace the vague 'Use PROACTIVELY for content creation tasks' with specific triggers like 'Use when the user asks for SEO content, blog articles, keyword-optimized copy, or mentions search rankings and organic traffic.'

Add natural synonyms and related terms users might say, such as 'search engine optimization', 'blog post', 'article writing', 'keyword research', 'ranking', or 'organic search'.

DimensionReasoningScore

Specificity

Names the domain (SEO-optimized content) but the actions are generic — 'writes content' and 'creates content' are essentially the same vague action repeated. No concrete specifics like 'writes blog posts, meta descriptions, landing page copy' are provided.

2 / 5

Completeness

The 'what' is present but vague (writes SEO content). The 'when' clause says 'Use PROACTIVELY for content creation tasks' which is extremely broad and not a concrete trigger — it doesn't specify what signals or user requests should activate this skill.

3 / 5

Trigger Term Quality

Includes some relevant keywords like 'SEO-optimized', 'keywords', 'topic briefs', and 'content creation', but misses many natural user phrases such as 'blog post', 'article', 'meta description', 'search engine optimization', 'ranking', or 'copywriting'.

3 / 5

Distinctiveness Conflict Risk

'Content creation tasks' is extremely broad and would overlap with any writing, copywriting, or content-related skill. The SEO angle provides some distinction, but 'content creation' as a trigger would conflict with many other skills.

2 / 5

Total

10

/

20

Passed

Validation

90%

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

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
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.