CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

seo-authority-builder

Analyzes content for E-E-A-T signals and suggests improvements to build authority and trust. Identifies missing credibility elements. Use for YMYL topics.

Quality

69%

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 ./skills/seo-authority-builder/SKILL.md
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 well-organized and readable but suffers from template filler, restatements of standard SEO knowledge Claude already has, and a lack of executable depth — no scoring criteria, audit methodology, or worked examples. The workflow sequence exists but has no validation checkpoints, and all content lives in one flat file with no progressive disclosure.

Suggestions

Remove the circular "Use this skill when / Do not use this skill when" sections and the generic Instructions bullets; they restate the skill name and add no operational value.

Add concrete methodology: E-E-A-T scoring criteria for the X/10 audit score, a filled-in example author bio template, and specific schema markup examples instead of naming deliverables only.

Move exhaustive checklists (trust signals, authority tactics, platform implementation) into a references file and add a validation step to the Approach (e.g., verifying suggested schema against Google's rich result requirements).

DimensionReasoningScore

Conciseness

The body uses terse bullet lists rather than verbose prose, but includes unnecessary content: circular filler ("Working on seo authority builder tasks or workflows", "The task is unrelated to seo authority builder"), generic instructions ("Clarify goals, constraints, and required inputs"), and enumerations of knowledge Claude already has ("Contact information", "Privacy policy/terms", "SSL certificates" as trust signals). Mostly efficient but with several sections that could be trimmed or cut, fitting the 3 anchor better than the noticeably padded 2.

3 / 5

Actionability

The output template ("Current Score: X/10... Implement Organization schema") and named deliverables provide some concrete guidance, but there is no E-E-A-T scoring methodology, no audit checklist specifics, and no example author bio — the Approach steps are abstract one-liners like "Assess topical coverage depth". Some concrete guidance with key details missing matches the 3 anchor; it falls short of 4 because most guidance is category enumeration rather than executable steps.

3 / 5

Workflow Clarity

The 7-step Approach provides a coherent, ordered sequence (analyze → identify → suggest → assess → propose → recommend), but no validation checkpoints exist and the steps are generically defined ("Suggest author credential additions" gives no how). This matches the 3 anchor — sequence present but checkpoints missing — rather than 4, which requires most checkpoints present; it is above 2 because the sequence is complete and sensible rather than rough.

3 / 5

Progressive Disclosure

The body has clear section headers and is scannable, but it is a flat, single-altitude file with no overview-to-detail split: everything from trust-signal checklists to platform implementation tactics is inlined, and there are no reference files or navigation. At ~125 lines it exceeds the under-50-line simple-skill exception, so the some-structure-could-be-better-organized 3 anchor fits better than 4.

3 / 5

Total

12

/

20

Passed

Description

75%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.

A solid description that clearly states three concrete capabilities and includes an explicit "Use for YMYL topics" trigger in third person. Its main weakness is the thin when-clause — a single trigger phrase with no synonyms or variations — which limits both completeness and trigger discoverability.

Suggestions

Expand the trigger clause to cover variations: e.g., "Use for YMYL topics or when the user mentions E-E-A-T, author credentials, trust signals, or building topical authority."

Surface more of the skill's actual capabilities in the description, such as schema markup recommendations and topical authority mapping, to improve coverage and distinctiveness.

DimensionReasoningScore

Specificity

The description lists several concrete actions — "Analyzes content for E-E-A-T signals", "suggests improvements to build authority and trust", "Identifies missing credibility elements" — with only minor gaps in coverage (no mention of schema markup, author bios, or topical authority). It exceeds the 1-2 concrete actions of the midpoint anchor but is not comprehensive enough for a 5.

4 / 5

Completeness

Both what ("Analyzes content for E-E-A-T signals and suggests improvements... Identifies missing credibility elements") and when ("Use for YMYL topics") are explicitly present in third person. The when-clause is a single terse trigger with no variations, so it could be more explicit and specific, matching the 4 anchor rather than the concrete multi-phrase trigger coverage of a 5.

4 / 5

Trigger Term Quality

It includes good natural keywords an SEO user would say — "E-E-A-T signals", "authority and trust", "credibility", "YMYL topics" — but misses common variations like "expertise", "author credentials", and "trust signals". Coverage is good with a few natural terms missing, matching the 4 anchor rather than the comprehensive synonym coverage of a 5.

4 / 5

Distinctiveness Conflict Risk

The E-E-A-T/YMYL terminology carves out a clear niche with distinct triggers, but the broad "analyzes content"/"suggests improvements" pattern creates minor overlap risk with general SEO or content-audit skills. Mostly distinct with minor overlap risk from closely related skills — a 4, not a 5.

4 / 5

Total

16

/

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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

rmyndharis/antigravity-skills

Path

skills/seo-authority-builder/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.