executing-plans
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
semantic-coreСобирать семантическое ядро для SEO или рекламы через Wordstat: интенты, кластеризация, минус-слова, структура страниц и кампаний. Использовать для нового ядра, группировки запросов или проектирования поискового спроса.
Independent GitHub snapshot · Automated classification · Original documentation governs
Use when the user asks to build a keyword core, cluster semantics, prepare SEO structure, or prepare ad campaign groups from demand.
Ask only for missing essentials:
workspace_project_id if the result should be saved.search_tools and get_tool_schema before Wordstat calls.client_login or connection_id.get_provider_context.wordstat_top_requests.Before clustering or formatting the final result, read the relevant bundled references:
references/clustering-rules.md for cluster and campaign boundaries;references/intent-and-minus-words.md for intent and negative-keyword decisions;references/output-format.md for the deliverable structure.Use measured numbers only with the exact source phrase, returned phrase, section, region, devices and observed period. In embedded chat use typed observations. Zero is a measurement; missing or failed data is N/A. YES/NO is not frequency. Keep unmeasured expansion ideas separate. Do not claim website analysis without reading it. Frequency alone does not prove conversion potential. List missing sources explicitly; advice on supplied data does not require a paid refresh.
Return clusters, representative phrases, intent, recommended page/campaign, minus words, and validation notes. Mark estimates clearly when Wordstat data is unavailable.