CtrlK
BlogDocsLog inGet started
Tessl Logo

geo-content-optimizer

Optimize content for AI citations in ChatGPT, Perplexity, AI Overviews, Gemini, Claude. AI引用优化/GEO优化/AI搜索

57

Quality

67%

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

Quality

Content

62%

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

The skill has a strong, well-gated workflow and genuine supporting reference files, but it is verbose and relies on placeholder templates rather than concrete executable guidance. Moving the inline benchmark tables into references and replacing fill-in placeholders with concrete examples would lift the weaker dimensions.

Suggestions

Move the CORE-EEAT benchmark tables into a reference file and keep only a one-line pointer in SKILL.md to reduce inline bulk.

Replace fill-in report templates ([X], [Definition 1]) with at least one fully worked, concrete example so the output guidance is executable rather than skeletal.

Trim restated context Claude already knows (e.g., the opening paragraph on AI systems answering queries directly) to tighten token efficiency.

DimensionReasoningScore

Conciseness

The body is roughly 420 lines with large fill-in template blocks, repeated inline benchmark tables, and framing Claude does not need ("As AI systems increasingly answer user queries directly..."); it is usable per-section but padded overall.

2 / 3

Actionability

It provides templates, checklists, and one concrete worked example, but the core optimization step defers to a reference and the report templates are placeholder fill-ins ([X], [Definition 1]) rather than executable guidance.

2 / 3

Workflow Clarity

A clear five-step sequence (Load → Analyze → Apply → Generate → Self-Check) is paired with explicit Input/Output Validation Checkpoints, giving well-sequenced steps with verification gates.

3 / 3

Progressive Disclosure

Three real reference files exist and are linked one level deep with clear signaling, but large benchmark tables are inlined in SKILL.md that would fit better in the references, so structure is only partly offloaded.

2 / 3

Total

9

/

12

Passed

Description

72%

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 with good trigger-term coverage, but it omits an explicit "Use when..." clause within the description field, which limits its completeness. Tightening the what/when pairing would raise it to the top level.

Suggestions

Add an explicit trigger clause to the description, e.g. "Use when optimizing content for AI engines like ChatGPT, Perplexity, or AI Overviews, or when aiming for AI citations."

List a couple of distinct concrete actions (e.g., audit, restructure, add citations) rather than restating "optimize" across engines.

DimensionReasoningScore

Specificity

States a concrete action ("Optimize content for AI citations") and names specific engines, but lists a single repeated action rather than multiple distinct concrete actions, so it is not the top anchor.

2 / 3

Completeness

It clearly answers "what" (optimize content for AI citations) but the description field itself lacks a "Use when..." trigger clause, which caps completeness at 2 per the rubric guideline.

2 / 3

Trigger Term Quality

Covers natural terms users would say — "AI citations", "ChatGPT", "Perplexity", "AI Overviews", "Gemini", "Claude" — plus multilingual variants ("AI引用优化", "GEO优化", "AI搜索"), giving strong keyword coverage.

3 / 3

Distinctiveness Conflict Risk

The GEO / AI-citation niche with engine-specific triggers is clearly distinct and unlikely to fire for unrelated skills.

3 / 3

Total

10

/

12

Passed

Validation

81%

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

Validation13 / 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

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

13

/

16

Passed

Repository
MODSetter/SurfSense
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.