CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

seo-structure-architect

Analyzes and optimizes content structure including header hierarchy, suggests schema markup, and internal linking opportunities. Creates search-friendly content organization. Use for content structuring.

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-structure-architect/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

53%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 reasonably lean, covering the skill's focus areas with a few genuinely concrete artifacts (blueprint tree, schema priority list, deliverables). It is held back by generic boilerplate sections, restated common-knowledge SEO basics, high-level workflow steps without checkpoints, and the absence of worked examples for its key promised outputs.

Suggestions

Remove the boilerplate "Instructions" and "Use/Do not use this skill when" sections and trim well-known basics (e.g. "One H1 per page", "Maintain logical hierarchy") to only non-obvious guidance, freeing tokens for real value.

Add a short worked example of a key deliverable — e.g. a JSON-LD snippet for FAQ or Article schema, or a small internal linking matrix — so the guidance is copy-paste ready rather than descriptive.

Make the Approach steps concrete by specifying what each step produces (e.g. "Evaluate header hierarchy: flag skipped levels, multiple H1s, and keyword-stuffed headings") and include a verification step for the final blueprint.

DimensionReasoningScore

Conciseness

The core sections (Focus Areas, Siloing Strategy, Schema Markup Priority, Output) are lean lists, but the Instructions section is pure boilerplate ("Clarify goals, constraints, and required inputs. Apply relevant best practices and validate outcomes.") and Header Tag Best Practices restates knowledge Claude already has ("One H1 per page matching main topic", "Maintain logical hierarchy"). Mostly efficient with some unnecessary content that could be trimmed, matching anchor 3.

3 / 5

Actionability

There are concrete elements — the Structure Blueprint ASCII tree, a named list of high-impact schema types, and a deliverables list — but no worked example of the promised "Schema markup JSON-LD code" or "Internal linking matrix", and Approach steps like "Assess content organization" remain high-level. Some concrete guidance but incomplete, matching anchor 3 rather than the mostly-executable anchor 4.

3 / 5

Workflow Clarity

The Approach section provides a coherent 7-step sequence (analyze → evaluate → identify → suggest → recommend → assess → format), but the steps are generic verbs with no checkpoints, and validation is only implicit via the boilerplate "validate outcomes". As an advisory (non-destructive, non-batch) skill no cap applies, but it sits at anchor 3's "steps listed but validation gaps; checkpoints missing or implicit" rather than anchor 4's mostly-present checkpoints.

3 / 5

Progressive Disclosure

No bundle files exist and the body references none; the skill is a single self-contained, well-sectioned file (Use when / Focus Areas / Siloing / Schema / Approach / Output), so navigation is easy and nothing is buried. It is above anchor 3 (structure is good, no content misplaced inline) but not anchor 5 — at ~98 lines with some boilerplate sections adding noise and slightly uneven organization, minor gaps remain.

4 / 5

Total

13

/

20

Passed

Description

71%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 communicates what the skill does with several concrete, domain-specific actions, and it includes an explicit use-when clause. Its main weaknesses are the generic "Use for content structuring" trigger, the absence of the most natural trigger term "SEO", and the resulting overlap risk with general content-organization skills.

Suggestions

Expand the when-clause with concrete triggers, e.g. "Use when the user mentions SEO, heading or header tag structure (H1-H6), schema markup, internal linking, or content silos."

Add the term "SEO" and natural variations ("heading tags", "H1/H2", "table of contents", "content outline") so the description matches the phrases users actually say.

Sharpen the trigger to scope it to search-optimization contexts (e.g. "for SEO content structure") to reduce conflict with general content-writing or information-architecture skills.

DimensionReasoningScore

Specificity

Quotes: "Analyzes and optimizes content structure including header hierarchy, suggests schema markup, and internal linking opportunities" — several concrete actions are named (header hierarchy analysis, schema markup suggestions, internal linking). It lists several specific actions with minor gaps in coverage (e.g., table of contents structure and siloing covered by the skill are not mentioned), which matches the anchor 4 example style rather than the comprehensive coverage of anchor 5.

4 / 5

Completeness

Both parts are present: a clear "what" ("Analyzes and optimizes content structure... suggests schema markup, and internal linking opportunities") and an explicit when-clause ("Use for content structuring"). It is not anchor 5 because the when-clause is a thin generic phrase rather than concrete trigger phrases (e.g., "when the user mentions SEO, heading structure, or schema markup"), matching anchor 4's "'when' could be more explicit or specific".

4 / 5

Trigger Term Quality

Quotes: "header hierarchy", "schema markup", "internal linking", "content structuring" — these are natural phrases users would say. Good keyword coverage, but a few natural terms are missing, most notably "SEO" itself (the domain's most common trigger word) plus variations like "headings", "H1 tags", or "table of contents", placing it at anchor 4 rather than the comprehensive synonym coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

The capability description is niche, but the trigger "Use for content structuring" is broad and would fire on general content-organization, writing, or information-architecture tasks outside this skill's SEO scope. It is somewhat specific but could still overlap with similar skills (content strategy, general SEO, technical-writing skills), fitting anchor 3 better than anchor 4's "minor overlap risk".

3 / 5

Total

15

/

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-structure-architect/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.