CtrlK
BlogDocsLog inGet started
Tessl Logo

seo-geo

SEO & GEO (Generative Engine Optimization) for websites. Analyze keywords, generate schema markup, optimize for AI search engines (ChatGPT, Perplexity, Gemini, Copilot, Claude) and traditional search (Google, Bing). Use when user wants to improve search visibility.

83

1.21x
Quality

78%

Does it follow best practices?

Impact

95%

1.21x

Average score across 3 eval scenarios

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/seo-geo/SKILL.md

The canonical home for this skill is seo-geo in ReScienceLab/opc-skills

SKILL.md
Quality
Evals
Security

Quality

Content

82%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-structured, highly actionable skill body with a clear five-step workflow, executable commands and templates, and proper offloading of detail to reference files and scripts. The main improvements are adding an explicit validation feedback loop and fixing bundle hygiene (one dead reference link, one orphaned reference file).

Suggestions

Add an explicit feedback loop in Step 5, e.g. "If the Rich Results Test reports errors, fix the JSON-LD and re-run validation before generating the report."

Fix bundle hygiene: create the missing examples/opc-skills-case-study.md (or remove the link) and link references/google-docs-summary.md from the body so it is discoverable.

Trim the standard Open Graph/Twitter meta-tag template to only the skill-specific choices, and drop the deprecated meta keywords tag.

DimensionReasoningScore

Conciseness

The body is dense and skimmable — method tables, command blocks, and per-platform checklists with almost no filler or explanation of concepts Claude already knows. Minor trims possible: the full inline Open Graph/Twitter meta-tag template is standard HTML, and the deprecated meta keywords tag could be dropped. Not level 5 because of these few over-included tokens; well above level 3.

4 / 5

Actionability

Fully executable throughout: curl commands for robots.txt, sitemap, and meta-tag checks; `python3 scripts/seo_audit.py "https://example.com"` (the script exists and matches its documented usage); WebSearch query templates; a complete FAQPage JSON-LD block; and validator URLs. The common audit case is covered copy-paste ready end to end.

5 / 5

Workflow Clarity

A clear five-step sequence (Audit → Keyword Research → GEO → Traditional SEO → Validate & Monitor) with explicit validation commands (Rich Results Test, Schema.org Validator) and checklists in Steps 4-5. It falls short of level 5 because there is no explicit feedback loop instructing what to do when validation or a check fails (fix and re-validate), which the level-5 anchor requires.

4 / 5

Progressive Disclosure

Good structure: the body is an overview, detailed material is split into five real one-level-deep reference files and ten scripts, and links are clearly signaled. Minor gaps keep it at 4 rather than 5: `examples/opc-skills-case-study.md` is referenced but does not exist in the bundle, and `references/google-docs-summary.md` is present but never linked from the body.

4 / 5

Total

17

/

20

Passed

Description

75%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 solid description that names the domain, several concrete capabilities, both traditional and AI search targets, and an explicit use-when clause. Its main weaknesses are the generic 'when' trigger wording and a few missing natural phrasings users would actually say.

Suggestions

Make the use-when clause more concrete with trigger phrases, e.g. "Use when the user wants to improve search ranking, get cited by ChatGPT/Perplexity/AI Overviews, or add schema markup/JSON-LD to a site."

Add natural synonyms such as "rank higher", "get found on Google/Bing", and "AI Overview visibility" to strengthen trigger term coverage.

DimensionReasoningScore

Specificity

Lists several concrete actions — "Analyze keywords, generate schema markup, optimize for AI search engines (ChatGPT, Perplexity, Gemini, Copilot, Claude) and traditional search (Google, Bing)" — though "optimize for" is somewhat generic and coverage is less comprehensive than a level-5 example. It exceeds the 1-2 concrete actions of level 3, so it sits at 4.

4 / 5

Completeness

Both what ("Analyze keywords, generate schema markup, optimize for AI search engines... and traditional search") and when ("Use when user wants to improve search visibility") are present, but the when-clause is generic and lacks concrete trigger phrases, matching the level-4 anchor exactly. It is clearly above level 3, where 'when' is missing or only weakly implied.

4 / 5

Trigger Term Quality

Good natural keywords: "SEO", "keywords", "schema markup", "search visibility", plus named platforms (ChatGPT, Perplexity, Google, Bing) users mention when seeking AI-search visibility. A few common phrasings are missing ("rank higher", "get found on Google", "SERP"), keeping it below 5.

4 / 5

Distinctiveness Conflict Risk

The SEO/GEO domain with named AI platforms is a clear niche with distinct triggers, but there is minor overlap risk with general web-analytics or content-marketing skills. Not level 5: the broad "improve search visibility" framing could co-trigger with marketing-adjacent skills.

4 / 5

Total

16

/

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

Warning

Total

14

/

16

Passed

Repository
ReScienceLab/opc-skills
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.