semantic-core
Skill20 starsChanged 3 days agoMITView on GitHub
Собирать семантическое ядро для SEO или рекламы через Wordstat: интенты, кластеризация, минус-слова, структура страниц и кампаний. Использовать для нового ядра, группировки запросов или проектирования поискового спроса.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- Pupok462/open-geotheir own version, first seen Oct 24, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- Pupok462/open-geo★ 28same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository60 other files it gives its agents.
- AGENTS.mdAGENTS.md
- ai-markers-removeSkill
- article-reviserSkill
- article-writerSkill
- avito-adsSkill
- avito-businessSkill
- demand-researchSkill
- export-ad-reportsSkill
- human-editorial-polishSkill
- lidfly-connection-doctorSkill
- lidfly-knowledge-maintainerSkill
- lidfly-page-migrationSkill
- lidfly-site-commerceSkill
- lidfly-support-escalationSkill
- max-postingSkill
- mcp-v3-provider-contextSkill
- restaurant-yandexSkill
- semantic-coreSkill
- seo-optimizerSkill
- serp-monitorSkill
- telegram-postingSkill
- video-article-writerSkill
- vk-ads-campaign-builderSkill
- vk-social-communitySkill
- workspace-project-managerSkill
- yandex-direct-campaign-builderSkill
- yandex-edaSkill
- yandex-metrikaSkill
- yandex-productsSkill
- yandex-webmasterSkill
- youtube-video-seoSkill
- ai-markers-removeSkill
- article-reviserSkill
- article-writerSkill
- avito-adsSkill
- avito-businessSkill
- demand-researchSkill
- export-ad-reportsSkill
- human-editorial-polishSkill
- lidfly-connection-doctorSkill
- lidfly-knowledge-maintainerSkill
- lidfly-page-migrationSkill
- lidfly-site-commerceSkill
- lidfly-support-escalationSkill
- max-postingSkill
- mcp-v3-provider-contextSkill
- restaurant-yandexSkill
- seo-optimizerSkill
- serp-monitorSkill
- telegram-postingSkill
- video-article-writerSkill
- vk-ads-campaign-builderSkill
- vk-social-communitySkill
- workspace-project-managerSkill
- yandex-direct-campaign-builderSkill
- yandex-edaSkill
- yandex-metrikaSkill
- yandex-productsSkill
- yandex-webmasterSkill
- youtube-video-seoSkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 8 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use when the user asks to build a keyword core, cluster semantics, prepare SEO structure, or prepare ad campaign groups from demand.
- Distinctive: line 12
Ask only for missing essentials:
- Very specific: line 23
Use search_tools and get_tool_schema before Wordstat calls.
- Distinctive: line 35
Check seasonality and region when relevant.
- Distinctive: line 36
Remove irrelevant intents and collect minus words.
- Distinctive: line 41
Before clustering or formatting the final result, read the relevant bundled references:
- Distinctive: line 49
Use measured numbers only with the exact source phrase, returned phrase, section, region, devices and observed period.
- Distinctive: line 52
Keep unmeasured expansion ideas separate.
- Distinctive: line 58
If the campaign is not returned by the API (for example a statistics-only «Баннер на поиске» or Campaign Wizard object), still provide …
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Semantic Core
Use when the user asks to build a keyword core, cluster semantics, prepare SEO structure, or prepare ad campaign groups from demand.
Inputs
Ask only for missing essentials:
- product/service and geography;
- site or planned landing pages;
- business goal and target action;
- exclusions and legal restrictions;
- whether output is for SEO, ads, or both;
workspace_project_idif the result should be saved.
MCP Rules
- Use
search_toolsandget_tool_schemabefore Wordstat calls. - Wordstat does not need
client_loginorconnection_id. - For provider-specific follow-up, resolve scope through
get_provider_context.
Workflow
For keywords for an existing campaign, first read its settings with get_campaigns,
current groups, keywords, ads and the landing page. Use the returned platform rules
to explain API visibility; an empty response does not prove that the campaign is absent.
- Generate seed queries.
- Expand through
wordstat_top_requests. - Check seasonality and region when relevant.
- Remove irrelevant intents and collect minus words.
- Cluster by user intent, not only lexical similarity.
- Produce SEO page structure and/or ad group structure.
- Save only when requested, to the exact requested file, sheet or document using an available tool. For a Workspace destination, also resolve project scope; a connected Workspace does not imply permission to save there.
Before clustering or formatting the final result, read the relevant bundled references:
references/clustering-rules.mdfor cluster and campaign boundaries;references/intent-and-minus-words.mdfor intent and negative-keyword decisions;references/output-format.mdfor the deliverable structure.
Output
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.
If the campaign is not returned by the API (for example a statistics-only «Баннер на поиске» or Campaign Wizard object), still provide ready-to-paste keywords and negative keywords. Explain the observed limitation and the manual addition path in the Yandex Direct web interface; never claim that phrases were added through the API.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

