Yandex Metrica Skill for Claude Code

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

  • 1 ★ on the repository
  • Last commit
Skill

Extended access

Why this level

  • Reads traffic and conversion data, including commercially sensitive statistics
  • The token is requested with the metrika:write scope, though the README documents only reporting scenarios
All reasons and checks
Russian stack

elsvv/yandex-metrica-skill

Install

In your terminal, with SkillFoxx CLI

npx skillfoxx add skills/yandex-metrica-skill-for-claude-code

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.

  • Reads traffic and conversion data, including commercially sensitive statistics
  • The token is requested with the metrika:write scope, though the README documents only reporting scenarios

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

What it does

The skill gives Claude Code a set of bash scripts over curl for the Yandex Metrica API. check_connection.sh verifies the token and lists counters, counters.sh works with counters, stats.sh builds reports either from ready presets (traffic, sources, geo, content, technology) or from custom metrics, dimensions and dates, goals.sh reads goals, and logs.sh runs the full Logs API cycle: evaluating volume, creating the request, downloading a multi-part file and cleaning up processed logs. Coverage is also described for the Management API: counters, goals, filters, operations, grants, labels, segments, user parameters. The scripts are meant to run strictly via bash with absolute paths, not sourced from zsh.

Who it is for. For people who want Yandex Metrika reports right inside Claude Code without a separate MCP server, via simple bash scripts.

Good fit when

  • You want quick preset reports on traffic, sources, geography, content or technology
  • You need a raw visit log export via the Logs API
  • You prefer a light bash-and-curl skill over running a separate MCP server

Not a fit when

  • You need it on Windows without bash: the scripts assume a unix environment
  • curl, jq and python3 are not on the system: they are needed for requests, formatted output and URL encoding in filters

Example request

Show me the traffic sources report for counter 12345678 for January

Limitations

The repository metadata does not explicitly declare a license, though the README mentions MIT. curl, jq and python3 are required on the system. The token is requested with metrika:read and metrika:write scopes, though the scripts documented in the README are reporting-focused and do not show explicit write calls. Scripts must be run strictly via bash with absolute paths.

How to disable. Delete the skill folder from ~/.claude/skills/yandex-metrica and revoke the OAuth token at oauth.yandex.ru.

FAQ

Are there ready report presets?

Yes, stats.sh supports the traffic, sources, geo, content and technology presets, plus custom metrics and dimensions.

Can raw visit data be exported?

Yes, logs.sh runs the full Logs API cycle: evaluating volume, creating the request, downloading a multi-part file, and cleaning up processed logs.

Discussion

No questions or reviews yet.

Russian stack

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

SkillBroad access17Repository 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 skill and condensed Yandex Metrika API documentation for an agent: reports, Logs API, counter management, OAuth without leaking the token into chat

SkillExtended access16Repository 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
Russian stack

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

SkillBroad access1Repository stars

Yandex SEO audit

yandex-seo-audit

Russian stack

A Claude Code skill for technical SEO audits under Yandex requirements: canonical tags, JSON-LD, robots.txt, favicon and Webmaster diagnostics

SkillExtended access1Repository stars

README in short

The English README describes the skill as a set of scripts for the Yandex Metrica API: counters, reports, goals, raw log export. It gives a table of five scripts with their purpose, example calls for presets and a custom report with metrics and dimensions, and an example of creating a Logs API request. It separately lists coverage of the Management, Reporting and Logs APIs with a link to the full references/api-reference.md. It states the curl, jq and python3 system requirements, a list of skill activation triggers, and the MIT license.

README badge

Original SKILL.md

---
name: yandex-metrica
description: |
  Работа с Yandex Metrica API: аналитика, отчеты, цели, логи.
  Use when the user needs web analytics data from Yandex Metrica,
  traffic stats, conversion reports, goal management, raw log exports,
  counter management, segments, filters, or grants.
  Triggers: метрика, metrica, аналитика, счетчик, визиты, конверсии,
  отчет по трафику, источники трафика, Logs API, экспорт логов.
---

# yandex-metrica

Yandex Metrica API, web analytics: counters, reports, goals, logs export.

## Config

Requires YANDEX_METRICA_TOKEN in config/.env.
See config/README.md for token setup (OAuth, permissions: metrika:read, metrika:write).

## Quick Start

IMPORTANT: Always run scripts with bash prefix and absolute paths from the skill
directory. Scripts use bash-specific features and will not work if sourced from
zsh. Do NOT source scripts/common.sh directly, use the wrapper scripts below.

```bash
# 1. Setup token
bash scripts/get_token.sh --client-id YOUR_CLIENT_ID

# 2. Check connection
bash scripts/check_connection.sh

# 3. List counters
bash scripts/counters.sh --action list

# 4. Get traffic stats
bash scripts/stats.sh --counter 12345678 --preset traffic

# 5. Export raw logs
bash scripts/logs.sh --action create --counter 12345678 --date1 2025-01-01 --date2 2025-01-31
```

## API Overview

Base URL: https://api-metrika.yandex.net

Report a problem