Skip to content

kandler3/yandex-tracker

v1.1.0MIT

Manage Yandex Tracker issues, queues, comments, attachments, links, worklogs, searches, and bulk changes.

GitHubOpen Website

Yandex Tracker agent skill

ClawHub — Install skills.sh — Install Claude Code — Package Gemini CLI — Package Codex — Package

A skill for working with Yandex Tracker through the Python yandex_tracker_client package.

It supports:

  • reading, creating, updating, and transitioning issues;
  • Tracker Query Language and structured searches;
  • custom fields, comments, attachments, links, and worklogs;
  • queues, users, boards, and sprints;
  • bulk updates, transitions, and queue moves.

Installation

Install the skill from its public GitHub repository with the Vercel Agent Skills CLI:

npx skills add Kandler3/yandex-tracker-skill

The installer detects supported agents and lets you choose the target. You can also select an agent non-interactively, for example:

npx skills add Kandler3/yandex-tracker-skill --skill yandex-tracker --agent codex

OpenClaw users can install the published package from ClawHub:

clawhub install yandex-tracker

Prerequisites

  • An agent runtime that can read filesystem-based skills and execute Python 3.
  • A Yandex account with access to the required Tracker organization and queues.
  • A least-privilege OAuth token with the Tracker scope.
  • The Yandex 360 or Yandex Cloud organization ID.

Install yandex_tracker_client when the runtime does not manage dependencies automatically:

python -m pip install yandex_tracker_client

Setup

1. Get a Yandex OAuth token

Create a token at oauth.yandex.ru with only the permissions needed for Tracker. Avoid broad administrative tokens.

2. Find the organization ID

  • Yandex 360: open Tracker settings, select the organization, and copy its numeric ID.
  • Yandex Cloud: copy the string organization ID from Yandex Cloud Organization Manager.

3. Configure credentials

Store the token and organization ID in the secret or environment mechanism provided by the agent runtime:

TRACKER_TOKEN=your_oauth_token
TRACKER_ORG_ID=12345678

For a Yandex Cloud organization, set TRACKER_CLOUD_ORG_ID instead of TRACKER_ORG_ID. Set exactly one organization ID variable.

Do not put tokens in prompts, generated scripts, or repository files. OpenClaw users can follow the additional OpenClaw configuration.

Structure

skills/yandex-tracker/SKILL.md contains the shared workflow, safety constraints, and a topic index. Detailed instructions live beside it in references/, so an agent loads only the material relevant to the current request. Platform manifests remain at the repository root and all point to this single skill source.

See the skill card for ownership, intended use, dependencies, known risks, outputs, and release evidence.

License

This project is available under the MIT License.

Example requests

Show all issues assigned to me in queue DEV.

Create a critical task in BACKEND titled "Migrate auth to OAuth 2.0".

Close DEV-42 with the comment "Fixed in v3.1" and the fixed resolution.

Group open issues by assignee and summarize the totals.

The agent should execute the required API calls, aggregate related results, and return a concise confirmation or report.