CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

62%

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-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

50%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 competently organized, honest overview of scope and limits with a useful output template, but its actionability is undercut by missing scoring criteria and a dangling reference to a non-existent playbook file, and the workflow lacks validation checkpoints. Generic boilerplate sections add padding without value.

Suggestions

Fix the dangling reference: either create the referenced file under 'references/implementation-playbook.md' (and update the path in SKILL.md:24) or remove the pointer.

Add concrete scoring criteria or thresholds per category (e.g., what earns a 7 vs a 3 on Content Depth, how keyword usage is judged) so the X/10 scores in the report template are actually executable.

Remove the circular 'Use this skill when' boilerplate and merge the redundant 'Focus Areas' and 'What I Can Analyze' sections to tighten token efficiency.

DimensionReasoningScore

Conciseness

The Focus Areas, What I Can Analyze, What I Cannot Do, Approach, and Output sections are lean and free of concept over-explanation, but the circular 'Use this skill when working on seo content auditor tasks' boilerplate, the generic 'Clarify goals, constraints, and required inputs' instructions, and the heavy overlap between 'Focus Areas' and 'What I Can Analyze' add unnecessary tokens. This fits 'mostly efficient but includes some unnecessary explanation or could be tightened' rather than the 'efficient; minor instances' of a 4.

3 / 5

Actionability

The Output section provides a concrete report-table template ('Content Audit Report' with Category/Score/Issues/Recommendations columns) and a deliverables list, but there is no concrete scoring criteria, rubric, or thresholds for any category, and the sole pointer to detailed guidance — 'open `resources/implementation-playbook.md`' — references a file that does not exist in the bundle. This matches 'some concrete guidance but incomplete; missing key details' rather than the mostly-executable level of a 4.

3 / 5

Workflow Clarity

The Approach section lists a clear 6-step sequence (evaluate completeness, check E-E-A-T, analyze keywords, assess readability, identify missing trust signals, suggest improvements), but there are no validation checkpoints, verification steps, or feedback loops — the audit workflow has no guidance on how to verify or iterate on findings. This fits 'steps listed but validation gaps; checkpoints missing or implicit'; the destructive/batch cap does not apply since this is a read-only analysis skill.

3 / 5

Progressive Disclosure

The body is well-sectioned (Focus Areas, capabilities/limits, Approach, Output) and short enough that good organization alone could score highly, but it opens 'resources/implementation-playbook.md' (SKILL.md:24) — a file that does not exist in the bundle, using a nonstandard directory name instead of 'references/'. The reference is clearly signaled but dangling, fitting 'some structure but could be better organized' rather than the 'good structure' of a 4, and better than the 'references buried / content inlined' state of a 2.

3 / 5

Total

12

/

20

Passed

Description

58%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 clearly states what the skill does with domain-specific vocabulary and third-person voice, but it entirely lacks a 'Use when...' trigger clause, capping completeness at 3. Keyword coverage is adequate but misses natural synonyms users would commonly say.

Suggestions

Append an explicit trigger clause, e.g. "Use when the user asks to audit, score, or optimize written content for SEO, E-E-A-T, or content quality."

Add natural synonyms and variations users would say, such as "search engine optimization", "keyword optimization", "optimize my article/page", or "content review".

Consider adding a concrete artifact to the 'what', e.g. "produces a scored audit report with prioritized recommendations" to sharpen specificity.

DimensionReasoningScore

Specificity

"Analyzes provided content for quality, E-E-A-T signals, and SEO best practices. Scores content and provides improvement recommendations" names the domain and several concrete actions in third-person voice, matching the 'lists several specific actions; minor gaps' anchor. Not a 5 because the actions (analyze, score, recommend) are more abstract than fully comprehensive concrete operations, and not a 3 because it goes beyond a bare 1-2-action statement.

4 / 5

Completeness

The description has a clear 'what' (analyzes, scores, and recommends improvements for content) but contains no 'Use when...' clause or any explicit trigger guidance, which per the judging guidelines caps completeness at 3. Not a 4 because 'when' is entirely absent rather than merely weak; not a 2 because the 'what' is clearly stated rather than vague.

3 / 5

Trigger Term Quality

"SEO best practices", "content", "E-E-A-T", and "quality" are relevant natural keywords, but common variations users would say ("search engine optimization", "optimize content", "keyword optimization", "rank") are missing, fitting the 'some relevant keywords but missing common variations or synonyms' anchor. Not a 4 because the term coverage is narrow for the domain; not a 2 because multiple genuinely natural terms are present.

3 / 5

Distinctiveness Conflict Risk

SEO content auditing with E-E-A-T scoring is a fairly distinct niche with domain-specific triggers, matching 'mostly distinct; minor overlap risk with closely related skills' — it could overlap with general writing/editing or marketing copy skills. Not a 5 because 'content quality' and 'best practices' are broad enough to invite some overlap; not a 3 because the E-E-A-T/SEO framing is distinctly identifiable.

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-content-auditor/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.