use-youtrack
Skill1.1k starsChanged 5 days agoApache-2.0View on GitHub
General-purpose YouTrack operations for the kotlinx-rpc project (KRPC). Use this skill whenever the user wants to search, read, update, comment on, link, tag, or otherwise interact with existing YouTrack issues — anything that isn't creating a brand new issue. Also use it when the user asks about issue status, sprint progress, who's working on what, backlog queries, or wants to browse/filter issues. Trigger this even if the user doesn't say "YouTrack" explicitly — if they mention a KRPC-### issue ID, ask about tickets, want to check on an issue, update a status, or log work, this is the right skill. Do NOT use this skill for creating new issues — use file-youtrack-issue instead.
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 2 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 23
When this skill is invoked from the fix-issue skill (autonomous issue-fixing workflow),
- Distinctive: line 24
all YouTrack operations must use the agent identity: instead of the user's:
- Very specific: line 33
Use mcp__youtrack__* MCP tools for standard operations.
- Very specific: line 47
Read references/query-syntax.md for the full query syntax reference and common search patterns (sprint work, backlog, recently closed, …
- Very specific: line 55
Use mcp__youtrack__get_issue with the issue ID (e.g., KRPC-531).
- Very specific: line 65
Read references/update-operations.md for the full reference on changing fields, assignees, tags, comments, links, and logging work.
- Distinctive: line 88
Wait for reply, Duplicate, Closed
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
YouTrack Operations for kotlinx-rpc (KRPC)
General-purpose skill for interacting with the KRPC YouTrack project.
Project key: KRPC | URL: https://youtrack.jetbrains.com/issue/KRPC-*
For creating new issues, use the file-youtrack-issue skill instead.
Agent workflow override
When this skill is invoked from the fix-issue skill (autonomous issue-fixing workflow),
all YouTrack operations must use the agent identity instead of the user's:
- MCP server:
youtrack-agent(notyoutrack) - REST API token:
$YOUTRACK_AGENT_TOKEN(not$YOUTRACK_TOKEN)
The fix-issue skill's Authentication section has full details. Outside of fix-issue,
the defaults below apply.
Tools Available
Use mcp__youtrack__* MCP tools for standard operations. When MCP tools lack a capability
(bulk updates, custom queries, attachment management, etc.), fall back to the YouTrack REST
API via YOUTRACK_TOKEN:
curl -s -H "Authorization: Bearer $YOUTRACK_TOKEN" \
"https://youtrack.jetbrains.com/api/<endpoint>?fields=<fields>"REST API base: https://youtrack.jetbrains.com/api
Docs: YouTrack REST API
Searching Issues
Read references/query-syntax.md for the full query syntax reference and common search
patterns (sprint work, backlog, recently closed, etc.).
Key point: YouTrack has no semantic search — always run multiple queries with different keywords to get good coverage.
Reading Issues
Use mcp__youtrack__get_issue with the issue ID (e.g., KRPC-531). This returns:
- Summary, description, reporter, timestamps
- Custom fields (Type, State, Priority, Scope, Assignee, Target Release, Planning Period)
- Recent comments (configurable count via
recentCommentsCount) - Tags, votes, linked issue counts, attachments
For full comment history, use mcp__youtrack__get_issue_comments.
Updating Issues
Read references/update-operations.md for the full reference on changing fields, assignees,
tags, comments, links, and logging work.
Key rules:
Scopemust be a JSON array, even for a single value- Multiline text fields need actual newlines, not literal
\nescape sequences - Always add the
Vibe-reporttag alongside any other tags the user requests
KRPC Project Reference
For full field definitions (scopes with determination logic, types, priorities, tags,
optional fields, team members), read
file-youtrack-issue/references/krpc-fields.md (relative to .claude/skills/).
Quick lists for common lookups:
Scopes
Compiler Plugin, kRPC, kRPC. Client, kRPC. Server, kRPC. Transport, gRPC, gRPC. Client, gRPC. Server, gRPC. Web, Core, Protoc Plugin, Gradle Plugin, Infra, Housekeeping, Documentation, Other
States
Submitted, Open, In progress, In design, Fixed in branch, Fixed, Wait for reply, Duplicate, Closed
Types
Bug, Feature, Task, Usability Problem, Performance Problem, Meta Issue, Security Problem
Knowledge Base Articles
YouTrack also hosts articles (wiki-like docs). Use:
mcp__youtrack__search_articles— find articles by keywordmcp__youtrack__get_article— read a specific articlemcp__youtrack__create_article/mcp__youtrack__update_article— manage articles
Important Terminology
kRPC and gRPC are protocols, not transports. This matters in issue descriptions, comments, and when choosing scopes. kRPC is the custom RPC protocol; gRPC is HTTP/2 + Protocol Buffers. Both support multiple serialization formats.
Trending
Quiet since September.about the whole repository
Who's talking about Kotlin/kotlinx-rpc
- bright-room/mindstock“fix(deps): update kotlinx.rpc to v0.10.4”GitHub · Sep 25, 2026
- bright-room/mindstock“fix(deps): update kotlinx.rpc to v0.10.3”GitHub · Jul 10, 2026
- modelix/modelix.editor“fix(deps): update kotlinx.rpc to v0.10.4”GitHub · Jul 6, 2026
- ktorio/ktor-plugin-registry“Bump the all-gradle group with 11 updates”GitHub · Jun 30, 2026
- DerTyp7214/synara-api“chore(deps): bump kotlinx-rpc from 0.10.2 to 0.10.3”GitHub · Jun 27, 2026
The biggest 5 of 16 mentions linking to the repository that our crawl found. Each line is their own headline.
See all 16
Talked about on GitHub (16 times).
On GitHub · 16
- Sep 25, 2026fix(deps): update kotlinx.rpc to v0.10.4 — bright-room/mindstock0 reactions · 1 comment
- Jul 10, 2026fix(deps): update kotlinx.rpc to v0.10.3 — bright-room/mindstock0 reactions
- Jul 6, 2026fix(deps): update kotlinx.rpc to v0.10.4 — modelix/modelix.editor0 reactions · 1 comment
- Jun 30, 2026Bump the all-gradle group with 11 updates — ktorio/ktor-plugin-registry0 reactions
- Jun 27, 2026chore(deps): bump kotlinx-rpc from 0.10.2 to 0.10.3 — DerTyp7214/synara-api0 reactions · 1 comment
11 more on GitHub
- May 3, 2026Add compiler plugin implementation and Kotlin External FIR Support — TBSten/cream0 reactions
- Mar 30, 2026build(deps): bump kotlinx-rpc from 0.10.1 to 0.10.2 — modelix/modelix.editor0 reactions · 5 comments
- Jan 17, 2026chore(deps): bump kotlinx-rpc from 0.10.1 to 0.10.2 — DerTyp7214/synara-api0 reactions · 2 comments
- Dec 20, 2025build(deps): bump org.jetbrains.kotlinx:kotlinx-rpc-krpc-ktor-client from 0.10.0 to 0.10.1 — DerTyp7214/synara-api0 reactions · 1 comment
- Dec 20, 2025build(deps): bump org.jetbrains.kotlinx:kotlinx-rpc-krpc-ktor-server from 0.10.0 to 0.10.1 — DerTyp7214/synara-api0 reactions · 1 comment
- Jul 3, 2025Update kxrpc tutorial to 0.8.0 — ktorio/ktor-documentation0 reactions · 2 comments
- Jul 3, 2025Update kxrpc to 0.8.0 — ktorio/ktor-plugin-registry0 reactions · 1 comment
- Apr 4, 2025Update kxrpc to 0.6.0 — ktorio/ktor-plugin-registry0 reactions · 1 comment
- Jan 28, 2025Update kxrpc to 0.5.0 — ktorio/ktor-plugin-registry0 reactions
- Jan 7, 2025Migrate cloud-run server to RPC ProtoBuf — ashdavies/playground.ashdavies.dev0 reactions
- May 26, 2024KotlinでRemote Procedure Calls (RPC) を簡単に行えるライブラリkotlinx.rpc — AndroidDagashi/AndroidDagashi0 reactions
In this repository19 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- commit-changesSkill
- file-youtrack-issueSkill
- fix-issueSkill
- gh-stackSkill
- gradle_expertSkill
- interacting_with_project_runtimeSkill
- introspecting_gradle_projectsSkill
- managing_gradle_dependenciesSkill
- researching_gradle_internalsSkill
- run-local-verificationsSkill
- running_gradle_buildsSkill
- running_gradle_testsSkill
- searching_dependency_sourcesSkill
- update-docSkill
- update-shimSkill
- use-develocitySkill
- use-teamcitySkill
- verify-compiler-plugin-compatibilitySkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

