CtrlK
BlogDocsLog inGet started
Tessl Logo

seo-fundamentals

Core principles of SEO including E-E-A-T, Core Web Vitals, technical foundations, content quality, and how modern search engines evaluate pages.

37

Quality

35%

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-fundamentals/SKILL.md

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

SKILL.md
Quality
Evals
Security

Quality

Content

28%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 conceptual overview or study guide for SEO fundamentals rather than an actionable skill for Claude. It explains concepts Claude already knows well without providing any concrete implementation guidance, executable code, or step-by-step workflows. The table-based organization is clean but the content lacks the actionability and specificity needed to be a useful skill.

Suggestions

Add concrete, executable examples: show actual HTML for structured data markup, example robots.txt configurations, canonical tag implementations, and meta tag patterns rather than just listing what they are.

Define a clear workflow: when Claude is asked to optimize a page for SEO, what specific steps should it follow in what order? Include validation checkpoints (e.g., validate schema markup with a testing tool).

Remove or drastically condense sections that explain concepts Claude already knows (E-E-A-T definitions, what Core Web Vitals are, what structured data types exist) and focus on project-specific conventions or non-obvious implementation details.

Replace the placeholder 'When to Use' section with specific trigger conditions (e.g., 'Use when reviewing HTML templates for SEO compliance' or 'Use when generating structured data for a new page type').

DimensionReasoningScore

Conciseness

The content is mostly efficient in its table-based format, but it explains many concepts Claude already knows well (what E-E-A-T stands for, what Core Web Vitals are, what structured data types exist). Much of this is general SEO knowledge that doesn't add novel, actionable value beyond what Claude already has in its training data.

3 / 5

Actionability

The content is entirely descriptive and conceptual — it explains what SEO factors are but provides zero concrete code, commands, specific implementation steps, or executable guidance. There are no examples of how to implement canonical tags, generate sitemaps, add structured data markup, or measure CWV. It reads as a reference document, not an actionable skill.

1 / 5

Workflow Clarity

There is no workflow or sequenced process. The content is organized as a reference taxonomy of SEO concepts with tables, but lacks any step-by-step process for Claude to follow when performing SEO-related tasks. The 'When to Use' section is a generic placeholder that adds no clarity.

2 / 5

Progressive Disclosure

The content is reasonably well-structured with numbered sections and tables, making it navigable. However, there are no references to external files for deeper dives, and some sections (like structured data types or technical SEO elements) could benefit from being split out. For a standalone skill with no bundle, the internal organization is decent but the content is long enough that external references would improve it.

3 / 5

Total

9

/

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 the SEO domain and lists relevant subtopics but reads more like a course syllabus than a skill description. It lacks concrete action verbs describing what the skill does and entirely omits 'when' guidance, making it difficult for Claude to know when to select this skill over others. The passive, noun-heavy phrasing weakens both specificity and completeness.

Suggestions

Add concrete action verbs describing what the skill does, e.g., 'Analyzes pages for SEO compliance, audits Core Web Vitals, evaluates E-E-A-T signals, and recommends technical improvements.'

Add an explicit 'Use when...' clause with natural trigger phrases, e.g., 'Use when the user asks about search engine optimization, improving search rankings, Google page ranking, SEO audits, or page performance.'

Include common synonyms and natural user phrases such as 'search ranking', 'Google optimization', 'SEO audit', 'page speed', and 'meta tags' to improve trigger term coverage.

DimensionReasoningScore

Specificity

Names the domain (SEO) and lists several concepts (E-E-A-T, Core Web Vitals, technical foundations, content quality), but these are topic areas rather than concrete actions. No verbs describe what the skill actually does—it reads more like a table of contents than a capability list.

3 / 5

Completeness

Provides a vague 'what' (core principles of SEO including several subtopics) but completely lacks any 'when' clause or trigger guidance. There is no 'Use when...' or equivalent, which per the rubric should cap completeness at 3, and the 'what' itself is more of a topic listing than a clear capability statement, placing it at 2.

2 / 5

Trigger Term Quality

Includes relevant SEO-specific terms like 'E-E-A-T', 'Core Web Vitals', and 'content quality' that knowledgeable users might mention. However, it misses common natural phrases users would say such as 'search ranking', 'Google optimization', 'page speed', 'meta tags', 'keywords', or 'search engine optimization'.

3 / 5

Distinctiveness Conflict Risk

The SEO domain is somewhat specific, and terms like 'E-E-A-T' and 'Core Web Vitals' help narrow the scope. However, the broad framing ('core principles', 'technical foundations', 'content quality') could overlap with general web development, content writing, or performance optimization skills.

3 / 5

Total

11

/

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.