CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cs-aeo

Answer Engine Optimization (AEO) specialist agent. Use when content needs to be optimized for citation by AI language models (ChatGPT, Perplexity, Claude, Gemini, Mistral) rather than for traditional search rankings. Orchestrates the aeo skill — runs E-E-A-T audit, generates optimization variants in conservative/balanced/aggressive modes, and maintains a citation tracking ledger. Industry-aware (8 industries with calibrated thresholds). Distinguishes AEO from SEO and refuses to optimize for one channel at the expense of the other. Voice — pragmatic content strategist; respects existing SEO investments; insists on real first-person evidence over fabricated authority signals.

61

Quality

77%

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 ./.gemini/skills/cs-aeo/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

A well-organized agent-definition body with clear purpose, differentiation from sibling skills, and explicit hard rules, but it stops short of executable guidance: the three Python tools are named without any invocation examples, and the workflow's validation checkpoints are stated as refusal rules rather than explicit steps. Trimming the voice-script block and version metadata would tighten it further.

Suggestions

Add one example invocation per tool (e.g., `python aeo_optimizer.py <content> --mode balanced --industry healthcare`) with expected output shape, so guidance is executable rather than descriptive.

Add an explicit post-optimization validation step to the workflow — re-run aeo_audit.py on each variant and compare composite scores before presenting it — creating a verify/fix feedback loop.

Trim the '(8 sources)' parentheticals and move the Version/Source/License block out of the main body (or into a short footer note) to reduce non-actionable tokens.

DimensionReasoningScore

Conciseness

The body avoids explaining concepts Claude already knows and is mostly dense, but it could be tightened: the 7 quoted voice scripts run ~30 lines, meta-fluff like "(each cites 7+ sources)" / "(8 sources)" adds nothing actionable, and time-sensitive metadata ("Version: 2.7.3") sits in the footer rather than a deprecation/old-patterns section. Matches 'mostly efficient but includes some unnecessary explanation or could be tightened' rather than the minor-trims anchor at 4.

3 / 5

Actionability

Concrete artifacts are named (aeo_audit.py, aeo_optimizer.py, citation_tracker.py with modes and ledger actions) and hard rules give decision criteria, but no executable guidance appears — no invocation syntax, example commands, or expected output format for any tool. This matches 'some concrete guidance but incomplete; missing key details'; score 4 would require mostly executable commands with minor gaps.

3 / 5

Workflow Clarity

The sequence is present (minimal intake Q1-Q3 one per turn → audit before optimize → apply fixes → citation ledger over 4-12 weeks) and gating rules exist (85+ YMYL threshold, 'refuse to optimize below threshold'). But checkpoints are implicit rather than explicit validation steps — there is no verify-output step (e.g., re-audit the optimized variant, confirm citations are real before adding to the ledger is stated as a rule but not as a workflow step), matching 'sequence present but checkpoints missing or implicit'.

3 / 5

Progressive Disclosure

Good structure: the body is an overview with clearly signaled one-level-deep references to the aeo skill's docs (aeo_eeat_canon.md, llm_citation_patterns.md, aeo_vs_seo.md) each with a one-line description. However, those paths point into 'marketing-skill/skills/aeo/' which does not exist in this bundle, so navigation cannot be fully verified — minor organization gaps keep it at the 'good structure' anchor rather than 5.

4 / 5

Total

13

/

20

Passed

Description

92%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: explicit 'Use when' trigger with clear what/when coverage, concrete named actions, named target LLMs, and explicit boundary-drawing against SEO. Only gap is a few missing user-side synonyms for the AEO concept.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "runs E-E-A-T audit", "generates optimization variants in conservative/balanced/aggressive modes", "maintains a citation tracking ledger", "calibrates thresholds" across 8 industries — with comprehensive coverage of the skill's capabilities. This matches the anchor for multiple specific concrete actions with comprehensive coverage; score 4 would require minor gaps in coverage, but audit, optimization, tracking, industry calibration, and SEO-compatibility are all named.

5 / 5

Completeness

Both halves are explicit: what it does ("Orchestrates the aeo skill — runs E-E-A-T audit, generates optimization variants... maintains a citation tracking ledger") and when to use it ("Use when content needs to be optimized for citation by AI language models... rather than for traditional search rankings"). This matches the top anchor with concrete trigger phrases; score 4 would require the 'when' to be less explicit, which it is not.

5 / 5

Trigger Term Quality

Strong natural keywords: "citation by AI language models (ChatGPT, Perplexity, Claude, Gemini, Mistral)", "AEO", "SEO", "search rankings", "E-E-A-T". A few natural terms users might say are missing (e.g., "AI search", "get cited by ChatGPT", "generative engine optimization"), so it sits between "good coverage with a few missing" (4) and fully comprehensive (5).

4 / 5

Distinctiveness Conflict Risk

It carves out a clear niche and actively de-conflicts: "Distinguishes AEO from SEO and refuses to optimize for one channel at the expense of the other", and the trigger explicitly excludes "traditional search rankings". Minimal conflict risk with adjacent SEO skills; matches the clear-niche anchor.

5 / 5

Total

19

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

relative_links

Relative link issues: 1 missing, 1 suspicious

Warning

Total

14

/

16

Passed

Repository

alirezarezvani/claude-skills

Path

.gemini/skills/cs-aeo/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.