claude-skill-tracker
A Yandex Tracker skill for Claude Code, invoked with /tracker, optionally gathering context from your codebase
- 0 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- The exact capabilities of the /tracker command are not documented, including the scope of write access
- It depends on an external dev-workflow repository whose contents cannot be checked in advance
Install
- Works in
- Services
In your terminal, with SkillFoxx CLI
npx skillfoxx add skills/claude-skill-trackerDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The exact capabilities of the /tracker command are not documented, including the scope of write access
- It depends on an external dev-workflow repository whose contents cannot be checked in advance
This is third-party code. Review the repository files before installing.
What it does
The skill is installed into ~/.claude/skills/tracker and invoked with the /tracker command plus arguments. By default it requires a DEV_WORKFLOW_ROOT variable pointing at a separate dev-workflow repository the skill pulls shared logic from. An optional install.sh with a --deep flag enables deeper codebase context collection when working on issues.
Who it is for. For teams that already have their own dev-workflow repository with shared scripts and want to add a Yandex Tracker skill to it.
Good fit when
- Your team already has a dev-workflow repository to point DEV_WORKFLOW_ROOT at
- You want a simple /tracker command inside Claude Code without a separate MCP server
Not a fit when
- You have no dev-workflow repository, and the README does not explain what should be in it
- You need a self-contained server without a dependency on another external repository
Example request
/tracker show issues in the SUPPORT queue with status OpenLimitations
The README does not explain what the dev-workflow repository must contain or in what format, so the skill's behavior without it is unclear. The README itself is minimal and does not describe the /tracker command's actual capabilities beyond its call form.
How to disable. Delete the ~/.claude/skills/tracker folder.
FAQ
What is DEV_WORKFLOW_ROOT?
An environment variable pointing at a separate dev-workflow repository, the README does not detail its exact contents, only listing it as a requirement for the skill to work.
Can it be installed via a plugin manager?
Yes, if you already have dev-workflow-skills-registry added, with /plugin install tracker@dev-workflow-skills.
Discussion
No questions or reviews yet.
Related
All Yandex Tracker toolsYaTracker: Yandex Tracker skill
YaTracker
A Claude Code skill for Yandex Tracker with a board overview, issue statistics and self-learning memory about your organization's patterns
Yandex Tracker skill on the official Python client
Yandex Tracker Skill
A skill for Claude Code, Codex and Gemini CLI on top of the official yandex_tracker_client package: search, issues, statuses, sprints, bulk edits
Full task-lifecycle skills for Yandex Tracker
yt-bp-claud-code-skills
Seven Claude Code skills that carry a Yandex Tracker issue from plan to merge: estimation, work, review, deploy, tests, merge request
A Claude Code plugin for Yandex Tracker and Wiki backed by the yandex-cli binary: 16 commands with output tuned for agent reading
Yandex Tracker CLI
tracker
The tracker command-line tool for Yandex Tracker with JSON output and a ready SKILL.md workflow for agents
Yandex Tracker MCP with one-click install
yandex-tracker-mcp
A Yandex Tracker MCP server with a .mcpb extension for Claude Desktop that needs no terminal: issues, comments, status transitions and a read-only mode
README in short
A short English README shows installation via git clone into ~/.claude/skills/tracker or a plugin manager, an optional install.sh --deep setup, the /tracker command, and a requirement for the DEV_WORKFLOW_ROOT variable and an installed claude CLI. MIT license.