YouTrack Issue Tracker

Manage YouTrack issues, projects, and workflows via CLI. Use when creating, updating, searching, or commenting on YouTrack issues, listing projects, checking issue states, or automating issue workflows.

Security Scan

The skill's documentation matches a YouTrack CLI, but it assumes a local 'ytctl' CLI and configuration files/env-vars that are not declared or provided — the pieces don't line up.

Purpose & Capability

The name/description and the SKILL.md commands are internally consistent for a YouTrack CLI helper. Requiring jq and curl is plausible for a shell-based wrapper. However the SKILL.md repeatedly calls a local CLI 'ytctl' (in 'scripts/') even though the package contains no code or install instructions — the skill as distributed cannot actually perform the described actions without external files.

Instruction Scope

Runtime instructions instruct the agent to run many ytctl commands and to read credentials from ~/.config/youtrack/config.json or environment variables (YOUTRACK_URL, YOUTRACK_TOKEN). The metadata declares no config paths or env vars. The instructions could cause the agent to read a user's home config file for credentials if present — that behavior is within the stated purpose but is not declared up-front and is ambiguous. The SKILL.md does not tell the agent how to obtain or install ytctl, nor does the registry include it.

Install Mechanism

There is no install spec and no code files (instruction-only). This is low risk from an installation viewpoint, but functionally problematic: the SKILL.md expects a 'ytctl' binary/script in 'scripts/' that is not included. That missing install step is a coherence issue (not a direct injection risk).

Credentials

The SKILL.md requires either a config file (~/.config/youtrack/config.json) or the env vars YOUTRACK_URL and YOUTRACK_TOKEN, which are proportionate to the claimed purpose. However the registry metadata lists no required env vars or config paths — this mismatch is suspicious and leaves unclear whether the skill will try to access local credential files unexpectedly.

Persistence & Privilege

The skill does not request persistent 'always' inclusion, does not request additional privileges, and does not attempt to modify other skills. No elevated persistence is requested.

What to consider before installing

This skill reads like documentation for a YouTrack CLI but does not include the ytctl script or an install step. Before installing or enabling it: confirm where 'ytctl' comes from (the package/source), verify the skill's origin, and only provide a YOUTRACK_TOKEN to trusted code. If you expect this skill to run autonomously, ensure it won't silently read ~/.config/youtrack/config.json unless you put only safe data there. If the registry metadata should declare YOUTRACK_URL/YOUTRACK_TOKEN or the config path, ask the publisher to fix the metadata or provide the CLI code; otherwise treat it as incomplete and avoid granting it access to your credentials.

YouTrack CLI

Use ytctl (in scripts/) for YouTrack issue tracking.

Setup

Credentials stored in ~/.config/youtrack/config.json:

{
  "url": "https://your-instance.youtrack.cloud",
  "token": "perm:xxx"
}

Or set env vars: YOUTRACK_URL, YOUTRACK_TOKEN

Generate token: YouTrack → Profile → Account Security → New Token

Commands

# List projects
ytctl projects

# List issues (with optional filters)
ytctl issues                           # all issues
ytctl issues SP                        # issues in project SP
ytctl issues SP --query "state: Open"  # filtered
ytctl issues --max 50                  # limit results

# Get issue details
ytctl issue SP-123

# Create issue
ytctl create SP "Bug: Login fails"
ytctl create SP "Feature request" "Detailed description here"

# Update issue
ytctl update SP-123 state "In Progress"
ytctl update SP-123 assignee john.doe
ytctl update SP-123 priority Critical

# Add comment
ytctl comment SP-123 "Investigating this now"

# Search with YouTrack query syntax
ytctl search "project: SP state: Open assignee: me"
ytctl search "created: today"
ytctl search "#unresolved sort by: priority"

# List workflow states for project
ytctl states SP

# List users
ytctl users
ytctl users --query "john"

Query Syntax

YouTrack query examples:

• state: Open — by state
• assignee: me — assigned to current user
• created: today — created today
• updated: {last week} — updated in last week
• #unresolved — all unresolved
• has: attachments — with attachments
• sort by: priority desc — sorted

Combine: project: SP state: Open assignee: me sort by: updated

Output

Default: table format. Add --json for raw JSON output:

ytctl issues SP --json
ytctl issue SP-123  # always JSON for single issue

Bulk Operations

# Update all matching issues (with dry-run preview)
ytctl bulk-update "project: SP state: Open" state "In Progress" --dry-run
ytctl bulk-update "project: SP state: Open" state "In Progress"

# Comment on all matching issues
ytctl bulk-comment "project: SP state: Open" "Batch update notice"

# Assign all matching issues
ytctl bulk-assign "project: SP #unresolved" john.doe --dry-run

Reports

# Project summary (default 7 days)
ytctl report SP
ytctl report SP --days 14

# User activity report
ytctl report-user zain
ytctl report-user zain --days 30

# State distribution with bar chart
ytctl report-states SP

Notes

• Project can be shortName (SP) or full name
• Fields: state, summary, description, assignee, priority
• Use ytctl states PROJECT to see valid state names
• Bulk operations support --dry-run to preview before executing