seo-fundamentals
SEO fundamentals, E-E-A-T, Core Web Vitals, and Google algorithm principles.
Install with Tessl CLI
npx tessl i github:lchenrique/politron-ide --skill seo-fundamentalsOverall
score
61%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
33%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 domain (SEO) with some specific technical concepts but fails to describe what actions Claude performs or when this skill should be selected. It reads more like a topic list than a functional skill description, lacking both actionable verbs and explicit trigger guidance.
Suggestions
Add concrete actions describing what Claude does with this knowledge (e.g., 'Analyzes pages for SEO compliance', 'Provides E-E-A-T optimization recommendations', 'Audits Core Web Vitals issues').
Add a 'Use when...' clause with trigger terms like 'SEO audit', 'search rankings', 'page optimization', 'Google ranking', 'search engine optimization'.
Include common natural language variations users might say, such as 'improve search rankings', 'optimize for Google', or 'website performance'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (SEO) and lists specific concepts (E-E-A-T, Core Web Vitals, Google algorithm principles), but doesn't describe concrete actions Claude would perform with these concepts. | 2 / 3 |
Completeness | Only partially answers 'what' (lists topics but not actions) and completely lacks a 'when' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes relevant technical terms like 'SEO', 'E-E-A-T', 'Core Web Vitals' that knowledgeable users might say, but misses common natural variations like 'search engine optimization', 'page speed', 'ranking', 'search rankings', or 'Google search'. | 2 / 3 |
Distinctiveness Conflict Risk | The SEO domain is reasonably specific, and terms like 'E-E-A-T' and 'Core Web Vitals' are distinctive, but without clear action verbs or use cases, it could overlap with general web development or content writing skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
65%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an excellent quick-reference guide that efficiently presents SEO fundamentals in a scannable table format. However, it functions more as a reference card than an actionable skill - it tells Claude what matters but not how to implement or verify SEO improvements. The lack of executable examples, implementation workflows, and validation steps limits its practical utility for hands-on SEO tasks.
Suggestions
Add executable code examples for common tasks like generating schema markup JSON-LD, checking meta tag lengths, or validating robots.txt
Include a step-by-step workflow for conducting an SEO audit with validation checkpoints (e.g., 1. Check indexing status → 2. Audit Core Web Vitals → 3. Review content gaps)
Add concrete implementation examples showing before/after for title tags, meta descriptions, and schema markup rather than just best practice guidelines
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient use of tables to convey information. No unnecessary explanations of basic concepts - assumes Claude understands SEO terminology and jumps straight to actionable reference data. | 3 / 3 |
Actionability | Provides specific targets (LCP < 2.5s, title 50-60 chars) and clear do/don't guidance, but lacks executable code examples for implementing schema markup, checking Core Web Vitals programmatically, or concrete implementation steps. | 2 / 3 |
Workflow Clarity | Content is organized logically by topic but lacks sequential workflows for SEO implementation. No step-by-step process for auditing a site, implementing fixes, or validation checkpoints to verify SEO improvements. | 2 / 3 |
Progressive Disclosure | Well-structured with clear sections and tables, but everything is in one file with no references to deeper documentation for complex topics like schema markup implementation or technical SEO audits that would benefit from separate detailed guides. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
91%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
Total | 10 / 11 Passed | |
- 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.