CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

seo-dataforseo

Live SEO data via DataForSEO MCP server: SERP analysis, keyword research (volume, difficulty, intent, trends), backlink profiles, on-page analysis, competitor and content analysis, business listings, AI visibility (LLM mention tracking), and domain analytics. Requires DataForSEO extension installed. Use when user says "dataforseo", "live SERP", "keyword volume", "backlink data", "AI visibility check", or "real search data".

Quality

88%

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

The canonical home for this skill is seo-dataforseo in AgriciDaniel/claude-seo

SKILL.md
Quality
Evals
Security

Quality

Content

85%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 highly actionable, well-structured MCP command reference: exact tool names, parameters, cost-guardrail validation loops, and clean one-level-deep bundle references (both referenced files exist and hold the promised content). The main weakness is token efficiency — a caveat repeated three times, an approval flow duplicated between the body and cost-tiers.md, and date-stamped version pins outside any deprecated section.

Suggestions

State the 'pinned MCP server has no Google Images tool' caveat once (in the serp-images section) and reference it from the quick-reference table and the seo-images cross-skill bullet instead of repeating the full explanation.

Keep the cost-approval flow in only one place (references/cost-tiers.md) and have the Cost Guardrails section say just 'run the check script before every call; see references/cost-tiers.md for the approval flow and outcomes', removing the duplicated branch/log steps and user commands.

Move the version pin and verification dates (dataforseo-mcp-server@2.8.10, 2026-09-23) into a short 'Version notes' or deprecated-style section so the time-sensitive stamps don't sit in the main operational text.

DimensionReasoningScore

Conciseness

The body is a dense, competent command catalog with no basic-concept padding, but it could be tightened: the 'no Google Images tool on the pinned MCP server' caveat is repeated three times (quick-reference table, the serp-images section, and the seo-images cross-skill bullet), and the cost-approval flow (check/approved/needs_approval/blocked/log) is fully duplicated in both the body and references/cost-tiers.md. Time-sensitive version/date stamps ("dataforseo-mcp-server@2.8.10", "checked against the package, 2026-09-23") appear outside any deprecated/old-patterns section, which the rubric explicitly penalizes, holding this below the level-4 'minor instances that could be trimmed' anchor.

3 / 5

Actionability

Every command specifies exact MCP tool names (e.g., `serp_organic_live_advanced`, `ai_opt_llm_ment_search`), concrete default parameters (location_code=2840, language_code=en, depth=100), expected outputs, and copy-paste-ready shell commands for cost guarding ("${CLAUDE_PLUGIN_ROOT}/scripts/claude-seo" run dataforseo_costs.py check <endpoint>). As an instruction-only MCP skill its guidance is fully executable and covers the common cases, matching the level-5 anchor.

5 / 5

Workflow Clarity

Multi-step processes are explicitly sequenced with validation checkpoints: a mandatory pre-call cost check with three-way branching (approved → proceed, needs_approval → confirm with user, blocked → do not proceed), post-call cost logging, a numbered 4-step workflow for ai-mentions, and an error-handling section with recovery guidance (rate limit → wait and retry; no results → report and broaden query). The explicit pre-call validation and error feedback loops match the level-5 anchor; the batch/destructive cap does not apply since validation is present.

5 / 5

Progressive Disclosure

The body is a well-navigable overview (quick-reference table up front, grouped per-command sections) that appropriately offloads the pricing table to references/cost-tiers.md and the bulk utility tool list to references/tool-catalog.md — both real files, clearly signaled ("Load references/cost-tiers.md for the full pricing table"), exactly one level deep with no nested references. This matches the level-5 anchor: clear overview with well-signaled one-level-deep references and appropriately split content.

5 / 5

Total

18

/

20

Passed

Description

88%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: concrete, comprehensive capability enumeration in third-person voice, an explicit 'Use when' trigger clause with natural user phrases, and a stated prerequisite. The only gaps are a few missing natural trigger variations and minor overlap risk with closely related SEO skills in the same suite.

DimensionReasoningScore

Specificity

The description lists multiple concrete capability areas with sub-details — "SERP analysis, keyword research (volume, difficulty, intent, trends), backlink profiles, on-page analysis, competitor and content analysis, business listings, AI visibility (LLM mention tracking), and domain analytics" — giving comprehensive, non-generic coverage. It clearly matches the anchor "Lists multiple specific concrete actions; comprehensive coverage" rather than the level-4 anchor, which expects minor gaps in coverage.

5 / 5

Completeness

It explicitly answers both questions: the "what" via the full capability list and the "when" via "Use when user says 'dataforseo', 'live SERP', 'keyword volume', 'backlink data', 'AI visibility check', or 'real search data'", plus the stated prerequisite. This directly matches the level-5 anchor (clear what AND when with concrete trigger phrases) and exceeds the level-4 anchor whose "when" is less explicit.

5 / 5

Trigger Term Quality

The explicit triggers "dataforseo", "live SERP", "keyword volume", "backlink data", "AI visibility check", or "real search data" are natural user phrasings with good coverage. A few common variations are missing (e.g., "search volume", "keyword difficulty", "competitor analysis", "SERP results"), so it fits the level-4 anchor "Good keyword coverage; a few natural terms missing" rather than the comprehensive level-5 anchor.

4 / 5

Distinctiveness Conflict Risk

The product-name trigger "dataforseo" and the live-data framing ("real search data") carve a clear niche, but triggers like "keyword volume" and "backlink data" could overlap with sibling SEO skills in the same suite (e.g., seo-content, seo-audit per the body's cross-skill section). This fits "Mostly distinct; minor overlap risk with closely related skills" rather than the minimal-conflict level-5 anchor.

4 / 5

Total

18

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

AgriciDaniel/claude-seo

Path

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