菜单
Build, audit, launch, and optimize Yandex Direct campaigns through LidFly MCP v3 with Wordstat, Metrika, provider context, resolve_campaign_scope, workspace_project_id, modern add_unified_campaign/add_responsive_ad workflows, and strict write guardrails.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Work with Avito Ads through LidFly MCP v3: account discovery, campaigns, groups, budgets, statistics, agency/access/legal operations, 9-digit account_id validation, and read-preflight-write-reread guardrails.
Export advertising reports from Yandex Direct, Yandex Metrika, VK Ads, and Avito Ads through LidFly MCP v3 into connected Google Sheets, Google Docs, or Google Drive files, including verified tables and public creative images. Use when the user asks to export, save, append, or update advertising statistics in a Google file.
Build, audit, and optimize VK Ads campaigns through LidFly MCP v3 with connection_id/client_id provider context, manual VK user-filter limits, campaign scope resolution, creative preflight, statistics, and safe write workflows.
Analyze Yandex Metrika through LidFly MCP v3: counter discovery, goals, UTM reports, Direct attribution, CPA/conversions, period comparisons, Workspace provider entities, and counter_id scope without client_login.
Work with Avito Ads through LidFly MCP v3: account discovery, campaigns, groups, budgets, statistics, agency/access/legal operations, 9-digit account_id validation, and read-preflight-write-reread guardrails.
Export advertising reports from Yandex Direct, Yandex Metrika, VK Ads, and Avito Ads through LidFly MCP v3 into connected Google Sheets, Google Docs, or Google Drive files, including verified tables and public creative images. Use when the user asks to export, save, append, or update advertising statistics in a Google file.
| name | yandex-direct-campaign-builder |
| description | Build, audit, launch, and optimize Yandex Direct campaigns through LidFly MCP v3 with Wordstat, Metrika, provider context, resolve_campaign_scope, workspace_project_id, modern add_unified_campaign/add_responsive_ad workflows, and strict write guardrails. |
Use for Yandex Direct campaign creation, audit, optimization, budgets, keywords, negative keywords, responsive ads, search queries, Wordstat, and Metrika-linked decisions.
search_tools({ provider: "yandex", query }).get_tool_schema before each new tool.get_provider_context({ provider: "yandex", query? }).resolve_campaign_scope({ provider: "yandex", query, workspace_project_id? }).scope_arguments into Direct calls.call_tool; write through call_write_tool.Direct tools use connection_id and optional client_login. Metrika tools use counter_id and optional connection_id, not client_login.
Use modern managed campaigns by default:
add_unified_campaign
-> add_adgroup/add_adgroups with adgroup_type: UNIFIED_AD_GROUP
-> add_keywords/add_keywords_batch
-> add_responsive_ad
-> manage_ads action: moderate only after explicit confirmation
Legacy add_campaign, add_ad, add_ads are compatibility-only for old text scenarios. If used, say clearly that it is a legacy TEXT_AD path and reread actual ad Type after creation.
workspace_project_id.get_campaigns with useful states and field_names.get_adgroups, get_ads or get_responsive_ads, get_keywords.get_autotargeting for categories.get_campaign_stats, get_search_queries with period and attribution.wordstat_* without client_login or connection_id.After confirmed work, save decisions, documents, analytics, campaign snapshots, or follow-up tasks only with resolved workspace_project_id. Use workspace_prepare_project_scope if uncertain.
When the user asks to export a Direct report to Google Sheets or Google Docs, keep this skill for campaign scope and report reads, then hand the verified Google write and reread to $export-ad-reports.