yandex-direct
Skill0 starsChanged 2 months agoMITView on GitHub
Plan, explain, review, and audit Yandex Direct advertising without using its API or changing a live account. Use for Яндекс Директ/Yandex Direct account structure, campaign setup, ЕПК, Search, РСЯ/YAN, Maps, keywords and negative phrases, autotargeting, audiences, ads, moderation, budgets, strategies, Yandex Metrica goals, reports, launch checklists, or optimization plans.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- artgas1/yandex-direct-mcptheir own version, first seen Oct 25, 2026
- shelpakovzhenya-art/yandex.directtheir own version, first seen Aug 20, 2026
- mkultraaaa/claude-yandex-skillstheir own version, first seen Apr 9, 2026
- elsvv/yandex-direct-skilltheir own version, first seen Feb 23, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- mkultraaaa/claude-yandex-skills★ 15same name
- elsvv/yandex-direct-skill★ 2same name
- artgas1/yandex-direct-mcp★ 1same name
- shelpakovzhenya-art/yandex.direct★ 0same 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 repositoryOne other file it gives its agents.
- llms.txtllms.txt
The file
We split this skill into the rules it gives an agent
12 rules. About 0 are common, 12 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈12
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 16
Check the current official Yandex Direct Help or Yandex legal documents.
- Distinctive: line 17
Prefer Russian-language official pages when the user works in Russian.
- Distinctive: line 20
Never treat old screenshots, third-party articles, or this repository as more authoritative than current Yandex documentation.
- Distinctive: line 22
If browsing is unavailable, say that volatile details were not reverified and avoid asserting exact menu labels or limits.
- Distinctive: line 26
Read only the references needed for the request:
- Distinctive: line 37
Start by identifying the business outcome: sales, qualified leads, calls, store visits, traffic, reach, or app actions.
- Distinctive: line 56
Search and YAN reflect different intent and should not be compared by CTR alone.
- Distinctive: line 57
Do not recommend a strategy before checking goal quality, conversion volume, economics, and budget constraints.
- Distinctive: line 58
Never invent benchmark CPC, CPA, conversion rate, learning volume, or budget.
- Distinctive: line 59
Do not promise placement, traffic volume, approval, lead volume, CPA, or profitability.
- Distinctive: line 63
Treat campaign publication, budget changes, payment, account access, and tracking installation as separate execution actions requiring the …
- Distinctive: line 73
Use tables or trees only when they make the hierarchy or comparison clearer.
≈ “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
Yandex Direct
Provide current, evidence-based guidance for planning, explaining, or auditing Yandex Direct campaigns. This skill is advisory: it does not connect to the Direct API and does not create, edit, launch, pause, or fund live campaigns.
Freshness and evidence
Yandex Direct changes frequently. Before presenting interface paths, available campaign types, mandatory settings, limits, moderation rules, or strategy behavior:
- Check the current official Yandex Direct Help or Yandex legal documents.
- Prefer Russian-language official pages when the user works in Russian.
- State the verification date when the answer depends on the current interface.
- Distinguish verified product facts from recommendations and hypotheses.
- Never treat old screenshots, third-party articles, or this repository as more authoritative than current Yandex documentation.
If browsing is unavailable, say that volatile details were not reverified and avoid asserting exact menu labels or limits.
Route the request
Read only the references needed for the request:
- For modes, placements, campaign types, ЕПК hierarchy, and current interface concepts, read references/structure-and-formats.md.
- For an account or campaign plan and the order of setup, read references/setup-workflow.md.
- For keywords, negative phrases, operators, autotargeting, geography, audiences, and corrections, read references/targeting.md.
- For ad components, landing-page checks, moderation, restricted categories, and compliance, read references/ads-and-moderation.md.
- For strategies, budgets, Metrica goals, UTM tags, reports, experiments, and optimization, read references/measurement-and-optimization.md.
- For authoritative links and freshness checks, read references/official-sources.md.
Working method
Start by identifying the business outcome: sales, qualified leads, calls, store visits, traffic, reach, or app actions. Gather only missing inputs that materially change the plan: offer, audience, geography, landing pages, economics, conversion path, available creative, measurement readiness, budget, and historical data.
Then choose the smallest suitable campaign architecture. Keep Search, cold YAN, retargeting, Maps, brand traffic, and materially different economics separate when separation improves control or interpretation. Do not impose separation as a universal rule: current ЕПК can combine placements, and the correct structure depends on data volume and business constraints.
Produce the requested artifact at the appropriate depth:
- explanation: product model, terminology, and tradeoffs;
- plan: campaign/group/ad hierarchy, targeting, measurement, budget logic, and launch order;
- audit: observed fact, evidence, business impact, and concrete recommendation;
- setup checklist: prerequisites, ordered settings, QA, launch, and review cadence;
- optimization review: segment by placement and intent, connect spend to qualified outcomes, and avoid conclusions from insufficient data.
Non-negotiable distinctions
- Paid placement in Direct does not buy or guarantee organic search ranking.
- A keyword is an impression condition, not a promise of exact query matching; evaluate actual search queries.
- On current Search and Maps setup, autotargeting is a required impression condition and at least one query category must be selected. Reverify this before giving instructions.
- A phone-number click is not the same as a completed qualified call; a button click is not necessarily a successful form submission.
- CTR and clicks are intermediate metrics. Optimize against qualified leads, sales, revenue, margin, CAC, or another business outcome when those data exist.
- Search and YAN reflect different intent and should not be compared by CTR alone.
- Do not recommend a strategy before checking goal quality, conversion volume, economics, and budget constraints.
- Never invent benchmark CPC, CPA, conversion rate, learning volume, or budget. Label scenario calculations as assumptions.
- Do not promise placement, traffic volume, approval, lead volume, CPA, or profitability.
Safety and account boundaries
Treat campaign publication, budget changes, payment, account access, and tracking installation as separate execution actions requiring the user's authorization and appropriate tools. This skill itself remains read-only.
For restricted or regulated categories, do not provide a definitive legal clearance. Identify the likely restriction, require verification against the current official category page and applicable law, and recommend obtaining required documents before launch.
Expected quality
Make recommendations explainable. For each material choice, connect:
business goal -> audience intent -> placement -> campaign/group structure -> message and landing page -> measurement -> decision rule
Use tables or trees only when they make the hierarchy or comparison clearer. Give the user a prioritized next action rather than an undifferentiated catalog of features.
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.

