agentleFS
Sign inStart free
KotlinKotlin/kotlinx-rpc/.claude/skills/use-develocity/SKILL.md

use-develocity

Skill1.1k starsChanged 5 days agoApache-2.0View on GitHub

Query and analyze kotlinx-rpc build scans, test results, and failure patterns from the Develocity server (develocity.jetbrains.com) using MCP tools. Use this skill whenever the user wants to look at build scans, investigate CI failures across builds, check build cache hit rates, analyze flaky tests, find recurring failure patterns, or query build performance history. Also trigger when the user mentions "Develocity", "build scan", "GE", "develocity.jetbrains.com", "build cache stats", "flaky tests", "failure groups", or asks about build trends, test stability, or CI health. Trigger even if the user doesn't say "Develocity" explicitly -- if they want to look at historical build data, cross-build test analysis, or failure aggregation, this is the right skill. Do NOT use this skill for running local Gradle builds -- use `running_gradle_builds` or `running_gradle_tests` instead. Do NOT use this skill for TeamCity build triggering or queue management -- use `use-teamcity`.

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    All Develocity configuration lives in a single convention plugin: gradle-conventions-settings/develocity/ which exposes …

    line 33
  2. Very specific:

    Only CI builds push to the remote cache (isPush = isCIRun).

    line 51
  3. Distinctive:

    Use develocity MCP to query and analyze build scans.

    line 73

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

Develocity for kotlinx-rpc

Query build scans, test results, and failure patterns from the kotlinx-rpc Develocity instance via mcp__develocity__* MCP tools.

Project Setup

  • Server: https://develocity.jetbrains.com
  • Build scan URL pattern: https://develocity.jetbrains.com/s/<buildId>
  • Gradle project name: kotlinx-rpc
  • Build tool: gradle

How it's wired

All Develocity configuration lives in a single convention plugin: gradle-conventions-settings/develocity/ which exposes conventions-develocity as a settings plugin. Builds opt in by applying id("conventions-develocity") in their settings.gradle.kts.

BuildPublishes scans?
Root (:)Yes
compiler-plugin/Yes
dokka-plugin/Yes
gradle-plugin/No
protoc-gen/No
native-deps/shims/No (hard opt-out)
native-deps/grpc-c-prebuilt/No (hard opt-out)

Build cache

  • Remote cache at develocity.jetbrains.com is always readable.
  • Only CI builds push to the remote cache (isPush = isCIRun).
  • Local cache is disabled on CI.

Custom scan metadata

Scans include custom values and links that are useful for filtering:

ContextCustom valueCustom link
CI (TC)CI build idkotlinx.rpc TeamCity build (link)
LocalGit Commit IDGitHub Commit Link
LocalGit Branch NameGitHub Branch Link
LocalGit Status (dirty)--

Opt-out properties

Developers can add these to ~/.gradle/gradle.properties:

  • kotlinx.rpc.develocity.skipBuildScans=true -- stop publishing scans
  • kotlinx.rpc.develocity.skipGitTags=true -- stop adding git metadata

MCP Tools

Use develocity MCP to query and analyze build scans.

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.

Check your setup, free