seo-structure-architect

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

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/seo-structure-architect/SKILL.md

Quality

Content

72%Weight 40%Scale 1-3

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 actionable, with concrete templates and named schemas, but it carries generic boilerplate sections and a workflow whose steps are abstract verbs without verification checkpoints. Tightening the filler and making the Approach steps concrete would raise the weaker dimensions.

Suggestions

Remove or specialize the generic 'Use this skill when / Do not use this skill when' boilerplate that merely restates the skill name.

Replace abstract Approach verbs with concrete, verifiable steps (e.g., 'Verify exactly one H1 exists; flag any H-rank jumps greater than one level').

Add a short validation/checklist step so the analyst confirms hierarchy consistency and schema validity before delivering the blueprint.

Dimension	Reasoning	Score
Conciseness	The core sections are lean and assume Claude's competence, but the boilerplate 'Use this skill when / Do not use this skill when' sections restate the skill name generically and add little, so it is mostly efficient with some filler that could be tightened.	2 / 3
Actionability	Provides concrete, specific guidance — an H1/H2/H3 blueprint template, named schema types (Article, FAQ, HowTo, BreadcrumbList), platform-specific implementation notes (WordPress TOC/schema plugins, Astro components), and explicit deliverable formats — which is actionable even without executable code.	3 / 3
Workflow Clarity	The 'Approach' section gives a 7-step sequence, but the steps are generic verbs ('Analyze', 'Evaluate', 'Identify', 'Assess') with no verification or quality checkpoints, so the sequence is present but lacks the explicit checkpoints needed for a 3.	2 / 3
Progressive Disclosure	It is a self-contained, well-sectioned single file with no nested or multi-level references, and no bundle files exist to verify; per the simple-skills note, well-organized sections with no external references warrant a 3.	3 / 3
	Total	10 / 12 Passed

Description

60%Weight 40%Scale 1-3

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 states concrete capabilities clearly but its trigger guidance is generic ('Use PROACTIVELY for content structuring'), weakening completeness, trigger quality, and distinctiveness. Adding natural user phrasings like 'SEO', 'content structure', or 'improve search visibility' would lift all three.

Suggestions

Replace 'Use PROACTIVELY for content structuring' with natural triggers a user would actually say, e.g. 'Use when the user asks to improve SEO, optimize content structure, fix header hierarchy, or add schema markup/internal links.'

Add common keyword variations ('SEO', 'search-friendly', 'content organization') so the skill surfaces for typical user requests.

Sharpen the when-clause to distinguish this from general writing/editing skills by tying it specifically to structural SEO work.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Analyzes and optimizes content structure including header hierarchy, suggests schema markup, and internal linking opportunities' — matching the multi-action anchor rather than the single-domain anchor at 2.	3 / 3
Completeness	The 'what' is clearly stated and a 'when' clause exists, but 'Use PROACTIVELY for content structuring' is a weak generic trigger rather than the explicit natural-trigger phrasing required for a 3.	2 / 3
Trigger Term Quality	Relevant terms appear ('header hierarchy', 'schema markup', 'internal linking') but the trigger 'Use PROACTIVELY for content structuring' is generic and omits common user phrasings like 'SEO' or 'improve rankings', so it sits at the 'some relevant keywords, missing common variations' level.	2 / 3
Distinctiveness Conflict Risk	The capability set carves a SEO-content niche, but the generic 'content structuring' trigger could still overlap with general content/writing skills, matching the 'somewhat specific but could overlap' anchor.	2 / 3
	Total	9 / 12 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: rmyndharis/antigravity-skills
Path: skills/seo-structure-architect/SKILL.md
Commit: e63f7dd

Reviewed: 13 days ago

Table of Contents

Discovery Implementation Validation

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.