CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

58

Quality

68%

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

61%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 content is well-structured and reasonably actionable with concrete SEO specifics, but it is held back by generic boilerplate sections and a workflow that lacks validation checkpoints. Tightening the filler and adding a verification step would meaningfully raise the score.

Suggestions

Replace the generic 'Use this skill when'/'Do not use this skill when'/'Instructions' boilerplate with skill-specific triggers and steps to improve conciseness.

Add a JSON-LD schema markup code example to back the 'Schema markup JSON-LD code' deliverable and raise actionability.

Insert a validation/review checkpoint into the 'Approach' workflow (e.g., verify header hierarchy is logical and schema validates before delivering) to lift workflow clarity above 3.

DimensionReasoningScore

Conciseness

Core sections (header best practices, siloing, schema priority, output) are efficient, but the 'Use this skill when' and 'Instructions' sections are generic boilerplate ('Working on seo structure architect tasks or workflows', 'Clarify goals, constraints, and required inputs') that could be trimmed.

3 / 5

Actionability

Concrete, actionable guidance including named schema types (Article/BlogPosting, FAQ, HowTo, BreadcrumbList), explicit header rules (one H1, H2s for sections), and an output blueprint template; a JSON-LD example for the schema-deliverable would close the gap to anchor 5.

4 / 5

Workflow Clarity

The 'Approach' section provides a clear 7-step sequence but includes no validation checkpoints or feedback loops; this is a non-destructive analysis skill so the destructive-cap does not apply, yet the missing checkpoints match anchor 3.

3 / 5

Progressive Disclosure

The body is well-organized into clearly headed sections (Focus Areas, Header Tag Best Practices, Siloing Strategy, Schema Markup Priority, Approach, Output) and is self-contained with no references needed; at ~100 lines it exceeds the simple-skill threshold that would permit a 5.

4 / 5

Total

14

/

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.

The description is specific, well-triggered, and complete with both what and when guidance, sitting solidly above the midpoint. Its main weakness is a generic 'Use PROACTIVELY for content structuring' when-clause that lacks concrete trigger phrases.

DimensionReasoningScore

Specificity

Lists several concrete actions ('analyzes and optimizes content structure including header hierarchy, suggests schema markup, and internal linking opportunities') but the verbs are slightly more abstract than anchor 5's fully concrete actions like 'extract/fill/merge'.

4 / 5

Completeness

Has both a clear 'what' (analyze/optimize structure, suggest schema, internal linking) and a 'when' ('Use PROACTIVELY for content structuring'), but the when-clause is generic rather than listing concrete trigger phrases, matching anchor 4.

4 / 5

Trigger Term Quality

Good coverage of natural SEO terms ('header hierarchy', 'schema markup', 'internal linking', 'content structuring') that users would say, though synonyms like 'structured data', 'JSON-LD', or 'H1 tags' are missing.

4 / 5

Distinctiveness Conflict Risk

The SEO content-architecture niche (header hierarchy, schema markup, internal linking) is mostly distinct, with only minor overlap risk from the broad 'content structuring' trigger.

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