CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

seo-seranking

SE Ranking AI visibility analyst (extension). Tracks AI Share-of-Voice across ChatGPT, Gemini, Perplexity, AI Overviews, and AI Mode in a single query.

Quality

70%

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 ./extensions/seranking/skills/seo-seranking/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%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-organized, token-efficient overview with concrete routing commands and sensible guardrails, and its single-file structure suits its size. Its main weakness is execution detail: no actual SE Ranking API call example or end-to-end query workflow, leaving Claude to infer how to invoke the vendor API and validate responses.

Suggestions

Add a minimal executable example of the SE Ranking API call (endpoint URL, auth header using SERANKING_API_KEY, and a sample request/response for an AI visibility query) so the core operation is copy-paste runnable.

Spell out the run workflow with checkpoints: query the API, validate the response (HTTP status, sample size fields), then report each *_sov percentage with a confidence note; include what to do on API error or empty samples.

Trim the Profound/Peec AI comparison sentence, which adds vendor context without operational value.

DimensionReasoningScore

Conciseness

The body is lean and operational — routing table, API key check, unit costs, delegation rules — with almost no explanation of concepts Claude already knows. One tangential sentence ("The scorer is the same logic used by Profound / Peec AI but bundled into one MCP/API") could be trimmed, keeping it at anchor 4 rather than 5.

4 / 5

Actionability

Concrete elements exist (routing commands like "/seo seranking ai-visibility <brand>", the env-var verification step, and the logging command "${CLAUDE_PLUGIN_ROOT}/scripts/claude-seo run dataforseo_costs.py"), but for a skill whose entire purpose is driving the SE Ranking REST API there is no executable API example — no endpoint, auth header format, or sample request/response. This lands at anchor 3 (some concrete guidance but missing key details) rather than 4.

3 / 5

Workflow Clarity

Prerequisites are sequenced with one explicit validation checkpoint ("Before any call, verify SERANKING_API_KEY is present... If absent, tell the user to run the installer"), but the main operation — issue query, parse the *_sov fields, report with confidence note — is described only loosely with no checkpoints for API errors or empty samples. Matches anchor 3 (sequence present, checkpoints missing or implicit) rather than 4.

3 / 5

Progressive Disclosure

This is a short (~50-line) single-file skill with no bundle directories, organized into clear sections (Prerequisites, Routing, scoring fields, Cost guardrails, delegation, Security) and a routing table. Per the rubric's simple-skill guideline, content under 50 lines with no need for external references scores 5 with well-organized sections; nothing inlined here belongs in a separate file.

5 / 5

Total

15

/

20

Passed

Description

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

The description is specific and distinctive, naming a clear vendor niche and concrete platform coverage, but it omits any "when to use" trigger guidance, which caps its completeness. Trigger term coverage is good though missing common synonyms like "brand mentions" or "AI SEO".

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks about brand visibility, share-of-voice, or brand mentions in ChatGPT, Gemini, Perplexity, or Google AI answers."

Include natural synonyms such as "brand mentions", "AI SEO", "GEO", or "LLM visibility" alongside the platform names to broaden trigger coverage.

Mention a second concrete capability (e.g. SERP position tracking or competitor gaps) if the skill supports it, to lift specificity beyond a single action.

DimensionReasoningScore

Specificity

"Tracks AI Share-of-Voice across ChatGPT, Gemini, Perplexity, AI Overviews, and AI Mode in a single query" names the domain and one concrete action with specific platforms, but offers no additional actions (no analysis, reporting, or comparison verbs). It matches anchor 3 (domain plus 1-2 concrete actions, not comprehensive) rather than 4, which requires several specific actions.

3 / 5

Completeness

The "what" is clear (tracks AI Share-of-Voice across five named platforms in a single query), but there is no "when" — no "Use when..." clause or equivalent explicit trigger guidance. Per the judging guidelines, a missing trigger clause caps completeness at 3, matching the anchor "clear what but when missing or only weakly implied".

3 / 5

Trigger Term Quality

Includes strong natural terms users would say — "AI visibility", "Share-of-Voice", "ChatGPT", "Gemini", "Perplexity", "AI Overviews", "AI Mode", "SE Ranking". Missing common variations such as "brand mentions", "AI SEO", "GEO", or "LLM visibility", so it falls short of anchor 5's comprehensive synonym coverage but is clearly above anchor 3's partial coverage.

4 / 5

Distinctiveness Conflict Risk

"SE Ranking AI visibility analyst (extension)" carves out a distinct vendor-specific niche with platform-specific triggers, but the body itself acknowledges closely related skills (seo-geo) covering the same AI-visibility domain, indicating minor overlap risk with sibling skills. Mostly distinct rather than the minimal-conflict clarity of anchor 5.

4 / 5

Total

14

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

AgriciDaniel/claude-seo

Path

extensions/seranking/skills/seo-seranking/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.