Yandex Metrika Assistant skill

A skill and condensed Yandex Metrika API documentation for an agent: reports, Logs API, counter management, OAuth without leaking the token into chat

  • 16 ★ on the repository
  • Last commit
  • MIT
Skill

Extended access

Why this level

  • The OAuth token can grant rights to change counters and goals, not just read data
  • The Logs API exports raw visitor-level site data
All reasons and checks
Russian stack

horosheff/yandex-metrika-assistant

Install

In your terminal, with SkillFoxx CLI

npx skillfoxx add skills/yandex-metrika-assistant

Detects the agents on your machine, shows the access level and pins the version.

Other ways to install

Access and checks

How we review

Extended accessThe tool runs code or makes network calls and only reads external data.

  • The OAuth token can grant rights to change counters and goals, not just read data
  • The Logs API exports raw visitor-level site data

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

What it does

The repository is built as an OpenClaw skill, but at its core it is a SKILL.md decision map: which Metrika API endpoint to call for a given user request, how to avoid confusing visit counters ym:s: with pageview counters ym:pv:, where to get an OAuth token and how not to ask for it again once it is saved. The docs/ folder condenses the official API: base URL and request structure, OAuth, quotas, the Reporting API (stat), the Logs API with a create-status-download-clean workflow, data import, and a management quick start. A user-intents matrix maps typical user phrasing ("where is traffic coming from", "goals", "compare periods") to specific API methods.

Who it is for. For site owners and marketers who want Metrika reports through plain chat requests, and for OpenClaw integrators.

Good fit when

  • You want traffic, goal and source reports without opening the Metrika interface
  • You need a raw-data export workflow through the Logs API
  • You work in OpenClaw and want a ready plugin with token configuration

Not a fit when

  • You need visualized reports rather than the agent's text answers
  • You are not on OpenClaw: token configuration via openclaw.plugin.json will need adapting

Example request

Show daily visits for the last 7 days and a traffic source summary

Limitations

The skill is designed and tested for the OpenClaw platform with its openclaw.plugin.json plugin format; for other agents the token has to be passed manually via the YANDEX_METRIKA_OAUTH_TOKEN environment variable. You need a Yandex OAuth token with Metrika access scopes: stats, counters, and optionally spend and offline data. The author explicitly asks not to forward the token over Telegram.

How to disable. In OpenClaw, disable the yandex-metrika-assistant plugin; in other agents, delete the skill folder from your skills directory.

FAQ

Does it work outside OpenClaw?

The SKILL.md and docs are generic, but token configuration through the plugin targets OpenClaw; other agents need the environment variable instead.

How does the agent avoid mixing up visits and pageviews?

The SKILL.md explicitly warns not to confuse the ym:s: (visits) and ym:pv: (pageviews) counters when picking metrics.

Discussion

No questions or reviews yet.

Russian stack

Three Agent Skills in one repository: calling the Yandex Direct, Metrica and Wordstat APIs directly via JSON

SkillBroad access1Repository stars
Russian stack

A Claude Code skill for Yandex Metrica built on bash scripts over curl: preset reports, goals, counters and raw log exports

SkillExtended access1Repository stars

Yandex Metrika search phrases: SEO skill

Yandex Metrika Search Phrases

Russian stack

A skill that pulls real search phrases from Yandex Metrika with visits, bounce rate and time on site into CSV and Markdown

SkillMinimal access1Repository stars

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 minimalist Python MCP with 12 read-only tools using the correct OAuth header, paired with a skill that carries the period-comparison methodology

MCP serverExtended access4Repository stars

Alternatives

Tools by other authors for the same tasks.

README in short

The README explains the repository's purpose: a SKILL.md for endpoint selection, condensed API docs in docs/, and an OpenClaw plugin manifest with the token and options. It covers the audience (site owners, automation developers, OpenClaw integrators), reporting, management and import capabilities, compliance with OpenClaw's skill format requirements, HTTP and PowerShell examples, and the project layout. It lists a Telegram support channel and asks not to forward the token there.

README badge

Original SKILL.md

---
name: yandex-metrika-assistant
description: OpenClaw + Яндекс.Метрика API — stat/Logs/management, OAuth, presets, UTM, цели, CSV, квоты; плагин yandex-metrika-assistant.
homepage: https://github.com/Horosheff/yandex-metrika-assistant
---

# Яндекс.Метрика API — заточка под OpenClaw

Плагин: yandex-metrika-assistant (openclaw.plugin.json в этой папке).
Цель: ноль сюрпризов — сначала конфиг и секреты, потом правильный endpoint, без выдуманных метрик и без утечки токена.

## Онбординг человека (порядок ответов агента)

Если токена еще нет: дай ссылку на docs/INSTALL-FOR-HUMANS-RU.md, перечисли нужные галочки в приложении Яндекс OAuth, укажи канал поддержки и не проси токен в открытую.

После того как ключ добавлен: не проси продиктовать токен повторно, предложи 3-5 коротких вариантов с чего начать.

Report a problem