Use Develocity Agent Skill
> 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`.
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/Kotlin/kotlinx-rpc --skill use-develocityThe instruction itself
7 sections, as written by the authorDevelocity 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.comis 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 scanskotlinx.rpc.develocity.skipGitTags=true-- stop adding git metadata
MCP Tools
Use develocity MCP to query and analyze build scans.
Other skills for the same job
different authors, same section of the catalogue
Integration with protocols.io API for managing scientific protocols. This skill should be used when working with protocols.io to search, create, update, or publish protocols; manage protocol steps and materials; handle discussions and comments; organize workspaces; upload and manage files; or integrate protocols.io functionality into workflows. Applicable for protocol discovery, collaborative protocol development, experiment tracking, lab protocol management, and scientific documentation.
Analyzes job descriptions and generates tailored resumes that highlight relevant experience, skills, and achievements to maximize interview chances
Generate Excalidraw diagrams from natural language descriptions. Use when asked to "create a diagram", "make a flowchart", "visualize a process", "draw a system architecture", "create a mind map", or "generate an Excalidraw file". Supports flowcharts, relationship diagrams, mind maps, and system architecture diagrams. Outputs .excalidraw JSON files that can be opened directly in Excalidraw.
Build and distribute Expo development clients locally or via TestFlight
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Data structure for annotated matrices in single-cell analysis. Use when working with .h5ad files or integrating with the scverse ecosystem. This is the data format skill—for analysis workflows use scanpy; for probabilistic models use scvi-tools; for population-scale queries use cellxgene-census.
Benchling R&D platform integration. Access registry (DNA, proteins), inventory, ELN entries, workflows via API, build Benchling Apps, query Data Warehouse, for lab data management automation.
Comprehensive molecular biology toolkit. Use for sequence manipulation, file parsing (FASTA/GenBank/PDB), phylogenetics, and programmatic NCBI/PubMed access (Bio.Entrez). Best for batch processing, custom bioinformatics pipelines, BLAST automation. For quick lookups use gget; for multi-service integration use bioservices.
How to use it
Take kotlin/use-develocity from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.