CtrlK
BlogDocsLog inGet started
Tessl Logo

geo-content-optimizer

Use when the user asks to "optimize for AI", "get cited by ChatGPT", "AI optimization", "appear in AI answers", "GEO optimization", "get cited by AI", "show up in ChatGPT answers", "AI does not mention my brand", or "make content AI-quotable". Optimizes content for Generative Engine Optimization (GEO) to increase chances of being cited by AI systems like ChatGPT, Claude, Perplexity, and Google AI Overviews. Makes content AI-friendly while maintaining SEO value. For SEO-focused writing, see seo-content-writer. For entity and brand presence, see entity-optimizer.

60

Quality

73%

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 ./.agents/skills/geo-content-optimizer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

56%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 highly actionable and well-sequenced with validation checkpoints, a self-check, and a worked example, but it is markedly verbose — heavy placeholder templates and a conceptual fundamentals section inflate the token budget, and a referenced benchmark file is missing from the bundle.

Suggestions

Move the large placeholder report/analysis templates into a reference file and keep only a compact inline example, cutting the body substantially.

Remove or condense the conceptual 'How AI Systems Select Content to Cite' section, which restates general knowledge Claude already has.

Resolve the dangling '../../references/core-eeat-benchmark.md' reference — either bundle the file or inline the few GEO-First items the workflow actually needs.

DimensionReasoningScore

Conciseness

At ~590 lines the body is noticeably verbose, with large placeholder-filled template blocks (e.g. the GEO Analysis table of '[X]'/'[notes]' and the report tables) and a conceptual 'How AI Systems Select Content to Cite' section that pads rather than instructs, matching anchor 2.

2 / 5

Actionability

Provides concrete, actionable guidance — definition and quotable-statement templates with before/after examples, copy-paste FAQ JSON-LD schema, structure HTML examples, and a fully worked before/after Example — with only minor placeholder abstraction keeping it just below anchor 5.

4 / 5

Workflow Clarity

A clear numbered 11-step sequence is backed by explicit Input/Output Validation Checkpoints, a step-11 CORE-EEAT self-check table, and a '50% GEO score improvement' gate; it falls short of anchor 5 only because there is no explicit re-iterate loop after the self-check flags items needing attention.

4 / 5

Progressive Disclosure

Section structure is good and two real one-level-deep reference files are clearly signaled via markdown links, but large template blocks are inlined rather than split into references and '../../references/core-eeat-benchmark.md' is referenced twice yet absent from the bundle, fitting anchor 3 over 4.

3 / 5

Total

13

/

20

Passed

Description

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

A strong description: it leads with a rich set of natural trigger phrases, clearly states what the skill does and when to use it, and explicitly disambiguates from sibling SEO/entity skills. The only weakness is that the stated actions are somewhat abstract rather than granular.

DimensionReasoningScore

Specificity

Names the GEO domain and a couple of concrete actions ('Optimizes content for Generative Engine Optimization (GEO)', 'Makes content AI-friendly while maintaining SEO value'), but the verbs are abstract restatements rather than granular operations, so it stops at anchor 3 rather than 4.

3 / 5

Completeness

Explicitly answers both 'what' ('Optimizes content for GEO to increase chances of being cited by AI systems...') and 'when' (a leading 'Use when the user asks to...' clause with concrete trigger phrases), matching anchor 5.

5 / 5

Trigger Term Quality

Opens with nine quoted natural phrases a user would actually say ('optimize for AI', 'get cited by ChatGPT', 'show up in ChatGPT answers', 'AI does not mention my brand', 'make content AI-quotable'), giving comprehensive synonym coverage matching anchor 5.

5 / 5

Distinctiveness Conflict Risk

Clear GEO/AI-citation niche with distinct triggers, and explicit disambiguation ('For SEO-focused writing, see seo-content-writer. For entity and brand presence, see entity-optimizer.') minimizes conflict risk, matching anchor 5.

5 / 5

Total

18

/

20

Passed

Validation

75%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 12 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (626 lines); consider splitting into references/ and linking

Warning

metadata_field

'metadata' should map string keys to string values

Warning

relative_links

Relative link issues: 30 suspicious

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

12

/

16

Passed

Repository
teeclaw/phorm-nft
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.