CtrlK
BlogDocsLog inGet started
Tessl Logo

seo-content-auditor

Analyzes provided content for quality, E-E-A-T signals, and SEO best practices. Scores content and provides improvement recommendations based on established guidelines.

41

Quality

41%

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

The canonical home for this skill is seo-content-auditor 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 is largely a high-level description of what an SEO content audit involves rather than actionable instructions for performing one. It lacks concrete scoring criteria, specific thresholds, executable methodology, and validation steps. The content explains obvious concepts and includes unnecessary sections about what the skill can and cannot do, wasting token budget without adding value.

Suggestions

Replace the vague 'Approach' steps with a concrete scoring rubric that defines what constitutes each score level (e.g., 'Content Depth 8-10: covers all primary subtopics, includes at least 3 supporting data points per section').

Remove the 'What I Can Analyze' and 'What I Cannot Do' sections — Claude already knows its capabilities, and these waste tokens without adding actionable guidance.

Add a concrete worked example showing a sample piece of content being audited with the actual scoring methodology applied, so Claude can replicate the process consistently.

Define specific, measurable criteria for each audit category (e.g., 'Keyword density: flag if primary keyword appears <0.5% or >2.5% of total words; check for semantic variants in at least 3 headings').

DimensionReasoningScore

Conciseness

The skill contains significant unnecessary content: explaining what it can and cannot do (Claude already knows its limitations), generic instructions like 'Clarify goals, constraints, and required inputs,' and the 'Use this skill when' section is tautological. The 'What I Cannot Do' section is particularly wasteful.

2 / 5

Actionability

The skill provides only high-level vague direction ('Evaluate content completeness for topic,' 'Check for E-E-A-T indicators') without any concrete scoring methodology, thresholds, rubrics, or executable steps. The output table is a template but lacks the actual criteria or formulas for arriving at scores.

2 / 5

Workflow Clarity

The 'Approach' section lists 6 steps but they are vague and lack any validation checkpoints, specific criteria for evaluation, or feedback loops. There's no guidance on how to actually score each category, what constitutes a 5 vs 8 in 'Content Depth,' or how to verify the audit is complete and accurate.

2 / 5

Progressive Disclosure

There is a reference to 'resources/implementation-playbook.md' for detailed examples, which suggests some progressive disclosure intent. However, no bundle files are provided to verify this reference works, and the main file contains content that could be better organized or split out (e.g., the scoring rubric details could live in a reference file).

3 / 5

Total

9

/

20

Passed

Description

53%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 a clear domain (SEO content analysis) and mentions some specific concepts like E-E-A-T and scoring, but remains at a moderate level of specificity without enumerating the full range of capabilities. The biggest weakness is the absence of an explicit 'Use when...' clause, which limits Claude's ability to reliably select this skill. Trigger terms are adequate but miss common user phrasings and synonyms.

Suggestions

Add an explicit 'Use when...' clause with trigger phrases like 'Use when the user asks to review content for SEO, evaluate E-E-A-T compliance, audit page content, or optimize for search engines.'

Include natural synonyms and variations such as 'search engine optimization', 'content audit', 'on-page SEO', 'content review', 'ranking factors', and 'search visibility'.

Expand the list of specific capabilities, e.g., 'evaluates keyword usage, readability, meta descriptions, heading structure, internal linking, and topical authority signals'.

DimensionReasoningScore

Specificity

Names the domain (content analysis/SEO) and mentions a few concrete actions (scores content, provides improvement recommendations, analyzes for E-E-A-T signals), but doesn't comprehensively list specific capabilities like keyword analysis, readability scoring, meta tag evaluation, etc.

3 / 5

Completeness

Has a clear 'what' (analyzes content for quality, E-E-A-T, SEO; scores and recommends improvements) but lacks an explicit 'when' clause. There is no 'Use when...' guidance to help Claude know when to select this skill over others.

3 / 5

Trigger Term Quality

Includes some relevant keywords like 'E-E-A-T', 'SEO', 'content', and 'quality', but misses many natural user phrases like 'optimize for search', 'search engine optimization', 'content audit', 'ranking', 'on-page SEO', or 'content review'.

3 / 5

Distinctiveness Conflict Risk

The combination of E-E-A-T signals, SEO best practices, and content scoring creates a fairly distinct niche. However, it could overlap with general content writing or editing skills since 'quality' and 'improvement recommendations' are broad terms.

4 / 5

Total

13

/

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.