How do I install the Use Develocity skill?

Run npx skillmds@latest add kotlin/use-develocity in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Use Develocity safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Use Develocity?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Use Develocity free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Use Develocity?

Kotlin (@kotlin) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Use Develocity by kotlin — Agent Skill

Name: Use Develocity
Author: Kotlin

Use Develocity

Query and analyze kotlinx-rpc build scans, test results, and failure patterns from the Develocity server (ge.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", "ge.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`.

Kotlin f9dce8c 3.2 KB Updated Sep 17, 2026

File contents

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://ge.jetbrains.com
Build scan URL pattern: https://ge.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.

Build	Publishes 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 ge.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:

Context	Custom value	Custom link
CI (TC)	`CI build id`	`kotlinx.rpc TeamCity build` (link)
Local	`Git Commit ID`	`GitHub Commit Link`
Local	`Git Branch Name`	`GitHub Branch Link`
Local	`Git 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.

---name: use-develocitydescription: Query and analyze kotlinx-rpc build scans, test results, and failure patterns from the Develocity server (ge.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", "ge.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`.---# Develocity for kotlinx-rpcQuery build scans, test results, and failure patterns from the kotlinx-rpcDevelocity instance via `mcp__develocity__*` MCP tools.## Project Setup- **Server**: `https://ge.jetbrains.com`- **Build scan URL pattern**: `https://ge.jetbrains.com/s/<buildId>`- **Gradle project name**: `kotlinx-rpc`- **Build tool**: `gradle`### How it's wiredAll 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`.| Build | Publishes 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 `ge.jetbrains.com` is always **readable**.- Only CI builds **push** to the remote cache (`isPush = isCIRun`).- Local cache is disabled on CI.### Custom scan metadataScans include custom values and links that are useful for filtering:| Context | Custom value | Custom link ||-----------|-----------------------|---------------------------------------|| CI (TC) | `CI build id` | `kotlinx.rpc TeamCity build` (link) || Local | `Git Commit ID` | `GitHub Commit Link` || Local | `Git Branch Name` | `GitHub Branch Link` || Local | `Git Status` (dirty) | -- |### Opt-out propertiesDevelopers 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 ToolsUse develocity MCP to query and analyze build scans.

Frequently asked questions