agentleFS
KotlinKotlin/kotlinx-rpc/.claude/skills/use-youtrack/SKILL.md

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
  1. Very specific:

    When this skill is invoked from the fix-issue skill (autonomous issue-fixing workflow),

    line 23
  2. Distinctive:

    all YouTrack operations must use the agent identity: instead of the user's:

    line 24
  3. Very specific:

    Use mcp__youtrack__* MCP tools for standard operations.

    line 33
  4. Very specific:

    Read references/query-syntax.md for the full query syntax reference and common search patterns (sprint work, backlog, recently closed, …

    line 47
  5. Very specific:

    Use mcp__youtrack__get_issue with the issue ID (e.g., KRPC-531).

    line 55
  6. Very specific:

    Read references/update-operations.md for the full reference on changing fields, assignees, tags, comments, links, and logging work.

    line 65
  7. Distinctive:

    Wait for reply, Duplicate, Closed

    line 88

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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 (not youtrack)
  • 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:

  • Scope must be a JSON array, even for a single value
  • Multiline text fields need actual newlines, not literal \n escape sequences
  • Always add the Vibe-report tag 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 keyword
  • mcp__youtrack__get_article — read a specific article
  • mcp__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.

Download now (ZIP)

Trending

Quiet since September.about the whole repository

Dec 2025: 2 mentionsJan 2026: 1 mentionFeb 2026: 0 mentionsMar 2026: 1 mentionApr 2026: 0 mentionsMay 2026: 1 mentionJun 2026: 2 mentionsJul 2026: 2 mentionsAug 2026: 0 mentionsSep 2026: 1 mentionOct 2026: 0 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the Kotlin/kotlinx-rpc repository that our weekly crawl found. There is no adoption data for this file yet.

Who's talking about Kotlin/kotlinx-rpc

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

11 more on GitHub

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.