CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

48%

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/AI-Agents-Safe-Coding-Skills-claude/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

11%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 well-formatted but generic SEO concept primer that restates widely known knowledge, provides no executable guidance, and completely fails to surface the bundled seo_checker.py script — the one asset that would have made the skill actionable. It reads as educational reference material rather than a skill that instructs Claude to do anything.

Suggestions

Replace the concept-primer tables with actionable guidance, and reference the bundled audit tool explicitly (e.g. 'Run `python scripts/seo_checker.py <project_path>` to audit pages for meta tags, Open Graph, heading hierarchy, and alt attributes').

Cut or drastically compress sections that restate knowledge Claude already has (E-E-A-T definitions, CWV thresholds, robots.txt/sitemap purposes) and keep only genuinely non-obvious judgment calls (e.g. the relative-importance table).

Define at least one concrete workflow (audit -> interpret findings -> prioritize fixes) with validation checkpoints so the content instructs rather than describes.

DimensionReasoningScore

Conciseness

Nearly the entire body restates knowledge Claude already has — E-E-A-T dimensions, CWV thresholds ("LCP < 2.5s", "INP < 200ms", "CLS < 0.1"), the purpose of robots.txt/sitemaps/canonical tags, and title tag best practices — matching anchor 2 ('noticeably verbose; several unnecessary explanations'). It avoids anchor 1 only because the table format is compact rather than padded prose, but it is not a 3+ since almost no token adds information Claude lacks.

2 / 5

Actionability

The body contains no code, commands, or concrete instructions — it only describes concepts ('Title tag: Clear topic + intent', 'Technical SEO ensures pages are accessible'). This matches anchor 1 ('entirely vague or abstract; no concrete code or commands; only describes rather than instructs'), made worse by the fact that an executable script (scripts/seo_checker.py) exists in the bundle yet is never invoked or shown.

1 / 5

Workflow Clarity

There is no multi-step process, sequence, or task flow anywhere in the body — it is a topical concept reference, matching anchor 1 ('steps missing or incoherent; no sequence'). The simple-skill exception does not apply because no single unambiguous action is defined either; the body never tells Claude what to do with these principles.

1 / 5

Progressive Disclosure

The bundle contains scripts/seo_checker.py (a 219-line executable SEO audit tool), but the body never mentions or links to it — the skill's only executable asset is undiscoverable, matching anchor 2 ('minimal structure; references are buried'). It is not a 3 because no reference to the script is 'present but weakly signaled'; it is entirely absent, despite the body being well-sectioned otherwise.

2 / 5

Total

6

/

20

Passed

Description

61%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 names a distinct niche and covers relevant SEO terminology well, but it is topic-list rather than capability-list: it says what the skill contains, not what it does or when to use it. A 'Use when...' clause and action verbs would lift it substantially.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks about SEO, search rankings, page optimization, or Core Web Vitals.'

State concrete capabilities/actions (e.g. 'Apply these principles when auditing or improving a page's search visibility') instead of only listing topic areas.

Include common synonyms such as 'search engine optimization', 'rankings', or 'SERP' to broaden natural trigger coverage.

DimensionReasoningScore

Specificity

The description "Core principles of SEO including E-E-A-T, Core Web Vitals, technical foundations, content quality, and how modern search engines evaluate pages" names the domain and enumerates several specific topic areas, but states no concrete actions or capabilities (no verbs like 'audits', 'checks', 'optimizes'). It matches anchor 3 (names domain with some specificity but not comprehensive as actions); it is above anchor 2 because the topic coverage is concrete rather than generic, but below anchor 4 because nothing describes what the skill actually does.

3 / 5

Completeness

The 'what' is clear (core principles of SEO covering E-E-A-T, Core Web Vitals, technical foundations, content quality, and how search engines evaluate pages), but there is no 'Use when...' clause or equivalent trigger guidance. Per the judging guidelines, a missing 'Use when...' clause caps completeness at 3, which this description sits at exactly: clear 'what', 'when' absent.

3 / 5

Trigger Term Quality

Natural trigger terms are present: "SEO" (the term users actually say), "E-E-A-T", "Core Web Vitals", and "search engines". It falls between anchor 3 (missing common variations) and anchor 5 (comprehensive with synonyms); a few natural terms are missing — the spelled-out "search engine optimization", "ranking", "SERP", or "Google" — matching anchor 4's 'good keyword coverage; a few natural terms missing'.

4 / 5

Distinctiveness Conflict Risk

SEO is a clear niche with distinct terminology (E-E-A-T, Core Web Vitals), so overlap risk with unrelated skills is low — matching anchor 4 ('mostly distinct; minor overlap risk with closely related skills'). It is not a 5 because without explicit trigger phrases it could collide with closely related skills such as an SEO auditing or page-speed tooling skill.

4 / 5

Total

14

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

plugins/AI-Agents-Safe-Coding-Skills-claude/skills/seo-fundamentals/SKILL.md

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.