From managing-youtrack
Interact with YouTrack issue tracker via REST API. Create, read, update, and search issues and drafts; manage comments, tags, and issue links; log work items; inspect custom field schemas; list saved queries; look up users and groups. Use when the user asks about YouTrack issues, wants to file bugs, update tickets, add comments, manage tags or links, track time, or search for issues. Requires YOUTRACK_URL and YOUTRACK_TOKEN environment variables.
How this skill is triggered — by the user, by Claude, or both
Slash command
/managing-youtrack:managing-youtrackThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
- NEVER use pipes after curl commands to parse the output, do that in a separate tool call.
"${YOUTRACK_TOKEN}". Always include Accept: application/json; add Content-Type: application/json for write calls.curl -G --data-urlencode "query=..." instead of embedding the query string.fields parameter; default minimal issue fields: idReadable,summary.$type values → reference/fields.mdAfter create/update/delete, print a link to the affected item:
$YOUTRACK_URL/issue/<idReadable>$YOUTRACK_URL/issue/<idReadable>#focus=Comments-<COMMENT_ID>npx claudepluginhub forketyfork/agentic-skills --plugin managing-youtrackYouTrack issue tracker domain knowledge — data model, custom fields, query language, commands, linking, state machines, and tags. Invoke whenever task involves any interaction with YouTrack — creating issues, searching, updating fields, linking, querying, or understanding workflows.
Interacts with Jira issues via CLI scripts: search, create, update, transition, comment, log work, manage sprints/boards/attachments/links. Auto-triggers on Jira URLs and issue keys.
Core JIRA issue CRUD - create bugs/tasks/stories, get issue details, update fields, delete issues. TRIGGERS: 'show me [KEY]', 'get issue [KEY]', 'view issue', 'create a bug/task/story', 'update [KEY]', 'delete [KEY]', 'details of [KEY]', 'look up [KEY]', 'what's in [KEY]'. NOT FOR: epics (use jira-agile), transitions/status changes (use jira-lifecycle), comments/attachments (use jira-collaborate), time tracking (use jira-time), bulk operations on 10+ issues (use jira-bulk), dependencies/blockers (use jira-relationships), branch names/PR descriptions (use jira-dev).