SkillFoxx

Yandex ecosystem plugin marketplace

claude-yandex-skills

Fifteen Claude Code plugins for Yandex services sharing one OAuth token: Metrica, Webmaster, Wordstat, Direct, Disk, Tracker and more

  • 4 ★ on the repository
  • Last commit
  • MIT
Plugin

Broad access

Why this level

  • A single token opens mail, disk, calendar, ads and the task tracker at once
  • The Direct plugin, once activated, can change ad campaigns and spend budget
  • The token is stored on disk in a file rather than a system secrets store
All reasons and checks
Russian stack

atomachinskiy/claude-yandex-skillsAuthor:atomachinskiy

Install

Works in

Manual install

git clone --depth 1 https://github.com/atomachinskiy/claude-yandex-skills.git ~/.claude/yandex-skills-local

The recommended README path: the agent clones and wires up the plugins itself, the user only approves OAuth in the browser.

Access and checks

How we review

Broad accessThe tool can change data, run commands or handle secrets.

  • A single token opens mail, disk, calendar, ads and the task tracker at once
  • The Direct plugin, once activated, can change ad campaigns and spend budget
  • The token is stored on disk in a file rather than a system secrets store

This is third-party code. Review the repository files before installing.

What it does

The project is packaged as a Claude Code marketplace: the yandex-auth plugin runs a one-time implicit OAuth flow in the browser and stores the token in ~/.claude/secrets/yandex-app.json, and the other fourteen service plugins read that shared token and each call their own Yandex API. Each plugin is a skill with its own bash and python scripts plus reference docs. At the time of review the author marks Metrica, Webmaster, Wordstat, Disk and Calendar as fully working, while Direct, Audience, Telemost, 360 Admin, the Alice bot platform and Messenger are marked as probe status, each needing a separate OAuth scope or a service enabled on the account.

Who it is for. For people who work with several Yandex services at once and do not want to register a separate OAuth app for each.

Good fit when

  • You need several Yandex services in one agent without separate authorization for each
  • You need Metrica, Webmaster, Wordstat or Disk, which the project marks as working
  • You need a base you can finish wiring up for the remaining Yandex services yourself

Not a fit when

  • You only need one Yandex service: a dedicated plugin or MCP server for it is simpler
  • You need Direct, Audience, Telemost, 360 Admin, the Alice bot platform or Messenger right now: they are probe status and need extra scope setup

Example request

Show weekly site traffic from Yandex Metrica and the list of hosts from Webmaster

Limitations

The project is at version 0.2.0, and the README itself calls that version not final and mentions a possible future public release, even though the repository is already open. Five of the fourteen service plugins work in a limited way or need a separate application and scope setup in the Yandex console. yandex-forms is only partly functional because the public Yandex Forms API is limited. The /plugin slash commands in Claude Code can only be run by the user themselves, not by the agent through the Bash tool.

How to disable. Remove the plugin with /plugin uninstall or delete ~/.claude/yandex-skills-local and the entry in ~/.claude/settings.json, and remove the token from ~/.claude/secrets/yandex-app.json.

FAQ

Do I need a separate token per service?

No, one OAuth flow issues a token that every installed service plugin reuses.

Are all 15 plugins equally functional?

No, the author marks five of the fourteen service plugins as fully working; the rest are probe status or limited.

Discussion

No questions or reviews yet.

All Yandex Direct tools
Russian stack

A marketplace of 22 Claude Code plugins: Yandex Direct, Metrika, Webmaster, Wordstat, SEO crawling, publishing and research

PluginBroad access234
Russian stack

Five cache-first shell skills for Direct, Metrika, Webmaster, Wordstat and Search API, with Claude choosing which one to run

SkillBroad access17

Yandex Metrika skill plugin wrapper

claude-skill-yandex-metrika

Russian stack

A Claude Code plugin bundling a Yandex Metrika skill: traffic, conversions, UTM, search engines and Direct costs, with caching

PluginExtended access
Russian stack

A Codex and Claude Code plugin with skills and MCP for Yandex Direct, Metrika, Wordstat v2, Roistat, amoCRM and Yandex Search API

PluginBroad access21
Russian stack

A Claude plugin marketplace for ad accounts: a zero-setup read-only Direct connector plus full MCP servers for Direct, VK Ads, Metrika and Wordstat

PluginBroad access3

Yandex Direct MCP

yandex-direct-mcp

Russian stack

A Claude Code and Codex plugin for Yandex Direct: a 147-tool MCP server, OAuth, and skills for ad copy and stats analysis

PluginBroad access14

README in short

The Russian README shows the architecture: one Yandex OAuth app with a broad scope set, the yandex-auth plugin stores the token, and the other plugins read it through a shared common.sh. It gives a status table for all fifteen plugins, install instructions via git clone with a manual OAuth script run, an alternative via /plugin marketplace add, and the plugins directory layout with SKILL.md, config and scripts in each.

README badge

Report a problem