CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

geo-content-optimizer

Use when the user asks to "optimize for AI citations"; improves citation readiness for ChatGPT, Perplexity, AI Overviews, Gemini, and Claude. Not for structural on-page SEO — use on-page-seo-checker; not for net-new drafting — use content-writer. AI引用优化/GEO优化/AI搜索

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./seo-geo/implement/geo-content-optimizer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 a well-sectioned overview with a genuinely executable workflow, a concrete keyless probe command, honest measurement-latency guidance, and a clean one-level-deep local reference bundle. Its weaknesses are token weight spent on cross-suite contract/termination machinery and a wide fan-out of parent-repo links that reduce standalone navigability.

Suggestions

Compress or relocate the "Skill Contract" reads/writes/promotes and termination-note sections (e.g., into the already-referenced skill-contract.md) so SKILL.md spends its budget on GEO guidance.

Inline the Handoff Summary format (or a 3-line skeleton) instead of routing through ../../../references/skill-contract.md, and prune the parent-repo link fan-out (platform refs, llms-txt/OKF) to those the optimizer actually needs.

Add one short fix-and-recheck instruction after Step 5 (e.g., "if any self-check item is Fail, revise that passage and re-score") to close the validation loop explicitly, and inline the one-line meanings of the four gate CORE-EEAT IDs (C02, O03, O05, E01).

DimensionReasoningScore

Conciseness

The operational core (Quick Start, five-step Instructions, labeling rule) is lean and assumes competence, but a substantial share of tokens goes to host-framework ceremony — the "Skill Contract" reads/writes/promotes block, the "Handoff Summary" pointer, "Promotes ... to memory/hot-cache.md and memory/open-loops.md", and the visited-set/"max handoff depth of 3" termination note — none of which advances the GEO task itself. This fits anchor 3 ("mostly efficient but includes some unnecessary explanation or could be tightened"); it is not anchor 4 because the contract/termination boilerplate is more than a minor trim.

3 / 5

Actionability

Concrete, executable guidance dominates: a copy-paste command ("python3 \"${CLAUDE_PLUGIN_ROOT}/scripts/connectors/tavily.py\" search \"<target query>\" --answer --limit 10"), specific techniques ("standalone 25-50 word definitions, sourced quotable statements ... FAQ schema"), a save-path template ("memory/content/YYYY-MM-DD-<topic>.md"), and the Measured/User-provided/Estimated/N-A labeling rule. It misses anchor 5 because the Example section defers the actual output to a reference file and the CORE-EEAT IDs (C02, O03, E01) are unresolvable without loading the reference.

4 / 5

Workflow Clarity

The five numbered steps form a clear sequence ending in an explicit validation step ("CORE-EEAT GEO Self-Check — verify C02, C04, C09 ... with Pass/Warn/Fail") with a done-when gate ("the CORE-EEAT GEO self-check ... has no unaddressed Fail"), and the operation is not destructive/batch so no cap applies. It sits at anchor 4 rather than 5 because there is no explicit fix-and-re-check loop spelled out in the body (the iterate-until-pass behavior is only implied by "no unaddressed Fail") and the self-check criteria live in the reference.

4 / 5

Progressive Disclosure

Scoring against the actual bundle: all six cited local references exist with real content, are exactly one level deep, and are clearly signaled with per-file one-line descriptions in the "Reference Materials" list — close to anchor 5. It drops to anchor 4 ("minor organization gaps") because the body also fans out to ~10 paths outside the bundle ("../../../references/skill-contract.md", "../../../CONNECTORS.md", "../../../references/platforms/x.md", "../../tune/content-quality-auditor/SKILL.md", "scripts/connectors/*") which are unresolvable within this skill's directory and make the load-bearing Handoff Summary format depend on an external file.

4 / 5

Total

15

/

20

Passed

Description

73%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 well-constructed description with an explicit trigger phrase, precise engine scope, explicit exclusions that redirect to sibling skills, and bilingual trigger terms in third-person voice. Its main weakness is that the capability statement is a single abstract action, leaving the description thinner on what the skill concretely does than the body it summarizes.

Suggestions

Replace or extend "improves citation readiness" with 2-3 concrete actions, e.g., "adds standalone 25-50 word definitions, sourced quotable statements, and FAQ schema; reports before/after GEO scores".

Add the most common English trigger terms — "GEO", "generative engine optimization", "AI search visibility" — to complement the existing Chinese synonyms.

Trim the duplicated Chinese keyword tail ("AI引用优化/GEO优化/AI搜索") already covered by the summary field, since it pads the description without adding new trigger information.

DimensionReasoningScore

Specificity

The only stated action is "improves citation readiness for ChatGPT, Perplexity, AI Overviews, Gemini, and Claude" — one abstract verb plus a specific list of target engines, but no concrete actions (e.g., adding standalone definitions, quotable statements, FAQ schema) that the body shows it performs. This matches anchor 3 ("Names domain and 1-2 concrete actions, but not comprehensive"); it is below anchor 4 because several specific actions are not listed, and above anchor 2 because the domain and engine scope are named precisely.

3 / 5

Completeness

Both parts are present: the "what" ("improves citation readiness for...") and an explicit "when" ("Use when the user asks to 'optimize for AI citations'"), plus unusually strong negative boundaries ("Not for structural on-page SEO — use on-page-seo-checker; not for net-new drafting — use content-writer"). It stops short of anchor 5 because the "what" is a single abstract action rather than the multiple concrete capabilities the anchor-5 example lists; it exceeds anchor 3 because the when-clause is explicit with a concrete trigger phrase.

4 / 5

Trigger Term Quality

The quoted trigger "optimize for AI citations" is a natural user phrase, engine names (ChatGPT, Perplexity, AI Overviews, Gemini, Claude) are terms users actually mention, and the Chinese synonyms "AI引用优化/GEO优化/AI搜索" add bilingual coverage. It falls at anchor 4 ("Good keyword coverage; a few natural terms missing") rather than 5 because common English variants like "GEO", "generative engine optimization", and "AI search visibility" are absent from the description itself.

4 / 5

Distinctiveness Conflict Risk

The description carves out a clear niche (AI citation readiness) and explicitly disambiguates against the two most confusable siblings ("Not for structural on-page SEO — use on-page-seo-checker; not for net-new drafting — use content-writer"), giving minimal conflict risk. This matches anchor 5 ("Clear niche with distinct triggers; minimal conflict risk") — the explicit redirect clauses exceed anchor 4's "minor overlap risk".

5 / 5

Total

16

/

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

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 16 suspicious

Warning

referenced_paths_exist

Referenced path issues: 2 missing, 1 deeper-than-1-level

Warning

Total

12

/

16

Passed

Repository

aaron-he-zhu/aaron-marketing-skills

Path

seo-geo/implement/geo-content-optimizer/SKILL.md

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.