メニュー
This skill should be used when the user asks to "verify DataForSEO connection", "check DataForSEO MCP", "test DataForSEO setup", "is DataForSEO working", or needs to confirm that the DataForSEO MCP integration is operational.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/Agents-Store/claude-plugins --skill setupコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
This skill should be used when the user reports a problem with macstack-dev or the MACSTACK standard — "this skill did the wrong thing", "the schema is missing a field", "the passport for X is wrong", "send macstack feedback", "improve the schema based on my edit", "fix the macstack plugin" — and the fix must land in the right source (plugin, schema repo, or registry repo).
This skill should be used when the user asks to "set up Infisical for this project", "create .infisical.json", "pull the env keys", "wire the env", "sync secrets", or scaffold-project reaches the env step. Creates .infisical.json, pulls .env.prod/.env.dev, ensures every key from macstack.json resources.accesses exists, and installs the mandatory secrets scripts and commands.
This skill should be used when the user asks to "scaffold the project from macstack.json", "create the project working files", "generate project files from the spec", "build the project from macstack.json", or after a macstack.json is validated and the working tree must be built. Creates project files strictly in the prototype → stack plugins → dev plugins order.
SOC 職業分類に基づく
SKILL.md を表示中
| name | setup |
| description | This skill should be used when the user asks to "verify DataForSEO connection", "check DataForSEO MCP", "test DataForSEO setup", "is DataForSEO working", or needs to confirm that the DataForSEO MCP integration is operational. |
Verify that the DataForSEO MCP connection is working correctly.
.mcp.json or user settings)Run a lightweight read operation to verify connectivity:
Tool: mcp__dataforseo__serp_locations
Input: { "country_iso_code": "US" }
Expected result: Returns a list of US locations without errors.
Run a keyword data request to verify credentials work:
Tool: mcp__dataforseo__dataforseo_labs_google_keyword_overview
Input: { "keywords": ["test"], "location_name": "United States", "language_code": "en" }
Expected result: Returns keyword metrics (search_volume, cpc, competition).
| Symptom | Cause | Fix |
|---|---|---|
| Connection refused | MCP server not started | Check Node.js version (node -v must be >= 20) |
| 401 Unauthorized | Wrong credentials | Verify DATAFORSEO_USERNAME and DATAFORSEO_PASSWORD env vars |
npx error | Package not found | Run npx -y dataforseo-mcp-server@latest manually to test |
| Timeout | Network or firewall | Check internet connectivity to api.dataforseo.com |
| Empty results | Account has no credits | Check balance at app.dataforseo.com |
DataForSEO uses username/password authentication (not API keys):
DATAFORSEO_USERNAME — your account email (e.g., user@example.com)DATAFORSEO_PASSWORD — your account passwordObtain credentials at app.dataforseo.com.
DATAFORSEO_USERNAME and DATAFORSEO_PASSWORD in your environment)