write-seo-geo-content

Writes product-led content pages optimized for both search engines and AI engine citations. Produces markdown files with frontmatter, following page-type frameworks (comparison, guide, use case, learn, trust) with verified sources and no fabricated data.

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./write-seo-geo-content/SKILL.md

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A strong, highly actionable instruction skill with excellent workflow gating and concrete specs, slightly weakened by a monolithic single-file structure and redundancy between the detailed sections and the Verification Checklist. Splitting long reference material into bundled files and de-duplicating the checklist would raise the conciseness and progressive-disclosure scores.

Suggestions

Move the detailed Page-Type Frameworks, Core Content Blocks, and frontmatter/SEO standards into reference files (e.g. references/page-frameworks.md, references/seo-standards.md) and keep SKILL.md as a concise overview pointing to them.

De-duplicate the Verification Checklist so it references the source sections instead of restating title-tag, meta, citation, and word-count rules already specified above.

Consolidate the chart/visual guidance (currently spread across Block 4, Block 5, Quality Standards, and the checklist) into one location to reduce repeated content.

Dimension	Reasoning	Score
Conciseness	The body is mostly high-signal with concrete word counts and field tables and no padded concept explanations, but the Verification Checklist repeats SEO Standards, block specs, and GEO Checklist content, and chart/FAQ guidance is restated across multiple sections, so it could be tightened.	2 / 3
Actionability	Highly actionable for an instruction-only skill: exact character limits (title 50-60, meta 150-160), explicit URL patterns, a frontmatter field table, citation/PAA counts, folder mappings, and a copy-paste-ready output template — concrete and complete rather than abstract.	3 / 3
Workflow Clarity	Two sequenced modes plus a 4-step Pre-Writing Research Protocol are gated by explicit checkpoints ('Get user approval before proceeding', 'Complete all four steps before writing a single word', 'Verify against the Quality Checklist before delivering') with clear feedback loops on unverified stats and unsupported brand mentions.	3 / 3
Progressive Disclosure	Sections are well-organized with clear headers and the one cross-reference (create-geo-charts) is properly signaled, but at ~419 lines with no bundle files the content is monolithic — page-type frameworks, block specs, frontmatter/SEO standards, and the repeated checklist could be split into separate reference files to keep SKILL.md an overview.	2 / 3
	Total	10 / 12 Passed

Description

67%

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 and distinctive, clearly conveying what the skill does and its niche, but it lacks an explicit 'Use when' trigger clause and misses common trigger phrasing like 'SEO'. Adding trigger guidance and natural keywords would lift the completeness and trigger-term scores.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user needs SEO-optimized, AI-citation-ready product content pages (comparison, guide, use case, learn, or trust pages).'

Surface natural trigger keywords users actually say — 'SEO content', 'blog post', 'ranking pages', 'AI overview / LLM citations' — alongside the current phrasing.

Replace or supplement the jargon-y 'AI engine citations' with the more common 'AI search citations' or 'LLM citations' phrasing.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ('Writes product-led content pages', 'Produces markdown files with frontmatter') and enumerates specific page-type frameworks (comparison, guide, use case, learn, trust), matching the comprehensive-action anchor.	3 / 3
Completeness	Clearly answers 'what' (writes/produces pages following page-type frameworks) but lacks any explicit 'Use when...' trigger clause, so per the guidelines completeness is capped at 2 with 'when' only implied.	2 / 3
Trigger Term Quality	Includes relevant natural terms ('content pages', 'search engines', 'AI engine citations', 'markdown files') but omits the most common user phrasing 'SEO' and uses the non-standard 'AI engine citations' rather than 'AI search'/'LLM citations', leaving coverage of natural variations incomplete.	2 / 3
Distinctiveness Conflict Risk	The specialized SEO+GEO product-led content niche with page-type frameworks and verified-source constraints carves a clear, distinctive scope unlikely to trigger for unrelated skills.	3 / 3
	Total	10 / 12 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: onvoyage-ai/gtm-engineer-skills
Path: write-seo-geo-content/SKILL.md
Commit: 3777930

Reviewed: about 19 hours 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.