Official agent skill

Teamcity CLI

A skill your agent uses when working with TeamCity CI/CD or when user provides a TeamCity build URL.

OfficialApache-2.0Auto-check passedDevOps & Cloud

Install Teamcity CLI

skills CLI

$ npx skills add JetBrains/MPS --skill teamcity-cli -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install JetBrains/MPS teamcity-cli --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/JetBrains/MPS.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/teamcity-cli .claude/skills/teamcity-cli && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "teamcity-cli" agent skill from https://github.com/JetBrains/MPS/tree/master/.agents/skills/teamcity-cli into .claude/skills/teamcity-cli/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "teamcity-cli", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/JetBrains/MPS/tree/master/.agents/skills/teamcity-cli

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add JetBrains/MPS --skill teamcity-cli -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install JetBrains/MPS teamcity-cli --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/JetBrains/MPS.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/teamcity-cli .agents/skills/teamcity-cli && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "teamcity-cli" agent skill from https://github.com/JetBrains/MPS/tree/master/.agents/skills/teamcity-cli into .agents/skills/teamcity-cli/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "teamcity-cli", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add JetBrains/MPS --skill teamcity-cli -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install JetBrains/MPS teamcity-cli --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/JetBrains/MPS.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/teamcity-cli .cursor/skills/teamcity-cli && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "teamcity-cli" agent skill from https://github.com/JetBrains/MPS/tree/master/.agents/skills/teamcity-cli into .cursor/skills/teamcity-cli/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "teamcity-cli", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/JetBrains/MPS.git --path .agents/skills/teamcity-cli

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add JetBrains/MPS --skill teamcity-cli -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install JetBrains/MPS teamcity-cli --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/JetBrains/MPS.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/teamcity-cli .gemini/skills/teamcity-cli && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "teamcity-cli" agent skill from https://github.com/JetBrains/MPS/tree/master/.agents/skills/teamcity-cli into .gemini/skills/teamcity-cli/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "teamcity-cli", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install JetBrains/MPS teamcity-cli

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add JetBrains/MPS --skill teamcity-cli -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/JetBrains/MPS.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/teamcity-cli .github/skills/teamcity-cli && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "teamcity-cli" agent skill from https://github.com/JetBrains/MPS/tree/master/.agents/skills/teamcity-cli into .github/skills/teamcity-cli/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "teamcity-cli", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add JetBrains/MPS --skill teamcity-cli -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install JetBrains/MPS teamcity-cli --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/JetBrains/MPS.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/teamcity-cli .opencode/skills/teamcity-cli && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "teamcity-cli" agent skill from https://github.com/JetBrains/MPS/tree/master/.agents/skills/teamcity-cli into .opencode/skills/teamcity-cli/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "teamcity-cli", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: teamcity-cli
GitHub stars: 1.7k
Token cost: ~949 tokens
SKILL.md length: 324 words
Files: 5 (incl. references)
Skills in repo: 40
Repo updated: Oct 7, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

A skill your agent uses when working with TeamCity CI/CD or when user provides a TeamCity build URL.

Working with TeamCity CI/CD
SKILL.md covers Gotchas, Core Commands, Quick Workflows and References
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
User provides a TeamCity build URL

What it does

Teamcity CLI is an agent skill from JetBrains/MPS, published by the product's own GitHub organization. Use when working with TeamCity CI/CD or when user provides a TeamCity build URL. Use teamcity CLI for builds, logs, jobs, queues, agents, and pipelines.

Its SKILL.md is about 950 tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `.instill.json`, `references/commands.md` and `references/output.md`).

It sits in DevOps & Cloud, covering CI/CD. It works with Kotlin. The repository describes itself as: JetBrains Meta programming System. The licence is Apache-2.0.

When your agent uses it

Working with TeamCity CI/CD
User provides a TeamCity build URL

Example prompts

“/teamcity-cli”

What it can do on your machine

Read from SKILL.md and the folder at commit a92f944. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Teamcity CLI loads about 949 tokens when it runs, and up to ~13k if it reads all its reference files. Until then it costs about 42 tokens; SKILL.md has 324 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~42
When it runs · the whole SKILL.md, loaded when a task matches: ~949
With references · SKILL.md plus every file in references/, read only if the agent opens them: ~13k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from JetBrains/MPS at commit a92f944, republished under its Apache-2.0 licence (© JetBrains). 324 words, ~949 tokens.

Download SKILL.mdSave it as .claude/skills/teamcity-cli/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.

name: teamcity-cli
description: Use when working with TeamCity CI/CD or when user provides a TeamCity build URL. Use `teamcity` CLI for builds, logs, jobs, queues, agents, and pipelines.
version: 0.9.0
author: JetBrains

TeamCity CLI (`teamcity`)

bash

teamcity auth status                    # Check authentication
teamcity run list --status failure      # Find failed builds
teamcity run log <id> --failed --raw    # Full failure diagnostics

Do not guess flags or syntax. Use the Command Reference or teamcity <command> --help. Builds are runs (teamcity run), build configurations are jobs (teamcity job). Never use --count — use --limit (or -n).

Gotchas

Composite builds have empty logs — drill into child builds for the actual failure.
Build chains fail bottom-up — the deepest failed dependency is the root cause, not the top-level build. Use teamcity run tree <id>.
--local-changes excludes Kotlin DSL — push .teamcity/ changes before running.
Always use --raw for logs and dump to a temp file. Always use --watch when starting builds.
VCS triggers aren't always configured — after pushing a fix, you may need to start builds manually.
pipeline push does not validate — always run teamcity pipeline validate first.

Core Commands

Area	Commands
Builds	`run list`, `view`, `start`, `watch`, `log`, `cancel`, `restart`, `tests`, `changes`, `tree`
Artifacts	`run artifacts`, `run download`
Metadata	`run pin/unpin`, `run tag/untag`, `run comment`
Jobs	`job list`, `view`, `tree`, `pause/resume`, `param list/get/set/delete`
Projects	`project list`, `view`, `tree`, `param`, `token put/get`, `settings export/status/validate`
Queue	`queue list`, `approve`, `remove`, `top`
Agents	`agent list`, `view`, `enable/disable`, `authorize/deauthorize`, `exec`, `term`, `reboot`, `move`
Pools	`pool list`, `view`, `link/unlink`
Pipelines	`pipeline list`, `view`, `create`, `validate`, `pull`, `push`, `delete`
API	`teamcity api <endpoint>` — raw REST API access

Quick Workflows

See Workflows for full details on each.

Investigate failure: teamcity run list --status failure → teamcity run log <id> --failed --raw → teamcity run tests <id> --failed Debug build chain: teamcity run tree <run-id> → find deepest failed child → investigate that build Fix build failure: diagnose → classify → fix (code: --local-changes, DSL: settings validate, pipeline: pipeline validate) → push Monitor until green: start → watch → fix if failed → push → watch new build → repeat (max 3 attempts) Pipeline: teamcity pipeline create <name> -p <project> / teamcity pipeline validate [file] / teamcity pipeline pull <pipeline-id> → edit → teamcity pipeline push <pipeline-id> [file]

References

Command Reference — all commands and flags
Workflows — failure investigation, build chains, fix workflows, monitoring, flaky tests, pipelines
Output Formats — JSON, plain text, scripting

Files

SKILL.md and 4 other files (references) in .agents/skills/teamcity-cli of JetBrains/MPS.

SKILL.md
.instill.json
references/commands.md
references/output.md
references/workflows.md

Open the folder on GitHubat commit a92f944

Compare with similar skills

Teamcity CLI next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Teamcity CLI compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Teamcity CLI this skillJetBrains/MPS	1.7k	—	~949	Automated safety check: Pass	Apache-2.0	today
Gradle Build Performancercosteira79/android-skills	151	—	~720	Automated safety check: Pass	MIT	19 days ago
Teamcity CLIJetBrains/skills	364	—	~740	Automated safety check: Pass	None	3 mo ago
Upgrade Notesgetknit/knit	131	—	~1.2k	Automated safety check: Pass	GPL-3.0	3 days ago
Kt Search Releasejillesvangurp/kt-search	155	—	~1.2k	Automated safety check: Pass	MIT	3 mo ago
Levyra CI WorkflowsLUC4N3X/Levyra-deepsound	531	—	~2k	Automated safety check: Pass	GPL-3.0	today

Similar skills

Gradle Build Performance
rcosteira79/android-skills
A skill your agent uses when Android/Gradle builds are slow — diagnosing bottlenecks with build scans, enabling configuration cache, migrating kapt to KSP, fixing cache misses, and optimizing CI/CD…
151 GitHub stars~720 tokensUpdated 19 days ago
DevOps & CloudAuto-check passed
Teamcity CLI
JetBrains/skills
Official
A skill your agent uses when working with TeamCity CI/CD or when user provides a TeamCity build URL.
364 GitHub stars~740 tokensUpdated 3 mo ago
DevOps & CloudAuto-check passed
Upgrade Notes
getknit/knit
Read the vendor's breaking changes, deprecations, migration notes and CVEs for every version between the one pinned now and the one being moved to, through the whatsnew MCP server's upgradenotes tool.
131 GitHub stars~1.2k tokensUpdated 3 days ago
SecurityAuto-check passed
Kt Search Release
jillesvangurp/kt-search
A skill your agent uses when the user wants to cut, publish, tag, or create a GitHub release for kt-search, especially when the task includes version bumping, validating that commits are pushed…
155 GitHub stars~1.2k tokensUpdated 3 mo ago
DevelopmentAuto-check passed
Levyra CI Workflows
LUC4N3X/Levyra-deepsound
Automatically use for Levyra GitHub Actions, CI, F-Droid, Gradle/AGP/Kotlin/KSP compatibility, build performance, configuration/build cache, artifacts, release automation, workflow security, or…
531 GitHub stars~2k tokensUpdated today
MobileAuto-check passed
Monitor CI
nrwl/nx
Monitor Nx Cloud CI pipeline and handle self-healing fixes. An agent skill from nrwl/nx.
29k GitHub starsUsed in 6 repos~4.7k tokens
DevOps & CloudAuto-check passed

More from JetBrains/MPS

All 40 skills in this repo

Mps Language Analysis
JetBrains/MPS
Official
Analyze an MPS language by name — discover concepts, properties, references, children, aspects (editor/constraints/behavior), and metadata.
1.7k GitHub stars~1.4k tokensUpdated today
Auto-check passed
Mps Node Editing
JetBrains/MPS
Official
Add, update, or delete MPS nodes using JSON blueprints — covers the unified blueprint format, staged construction for large subtrees, validation, and reference repair.
1.7k GitHub stars~4.7k tokensUpdated today
Auto-check passed
Mps Project Management
JetBrains/MPS
Official
Open an MPS project in a running or freshly started MPS instance when MCP tools fail because no project is open (welcome screen), close an open project with mpsmcpcloseproject, or create a new empty…
1.7k GitHub stars~2.2k tokensUpdated today
Auto-check passed
Mps MCP Workflow
JetBrains/MPS
Official
Complete JetBrains MPS workflow guide for DSL projects — models, languages, generators, node JSON blueprints, validation, MPS MCP tool usage, and the index of companion skills.
1.7k GitHub stars~5.8k tokensUpdated today
Auto-check passed
Bugfix Workflow
JetBrains/MPS
Official
Structured MPS bugfix workflow driven by a YouTrack issue ID — preflight tool checks, version/branch derivation, parallel-agent problem analysis, solution design, branch creation, implementation…
1.7k GitHub stars~4.4k tokensUpdated today
Auto-check passed
Mps Aspect Structure Concepts
JetBrains/MPS
Official
Define concepts, interface concepts, enumerations, and constrained data types in an MPS language's structure aspect.
1.7k GitHub stars~2.8k tokensUpdated today
Auto-check passed

Works with

Kotlin

Questions about Teamcity CLI

What does Teamcity CLI do?

A skill your agent uses when working with TeamCity CI/CD or when user provides a TeamCity build URL. Teamcity CLI is an agent skill from JetBrains/MPS, published by the product's own GitHub organization. Use when working with TeamCity CI/CD or when user provides a TeamCity build URL.

When should I use Teamcity CLI?

Teamcity CLI fits situations like: working with TeamCity CI/CD; user provides a TeamCity build URL.

How do I install Teamcity CLI in Claude Code?

Run `npx skills add JetBrains/MPS --skill teamcity-cli -a claude-code`. Or copy the skill folder (.agents/skills/teamcity-cli in JetBrains/MPS) into .claude/skills/teamcity-cli in your project. Claude Code loads it when a task matches its description.

How do I install Teamcity CLI in Codex?

Run `npx skills add JetBrains/MPS --skill teamcity-cli -a codex`. Or copy the skill folder (.agents/skills/teamcity-cli in JetBrains/MPS) into .agents/skills/teamcity-cli in your project. Codex loads it when a task matches its description.

Can I use Teamcity CLI in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add JetBrains/MPS --skill teamcity-cli -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/teamcity-cli, .gemini/skills/teamcity-cli, .github/skills/teamcity-cli and .opencode/skills/teamcity-cli in your project.

What does Teamcity CLI need to run?

SKILL.md names no scripts, command-line tools or credentials: Teamcity CLI is instructions for the agent only.

Does Teamcity CLI access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Teamcity CLI safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Teamcity CLI use?

Teamcity CLI is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Teamcity CLI use?

About 949 tokens (SKILL.md is roughly 3.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 12k tokens, read only when the agent opens those files.

What are the alternatives to Teamcity CLI?

Skills that share tags, products or a category with Teamcity CLI: Gradle Build Performance (rcosteira79/android-skills, 151 stars), Teamcity CLI (JetBrains/skills, 364 stars), Upgrade Notes (getknit/knit, 131 stars) and Kt Search Release (jillesvangurp/kt-search, 155 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Teamcity CLI?

JetBrains (a GitHub organization, an official publisher) maintains it in JetBrains/MPS, which has 1,660 GitHub stars. The repository holds 40 skills in this directory. The repository was last updated on October 7, 2026.

Source: JetBrains/MPS on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Teamcity CLI

Facts

At a glance

What it does

When your agent uses it

Example prompts

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

TeamCity CLI (teamcity)

Gotchas

Core Commands

Quick Workflows

References

Files

Compare with similar skills

Similar skills

More from JetBrains/MPS

Related

Questions about Teamcity CLI

TeamCity CLI (`teamcity`)