CtrlK
BlogDocsLog inGet started
Tessl Logo

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".

74

Quality

92%

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

SKILL.md
Quality
Evals
Security

Quality

Content

85%

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 command reference with strong workflow clarity and clean progressive disclosure to verified bundle files. Its main weakness is conciseness: length and a few editorial asides could be trimmed without losing clarity.

Suggestions

Remove or relocate the inline correlation commentary (e.g. the 0.737 YouTube/AI-visibility note) to a reference file; keep per-command sections to tool names, parameters, and outputs.

Collapse the Quick Reference table or the per-command headers so each command appears once, eliminating the duplicated command-name listing.

Trim editorial asides like 'Valuable for GEO. YouTube mentions correlate most strongly with AI citations.' to keep sections token-efficient.

DimensionReasoningScore

Conciseness

The body is mostly an efficient command reference, but it is lengthy (~380 lines) with a Quick Reference table that duplicates every command later expanded in sections, plus editorial asides such as 'Some third-party studies report a 0.737 correlation between YouTube mentions and AI visibility' that could be tightened.

2 / 3

Actionability

Each command lists exact MCP tool names, default parameters (location_code=2840, language_code=en, depth=100) and outputs, and cost guardrails give copy-paste-ready commands like 'claude-seo run dataforseo_costs.py check <endpoint> [--count N]'.

3 / 3

Workflow Clarity

The Cost Guardrails section sequences check -> branch on approved/needs_approval/blocked -> log with explicit validation checkpoints, the ai-mentions section gives a numbered 4-step workflow, and Error Handling covers recovery paths.

3 / 3

Progressive Disclosure

A Quick Reference overview sits atop per-command detail, with clearly signaled one-level-deep references to references/cost-tiers.md and references/tool-catalog.md (both verified present); primary commands stay inline while the utility catalog and pricing are split out.

3 / 3

Total

11

/

12

Passed

Description

100%

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, third-person description that states concrete capabilities and pairs them with explicit natural-language trigger phrases. It clearly answers both 'what' and 'when' and occupies a distinct, low-conflict niche.

DimensionReasoningScore

Specificity

Enumerates multiple concrete capabilities — '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' — rather than vague language.

3 / 3

Completeness

Explicitly answers both what ('Live SEO data via DataForSEO MCP server: ...') and when ('Use when user says ...') with explicit triggers, satisfying the top anchor.

3 / 3

Trigger Term Quality

The 'Use when user says' clause lists natural terms an SEO user would actually utter ('live SERP', 'keyword volume', 'backlink data', 'AI visibility check', 'real search data', 'dataforseo'); not just internal jargon.

3 / 3

Distinctiveness Conflict Risk

Clear niche scoped to the DataForSEO MCP server with product-name triggers, making conflict with other skills unlikely; the top anchor match.

3 / 3

Total

12

/

12

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.

Validation15 / 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
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.