CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

dataforseo

Keyword & SERP research via the DataForSEO API — search volume, competition, CPC, keyword ideas for naming/SEO decisions

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

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/dataforseo/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

An exemplary lean, actionable skill body that teaches only the non-obvious judgment (result interpretation, cost etiquette) and provides runnable commands. Its weaknesses are external: the helper script it depends on is missing from the bundle, and there is no error-handling guidance for API failures.

Suggestions

Ship the referenced helper script in the skill bundle (e.g. scripts/dataforseo.py) — the body's entire usage section depends on it, but it is absent from the reviewed files, so the commands cannot run as shipped.

Add brief error-recovery guidance for API failures (e.g. what to do on auth errors, insufficient balance, or per-call errors, and whether/how to retry) to close the workflow feedback-loop gap.

Clarify the helper's actual location: the given path (~/.claude/.bootstrap-dir/skills/dataforseo/dataforseo.py) is environment-specific and unverifiable; a bundle-relative path would make the reference resolvable.

DimensionReasoningScore

Conciseness

Lean and efficient throughout: no re-explanation of concepts Claude already knows, and the "Reading the results" heuristics ("Zero / n/a volume on every candidate is itself the answer", "Wrong-intent volume is a trap") are judgment calls Claude could not derive on its own — every token earns its place.

5 / 5

Actionability

Copy-paste-ready commands with real arguments ("python3 \"$DFS\" volume \"claude code\" \"coding agent\"") plus an auth check, options, and concrete cost figures, but the referenced helper dataforseo.py is not present in the reviewed bundle, so the commands cannot actually run as shipped — a gap beyond fully executable.

4 / 5

Workflow Clarity

The sequence (whoami auth check → query → interpret results) is clear with an explicit validation checkpoint for the batch operation ("Check whoami for balance before large runs"), but there is no error-recovery guidance for failed or errored API calls, keeping it below the feedback-loop anchor.

4 / 5

Progressive Disclosure

Sections are well-organized and the skill is short enough to live in one file, but its single referenced file — "dataforseo.py in this skill folder" — does not exist in the reviewed bundle (no scripts/, references/, or assets/ directories), so the core reference cannot be verified as real.

3 / 5

Total

16

/

20

Passed

Description

66%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 specific, well-scoped description that names its API and lists concrete data capabilities, with good natural trigger terms. Its main weakness is the missing explicit use-when guidance inside the description field itself, which caps completeness.

Suggestions

Add an explicit trigger clause to the description field (e.g. "Use when choosing a product/repo/domain name, sizing keywords, or checking search demand and WebSearch isn't enough") — the frontmatter's separate when-to-use field carries this today, but the description alone does not.

Enumerate the SERP-side capabilities in the description (e.g. "see who ranks, ranked keywords for a domain, competitor domains") so "SERP research" is concrete rather than implied.

DimensionReasoningScore

Specificity

Lists several concrete capabilities — "search volume, competition, CPC, keyword ideas" — matching the several-specific-actions anchor, but SERP-side capabilities (who ranks, ranked keywords, competitor domains) are only implied by "SERP research" rather than enumerated, leaving minor coverage gaps.

4 / 5

Completeness

The "what" is clear and concrete, but the description field contains no explicit "Use when..." clause — "for naming/SEO decisions" only weakly implies when — which caps completeness at 3 per the guideline (the separate frontmatter when-to-use field covers this, but the description itself does not).

3 / 5

Trigger Term Quality

Natural phrases users would say — "keyword" research, "search volume", "SERP", "SEO", "CPC" — are present with good coverage, but common variations like "search demand" or bare "competitor research" are missing.

4 / 5

Distinctiveness Conflict Risk

"DataForSEO API" and "SERP research" carve a distinct niche with a named vendor, leaving only minor overlap risk with generic SEO/web-research skills.

4 / 5

Total

15

/

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

alinaqi/maggy

Path

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