youtrack
Manage IdeaVim YouTrack Issues
Teams working on IdeaVim need consistent YouTrack workflows instead of GitHub Issues. This skill gives agents the ticket conventions, commands, tags, and release steps for VIM issues.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "youtrack" from https://skillstore.io/skills/jetbrains-youtrack.md and its manifest at https://skillstore.io/api/skills/jetbrains-youtrack/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "youtrack". Summarize VIM-1234 and recommend the next action.
Expected outcome:
- Ticket details requested from YouTrack.
- Status, tags, and recent discussion reviewed.
- Recommended next action: ask the maintainer for missing reproduction details.
Using "youtrack". Prepare a private clarification request for VIM-1234.
Expected outcome:
A private comment draft asks for the missing details. The pending clarification tag is recommended for approval before changes are made.
Using "youtrack". Plan release updates for VIM tickets in version 2.29.0.
Expected outcome:
Ready tickets are grouped for fix-version updates. Risky status or version changes are listed for human approval first.
Security Audit
Medium RiskMost static findings are Markdown backtick and code-fence false positives, not executable Ruby or hidden shell substitution. The skill still documents YouTrack state-changing workflows, including release version deletion, without explicit approval guardrails. No prompt injection or credential exfiltration intent was found.
Confirmed security concerns (1)
Risk Factors
⚙️ External commands (49)
🌐 Network access (1)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/jetbrains-youtrack/audits/7?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/jetbrains-youtrack?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/jetbrains-youtrack?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/jetbrains-youtrack/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/jetbrains-youtrack.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
JetBrains. (2026). youtrack security audit report (audit version 7) [Author version unspecified]. Skillstore. https://skillstore.io/skills/jetbrains-youtrack/audits/7BibTeX citation
@techreport{jetbrains-jetbrains-youtrack-2026,
author = {JetBrains},
title = {youtrack security audit report (audit version 7)},
institution = {Skillstore},
year = {2026},
number = {7},
url = {https://skillstore.io/skills/jetbrains-youtrack/audits/7},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "youtrack security audit report (audit version 7)"
version: "unspecified"
type: report
authors:
- name: "JetBrains"
date-released: "2026-07-05"
url: "https://skillstore.io/skills/jetbrains-youtrack/audits/7"
identifiers:
- type: other
value: "skillstore:jetbrains-youtrack:audit:7"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Triage IdeaVim Tickets
Review VIM tickets, check details, and decide whether tags or comments are needed.
Coordinate Release Updates
Set fix versions, mark tickets ready to release, and manage release version records.
Request Clarification Privately
Add a pending clarification tag and prepare a private comment for the JetBrains team.
Try These Prompts
Use the YouTrack skill to fetch details for VIM-1234 and summarize status, assignee, tags, and open questions.
For VIM-1234, draft a concise public comment based on this analysis. Ask before posting it to YouTrack.
For VIM-1234, identify missing information, propose a private clarification comment, and recommend the pending clarification tag.
Review the linked VIM tickets for release 2.29.0, identify ready items, and propose status, tag, and fix-version changes for approval.
Best Practices
- Confirm the ticket ID and project before changing YouTrack records.
- Use private comments only when the content is intended for the JetBrains team.
- Request approval before mutating tags, status, comments, or release versions.
Avoid
- Do not use GitHub Issues for IdeaVim tickets when this workflow applies.
- Do not expose YOUTRACK_TOKEN values in prompts, logs, comments, or output.
- Do not delete release versions without explicit confirmation and version verification.