SEO keyword research using the DataForSEO API. Perform keyword analysis, YouTube keyword research, competitor analysis, SERP analysis, and trend tracking. Use when the user asks to: research keywords, analyze search volume/CPC/competition, find keyword suggestions, check keyword difficulty, analyze competitors, get trending topics, do YouTube SEO research, or optimize landing page keywords. Requires a DataForSEO API account and credentials in .env file.
Security Analysis
high confidenceThe skill appears to implement a legitimate DataForSEO client and workflows, but the package metadata omits the required credentials and the runtime writes files to the current working directory — these mismatches warrant caution before installing or running it.
Name, description, and code consistently implement DataForSEO keyword, SERP, and trends functionality. The functions, modules, and API calls match the stated purpose.
Runtime instructions are mostly scoped to calling DataForSEO endpoints and saving results. The SKILL.md tells the agent to install dependencies, create a .env with DATAFORSEO_LOGIN/PASSWORD, import and run functions from scripts/main.py, and auto-saves JSON summaries to a results/ directory. This behavior matches the stated purpose but the skill will create many timestamped files in the current working directory by default.
There is no formal install spec in registry metadata (instruction-only), but SKILL.md instructs running pip install -r scripts/requirements.txt. No external download URLs or extract steps are present. Review scripts/requirements.txt before running pip to confirm which packages will be installed.
The code requires DataForSEO credentials (DATAFORSEO_LOGIN and DATAFORSEO_PASSWORD loaded from a .env) and will fail without them. However, the registry metadata lists no required env vars or primary credential — this mismatch is misleading. Requiring only DataForSEO credentials is proportionate to the purpose, but the omission in metadata and the use of a .env file should be called out.
The skill does not request always:true, does not modify other skills, and does not request system-wide privileges. It does persist API responses to disk under results/ in the current working directory; this is expected for a data-collection tool but has privacy implications.
Guidance
Before installing or running this skill: - Confirm the source/author: the homepage is missing and the owner id is opaque; prefer skills with a trusted origin. - Expect to provide DataForSEO credentials (DATAFORSEO_LOGIN and DATAFORSEO_PASSWORD) via a .env in the project root. Do NOT put other secrets there. If you must use real credentials, consider creating a limited/test DataForSEO account and rotate credentials after use. - Review scripts/requirements.txt and consider installing dependencies in an isolated virtualenv or sandbox to avoid affecting your system packages. - Understand that the skill auto-saves API responses to a results/ directory in the current working directory; these files can include queries and results you may consider sensitive — run in a directory you control and inspect saved JSONs before sharing. - Because registry metadata does not declare the required env vars, treat that as a red flag: ask the publisher to update metadata or provide provenance before trusting automation that will read credentials and make network calls.
Latest Release
v1.0.0
Initial release — 25+ DataForSEO API functions for keyword research, SERP analysis, competitor analysis, and trend tracking
More by @adamkristopher
Published by @adamkristopher on ClawHub
