Name: dataforseo
Rating: 56.8 (1 reviews)
Author: membranedev

dataforseo

DataForSEO integration. Manage Organizations, Leads, Projects, Users, Goals, Filters. Use when the user wants to interact with DataForSEO data.

Quality

65%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/dataforseo/SKILL.md

Quality

Content

63%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 highly actionable with executable CLI commands and a clear connection-state feedback loop, but it carries redundant action listings and inlines bulk API reference that should be split into a separate file.

Suggestions

Move the 20-row "Popular actions" table (and the "DataForSEO Overview" bullet list) into a referenced ACTIONS.md, keeping only a few representative examples inline in SKILL.md.

De-duplicate the action catalog: the "DataForSEO Overview" nested bullets and the "Popular actions" table list overlapping actions — keep one and link to the other.

Add one concrete end-to-end example that runs a real DataForSEO action with actual parameters (e.g., fetching backlinks for a domain) so the actionability gap closes.

Dimension	Reasoning	Score
Conciseness	The CLI command sections are tight, but the "what is DataForSEO" intro and a duplicate action listing (the "DataForSEO Overview" bullets plus the 20-row "Popular actions" table) are unnecessary token weight that could be trimmed.	3 / 5
Actionability	Copy-paste ready commands cover the common cases (login, connection ensure, action list/run, request proxy) with a full flag table, but no example invokes a real DataForSEO action with concrete parameters beyond the generic '{"key": "value"}'.	4 / 5
Workflow Clarity	A clear install → authenticate → connect → poll-until-READY → search → run sequence exists with a real feedback loop on connection state (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR), but the referenced "Step 2" is unlabeled and action-run error handling is absent.	4 / 5
Progressive Disclosure	Section headers are well organized, but no bundle files exist and the ~20-row action reference table plus overview bullets are inlined content that belongs in a separate reference file rather than SKILL.md.	3 / 5
	Total	14 / 20 Passed

Description

67%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 answers both what and when and is bound to a distinctive named service, but relies on a repetitive single verb and lacks the task-oriented trigger terms (rankings, backlinks, SERP) a user would naturally say.

Suggestions

Vary the action verbs beyond the repeated "Manage" (e.g., "Create and track Organizations, manage Leads and Projects, configure Users, Goals, and Filters").

Add concrete trigger phrases users actually say, e.g. "Use when the user wants keyword rankings, backlinks, SERP data, or competitor analysis from DataForSEO."

Reference the SEO tasks (search volume, keyword ideas, on-page audits) so the skill triggers on task-oriented language rather than only the brand name.

Dimension	Reasoning	Score
Specificity	"Manage Organizations, Leads, Projects, Users, Goals, Filters" lists several concrete resource types, but the single repeated verb "Manage" applied to nouns is a minor gap versus distinct concrete operations.	4 / 5
Completeness	Both "what" (manage Organizations, Leads, Projects, Users, Goals, Filters) and "when" ("Use when the user wants to interact with DataForSEO data") are present, but the trigger clause is generic rather than concrete trigger phrases.	4 / 5
Trigger Term Quality	The natural keyword "DataForSEO" appears ("DataForSEO integration", "interact with DataForSEO data"), but common task-oriented synonyms users would say (keyword rankings, backlinks, SERP, SEO data) are missing.	3 / 5
Distinctiveness Conflict Risk	Naming a specific third-party service (DataForSEO) gives it a clear niche with minimal conflict risk, though a generic "interact with DataForSEO data" trigger leaves minor overlap with other SEO skills.	4 / 5
	Total	15 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/dataforseo/SKILL.md
Commit: f484c82

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.