geo-fundamentals

Generative Engine Optimization for AI search engines (ChatGPT, Claude, Perplexity).

Quality

43%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./.agent/skills/geo-fundamentals/SKILL.md

Quality

Discovery

22%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This description identifies a specific niche (GEO for AI search engines) but fails to explain what the skill actually does or when to use it. It reads more like a topic label than a functional skill description, lacking both concrete actions and explicit trigger guidance.

Suggestions

Add specific actions the skill performs, e.g., 'Analyzes content for AI search visibility, optimizes structure for LLM citation, improves brand mentions in AI responses'

Include a 'Use when...' clause with natural trigger terms like 'AI search optimization', 'GEO', 'getting cited by AI', 'AI visibility', 'appear in ChatGPT/Perplexity results'

Add common user phrases and variations: 'AI SEO', 'LLM optimization', 'AI search ranking', 'cited by AI assistants'

Dimension	Reasoning	Score
Specificity	The description names a domain ('Generative Engine Optimization') and lists AI search engines, but provides no concrete actions. It doesn't explain what the skill actually does - no verbs describing capabilities like 'optimize content', 'analyze rankings', or 'generate recommendations'.	1 / 3
Completeness	The description only vaguely addresses 'what' (optimization for AI search) and completely lacks a 'when' clause. There's no 'Use when...' guidance or explicit triggers for when Claude should select this skill.	1 / 3
Trigger Term Quality	Includes some relevant terms like 'AI search engines', 'ChatGPT', 'Claude', 'Perplexity', and the acronym-worthy 'Generative Engine Optimization'. However, it misses common user phrases like 'GEO', 'AI SEO', 'AI visibility', 'AI search ranking', or 'get found by AI'.	2 / 3
Distinctiveness Conflict Risk	The focus on AI search engines (ChatGPT, Claude, Perplexity) provides some distinctiveness from traditional SEO skills. However, without specific actions or triggers, it could overlap with general SEO, content optimization, or marketing skills.	2 / 3
	Total	6 / 12 Passed

Implementation

64%

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

This skill excels at concise, token-efficient presentation using tables effectively to convey GEO concepts. However, it reads more as a reference guide than an actionable skill - it tells Claude what GEO elements matter but doesn't provide concrete implementation steps, code examples, or validation workflows for actually optimizing content.

Suggestions

Add concrete examples showing before/after content optimization (e.g., a paragraph transformed to be more GEO-friendly)

Include a sequential workflow with validation steps: 'Audit existing content → Identify gaps → Implement changes → Verify with geo_checker.py → Iterate'

Provide executable code snippets for technical elements like schema markup implementation, not just checklist items

Dimension	Reasoning	Score
Conciseness	The content is highly efficient, using tables throughout to convey maximum information with minimal tokens. No unnecessary explanations of concepts Claude would already know; every section delivers actionable information.	3 / 3
Actionability	Provides good checklists and structured guidance, but lacks concrete executable examples. The script reference at the end is helpful, but the main content is more descriptive (what to do) than executable (how to do it with specific code/commands).	2 / 3
Workflow Clarity	Content is well-organized into logical sections, but lacks a clear sequential workflow for implementing GEO. The checklist provides items to complete but no explicit order, validation steps, or feedback loops for the optimization process.	2 / 3
Progressive Disclosure	Content is well-structured with clear sections and tables, but everything is in one file. For a skill of this size (~150 lines), some content like the detailed checklist or entity building could be split into separate reference files with clear navigation.	2 / 3
	Total	9 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning

	Total	10 / 11 Passed

Repository: lchenrique/politron-ide
Commit: 7114206

Reviewed: 29 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.