CtrlK
BlogDocsLog inGet started
Tessl Logo

seo-fundamentals

SEO fundamentals, E-E-A-T, Core Web Vitals, and Google algorithm principles.

53

Quality

61%

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 ./.agents/skills/seo-fundamentals/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%

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-organized reference of SEO best practices with concrete numeric targets, but it functions as a lookup table rather than actionable guidance: no executable workflow or validation steps, and the bundled SEO checker script is never referenced from the body. It is efficient but lacks instruction and discovery.

Suggestions

Reference the bundled script explicitly in the body (e.g., "## Audit a project: run `python scripts/seo_checker.py <path>` to detect missing meta tags, Open Graph tags, and heading-hierarchy issues") to make the bundle discoverable and raise both actionability and progressive disclosure.

Add a short, sequenced optimization workflow with a validation checkpoint (e.g., audit -> fix meta/heading issues -> re-run checker -> confirm zero issues) to address workflow_clarity.

Replace some purely descriptive tables with one or two concrete examples (e.g., a sample title tag / meta description pair at the stated character counts) to lift actionability toward copy-paste-ready guidance.

DimensionReasoningScore

Conciseness

The body is dense reference material organized as tables (Core Web Vitals targets, title-tag character counts, prioritized ranking factors) with no prose padding and no explanation of basic concepts Claude already knows, matching the level-3 "lean and efficient; every token earns its place" anchor. It is not level 2 because there is no unnecessary explanation to tighten.

3 / 3

Actionability

The body supplies concrete numeric targets ("LCP < 2.5s", "Title tag 50-60 chars") but provides no executable code, commands, or step-by-step how-to, and the bundled `seo_checker.py` script is never referenced, matching the level-2 anchor of "some concrete guidance but incomplete; missing key details." It is not level 3 because nothing is copy-paste executable, and not level 1 because the numeric targets are genuinely concrete rather than purely abstract.

2 / 3

Workflow Clarity

There is no multi-step workflow, sequence, or validation checkpoint — the body is a flat reference of principles, which the level-2 anchor ("steps listed but validation gaps; sequence present but checkpoints missing") fits better than level 1 because the sections are clearly organized rather than unclear. It is not level 3 because no validation feedback loop or explicit process sequence exists, and not level 1 because the topical structure is unambiguous.

2 / 3

Progressive Disclosure

The body is well-organized into sections but is fully monolithic with no external references, and the provided bundle file `scripts/seo_checker.py` is never signaled in the body, matching the level-2 anchor "references present but not clearly signaled." It is not level 3 because a real bundle asset is undiscoverable, and not level 1 because the content is well-sectioned rather than a disorganized wall of text.

2 / 3

Total

9

/

12

Passed

Description

57%

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 a clear, distinctive SEO niche and lists relevant subtopics, but it reads as a concept list rather than a statement of concrete actions and lacks an explicit "Use when..." trigger clause. It is solid but does not fully exemplify the strongest descriptions.

Suggestions

Rewrite the description to lead with concrete actions (e.g., "Audits and optimizes web pages for search engines — implements meta tags, improves E-E-A-T, and fixes Core Web Vitals") to reach the specificity level-3 anchor.

Add an explicit "Use when..." clause (e.g., "Use when optimizing pages for search, implementing meta tags, or fixing Core Web Vitals") to raise completeness from 2 to 3.

Include more natural user variations such as "meta tags", "search rankings", and "page speed" to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

The description names the domain and enumerates concrete subtopics ("E-E-A-T, Core Web Vitals, and Google algorithm principles") but lists concepts rather than concrete actions, so it does not reach the level-3 bar of "multiple specific concrete actions." It is not level 1 because it is not vague or abstract like "Helps with documents" — the topics are named explicitly.

2 / 3

Completeness

The description states "what" ("SEO fundamentals, E-E-A-T, Core Web Vitals, and Google algorithm principles") but contains no "Use when..." trigger clause; per the rubric a missing explicit trigger guidance caps completeness at 2. It is not level 1 because the "what" is clearly present, and not level 3 because the "when" is absent rather than explicit.

2 / 3

Trigger Term Quality

"SEO", "Core Web Vitals", and "E-E-A-T" are natural terms a user might say, but common variations such as "meta tags", "search ranking", or "page speed" are missing, matching the level-2 anchor of "some relevant keywords but missing common variations." It is not level 3 due to incomplete coverage and not level 1 because the included terms are natural rather than pure jargon.

2 / 3

Distinctiveness Conflict Risk

"SEO", "E-E-A-T", and "Core Web Vitals" form a clear, narrow niche with triggers unlikely to fire for unrelated skills, matching the level-3 anchor. It is not level 2 because the domain is distinctive rather than broadly overlapping with other skills.

3 / 3

Total

9

/

12

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

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

Warning

Total

14

/

16

Passed

Repository
vudovn/ag-kit
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.