claude-skill-tracker
A Yandex Tracker skill for Claude Code, invoked with /tracker, optionally gathering context from your codebase
Medium risk
We rate an entry medium when the tool runs code, makes network calls or reads project files. Check what exactly it does before installing.
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
In your terminal, with SkillFoxx CLI
npx skillfoxx add skills/claude-skill-trackerDetects the agents on your machine, checks the risk and pins the version.
Other ways to install
Run in a terminal in the project folder
npx skills add vladimirfyodorov/claude-skill-tracker --skill tracker -a claude-code -yThe skills tool installs the current version from the repository. Add the -g flag to use the skill in every project.
Run in a terminal in the project folder
npx skills add vladimirfyodorov/claude-skill-tracker --skill tracker -a cursor -yThe skills tool installs the current version from the repository. Add the -g flag to use the skill in every project.
Run in a terminal in the project folder
npx skills add vladimirfyodorov/claude-skill-tracker --skill tracker -a github-copilot -yThe skills tool installs the current version from the repository. Add the -g flag to use the skill in every project.
Run in a terminal in the project folder
npx skills add vladimirfyodorov/claude-skill-tracker --skill tracker -a codex -yThe skills tool installs the current version from the repository. Add the -g flag to use the skill in every project.
Run in a terminal in the project folder
npx skills add vladimirfyodorov/claude-skill-tracker --skill tracker -a gemini-cli -yThe skills tool installs the current version from the repository. Add the -g flag to use the skill in every project.
Run in a terminal in the project folder
npx skills add vladimirfyodorov/claude-skill-tracker --skill tracker -a cline -yThe skills tool installs the current version from the repository. Add the -g flag to use the skill in every project.
Run in a terminal in the project folder
npx skills add vladimirfyodorov/claude-skill-tracker --skill tracker -a roo -yThe skills tool installs the current version from the repository. Add the -g flag to use the skill in every project.
A fork of Roo Code, same .roo folders.
Run in a terminal in the project folder
npx skills add vladimirfyodorov/claude-skill-tracker --skill tracker -a opencode -yThe skills tool installs the current version from the repository. Add the -g flag to use the skill in every project.
Clone the repository into ~/.claude/skills/tracker with git clone https://github.com/VladimirFyodorov/claude-skill-tracker ~/.claude/skills/tracker, set DEV_WORKFLOW_ROOT, and optionally run install.sh --deep for deeper context.
Other ways from the author
git clone https://github.com/VladimirFyodorov/claude-skill-tracker ~/.claude/skills/trackerDirect install into the Claude Code skills folder.
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.
Security check
- 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
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.
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.
Related
A skills library that gives coding agents a development process: brainstorming, planning, TDD, subagents and code review
Skills for real engineers by Matt Pocock
Skills For Real Engineers
Small composable skills for engineering with agents: plan grilling, TDD, bug diagnosis, code review and architecture
GitHub toolkit for spec-driven development: the specify CLI adds agent commands and skills to a project, from principles to implementation
Reference MCP servers
Model Context Protocol servers
Official reference MCP servers: Filesystem, Fetch, Git, Memory, Sequential Thinking, Time and Everything