Teamcity CLI
JetBrains/MPS
A skill your agent uses when working with TeamCity CI/CD or when user provides a TeamCity build URL.
A skill your agent uses when working with TeamCity CI/CD or when user provides a TeamCity build URL.
Install Teamcity CLI
$ npx skills add JetBrains/skills --skill teamcity-cli -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install JetBrains/skills teamcity-cli --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/JetBrains/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/teamcity-cli .claude/skills/teamcity-cli && rm -rf skills-srcUse ~/.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/
Install the "teamcity-cli" agent skill from https://github.com/JetBrains/skills/tree/main/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 install https://github.com/JetBrains/skills/tree/main/teamcity-cliType 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.
$ npx skills add JetBrains/skills --skill teamcity-cli -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install JetBrains/skills teamcity-cli --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/JetBrains/skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/teamcity-cli .agents/skills/teamcity-cli && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "teamcity-cli" agent skill from https://github.com/JetBrains/skills/tree/main/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.
$ npx skills add JetBrains/skills --skill teamcity-cli -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install JetBrains/skills teamcity-cli --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/JetBrains/skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/teamcity-cli .cursor/skills/teamcity-cli && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "teamcity-cli" agent skill from https://github.com/JetBrains/skills/tree/main/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 https://github.com/JetBrains/skills.git --path 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.
$ npx skills add JetBrains/skills --skill teamcity-cli -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install JetBrains/skills teamcity-cli --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/JetBrains/skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/teamcity-cli .gemini/skills/teamcity-cli && rm -rf skills-srcUse ~/.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/
Install the "teamcity-cli" agent skill from https://github.com/JetBrains/skills/tree/main/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.
$ gh skill install JetBrains/skills teamcity-cliInstalls 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).
$ npx skills add JetBrains/skills --skill teamcity-cli -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/JetBrains/skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/teamcity-cli .github/skills/teamcity-cli && rm -rf skills-srcUse ~/.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/
Install the "teamcity-cli" agent skill from https://github.com/JetBrains/skills/tree/main/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.
$ npx skills add JetBrains/skills --skill teamcity-cli -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install JetBrains/skills teamcity-cli --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/JetBrains/skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/teamcity-cli .opencode/skills/teamcity-cli && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "teamcity-cli" agent skill from https://github.com/JetBrains/skills/tree/main/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
- 364
- Token cost
- ~740 tokens
- SKILL.md length
- 196 words
- Files
- 4 (incl. references)
- Skills in repo
- 77
- Repo updated
- First seen
- Licence
- None found
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 Quick Start, Core Commands, Quick Workflows and References
- Calls mvn
- User provides a TeamCity build URL
What it does
Teamcity CLI is an agent skill from JetBrains/skills, 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, and agents.
Its SKILL.md is about 740 tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `references/commands.md`, `references/output.md` and `references/workflows.md`).
It sits in DevOps & Cloud, covering CI/CD. It works with Kotlin. The repository describes itself as: Curated agent skills collection verified by JetBrains.
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 e0f258b. 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
Shell commands in SKILL.md call:
mvn
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 740 tokens when it runs, and up to ~7.9k if it reads all its reference files. Until then it costs about 39 tokens; SKILL.md has 196 words of instructions outside code blocks.
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
Without a licence we can't republish the file, so here is its outline and opening line. It has 196 words (~740 tokens).
“Do not guess flags or syntax. Use the Command Reference or teamcity --help. Fall back to teamcity api /app/rest/... when needed. Builds are runs (teamcity run), build configurations are jobs (teamcity job).”
- name
- teamcity-cli
- version
- 0.7.0
- author
- JetBrains
- metadata.short-description
- Operate TeamCity from the CLI
- metadata.source
- https://github.com/JetBrains/teamcity-cli/tree/main/skills/teamcity-cli
Files
SKILL.md and 3 other files (references) in teamcity-cli of JetBrains/skills.
- SKILL.md
- references/commands.md
- references/output.md
- references/workflows.md
Open the folder on GitHubat commit e0f258b
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Teamcity CLI this skillJetBrains/skills | 364 | — | ~740 | Automated safety check: Pass | None | |
| Teamcity CLIJetBrains/MPS | 1.7k | — | ~949 | Automated safety check: Pass | Apache-2.0 | |
| Gradle Build Performancercosteira79/android-skills | 151 | — | ~720 | Automated safety check: Pass | MIT | |
| Upgrade Notesgetknit/knit | 131 | — | ~1.2k | Automated safety check: Pass | GPL-3.0 | |
| Kt Search Releasejillesvangurp/kt-search | 155 | — | ~1.2k | Automated safety check: Pass | MIT | |
| Levyra CI WorkflowsLUC4N3X/Levyra-deepsound | 531 | — | ~2k | Automated safety check: Pass | GPL-3.0 |
Similar skills
- Official
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…
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.
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…
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…
Monitor CI
nrwl/nx
Monitor Nx Cloud CI pipeline and handle self-healing fixes. An agent skill from nrwl/nx.
More from JetBrains/skills
All 77 skills in this repo- Official
Playwright
JetBrains/skills
A skill your agent uses when the task requires automating a real browser from the terminal (navigation, form filling, snapshots, screenshots, data extraction, UI-flow debugging) via playwright-cli…
- Official
Skill Creator
JetBrains/skills
Guide for creating effective skills. An agent skill from JetBrains/skills.
- Official
Transcribe
JetBrains/skills
Transcribe audio files to text with optional diarization and known-speaker hints.
- Official
Imagegen
JetBrains/skills
A skill your agent uses when the user asks to generate or edit images via the OpenAI Image API (for example: generate image, edit/inpaint/mask, background removal or replacement, transparent…
- Official
Speech
JetBrains/skills
A skill your agent uses when the user asks for text-to-speech narration or voiceover, accessibility reads, audio prompts, or batch speech generation via the OpenAI Audio API; run the bundled CLI…
- Official
Screenshot
JetBrains/skills
A skill your agent uses when the user explicitly asks for a desktop or system screenshot (full screen, specific app or window, or a pixel region), or when tool-specific capture capabilities are…
Related
Works with
Categories
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/skills, 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/skills --skill teamcity-cli -a claude-code`. Or copy the skill folder (teamcity-cli in JetBrains/skills) 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/skills --skill teamcity-cli -a codex`. Or copy the skill folder (teamcity-cli in JetBrains/skills) 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/skills --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?
Going by SKILL.md and its folder, Teamcity CLI needs the command-line tools its instructions call (mvn).
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?
No licence was found for Teamcity CLI or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does Teamcity CLI use?
About 740 tokens (SKILL.md is roughly 3k 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 7.1k 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: Teamcity CLI (JetBrains/MPS, 1.7k stars), Gradle Build Performance (rcosteira79/android-skills, 151 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/skills, which has 364 GitHub stars. The repository holds 77 skills in this directory. The repository was last updated on June 29, 2026.
Source: JetBrains/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.