Added GEO principles to SKILL.md

[JV0812]

Purpose of this pull request

This pull request is to create a SKILL.md file with GEO principles to enhance the AI citation.

Select the type of change

• Minor Changes - Typos, formatting, slight revisions
• Update Content - Revisions, updating sections
• New Content - New features, sections, pages, tutorials
• Site and Tools - .clabot, version updates, maintenance, dependencies, new packages for the site (Docusaurus, Gatsby, React, etc.)

Ticket (if applicable)

Create SKILL.md for GEO principles

[mafsumo]

@JV0812 great start! I added a comments for review.

[JV0812]

@mafsumo Thanks for your review and feedback. I have incorporated your comments. Please let me know if any updates needed.

[kimsauce]

The structure is solid — clear trigger guards, good JSON-LD FAQ schema pattern, and the five principles are well-organized. A few issues need fixing before merge.

Critical

1. British spelling throughout

"optimise/Optimisation" appears in the frontmatter name/description fields and throughout the body. Needs to be American English everywhere:

• Optimisation → Optimization
• optimise → optimize
• optimised → optimized

2. Duplicate paragraph in Gotchas

The sentence "These are GEO-specific behaviors that differ from standard doc authoring..." appears twice (lines 172 and 176). Remove one.

3. YAML frontmatter example has incorrect indentation

All top-level keys in the frontmatter template have two leading spaces ( id:, title:, etc.). Standard YAML frontmatter uses no leading indent on top-level keys. Anyone copying this example will get malformed frontmatter.

Minor

4. Description character count conflicts with style guide

The Gotchas section says "Keep description: under 160 characters." The style guide now specifies 140–160 as the target range — too short is also a problem. Update to: "Keep description: between 140–160 characters."

5. Comma splice (line 105)

"AI cannot follow cross-references between pages, a self-contained page is the only page that gets cited."

Should be two sentences.

6. Trailing space (line 78)

"matches the H1 (generated from frontmatter )" — space before the closing paren.

[kimsauce]

One more suggestion (non-blocking): consider adding a cross-references section at the bottom of the skill file pointing to the related tooling that now exists alongside this:

• /geo-optimize — interactive command for applying GEO improvements to a doc (proposes changes, waits for approval)
• /seo-audit — audit command that checks SEO/AEO/GEO signals and can hand off to /geo-optimize
• Public style guide AEO/GEO guidance: #aeo-answer-engine-optimization and #geo-generative-engine-optimization

Without these pointers, someone reading the skill file has no way to discover the command workflow or the human-readable guidance in the style guide.

[kimsauce]

Two structural issues to resolve before merge:

1. Skill directory name mismatch. The directory is geo-guide, which means Claude would invoke this as /geo-guide. But the active command listed in CLAUDE.md is /geo-optimize, which expects a skill at .claude/skills/geo-optimize/SKILL.md. If this is meant to back that command, rename the directory to geo-optimize.

2. CLAUDE.md not updated. All skills are explicitly listed in CLAUDE.md under ## Skills:

- .claude/skills/sumo-style/SKILL.md
- .claude/skills/docusaurus/SKILL.md
- .claude/skills/pr-template-guide/SKILL.md

This new skill needs to be added there so Claude loads it in future conversations.

[JV0812]

@kimsauce I have addressed all your comments. As you said, we can update the file without the head frontmatter. Once we build the plumbing (engineering work) we can add those later.

[kimsauce]

The structure is solid and the 'Do not apply GEO for' section is especially important to get right — good call including it. A few things to tighten up below.