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.
92
91%
Does it follow best practices?
Impact
99%
1.59xAverage score across 3 eval scenarios
Low
Low-risk findings worth noting
The canonical home for this skill is teamcity-cli in JetBrains/teamcity-cli
Pipeline create and YAML edit-publish automation
Validate before push
20%
100%
Create with --project
0%
100%
Create with --vcs-root
0%
100%
VCS pipeline: no pull/push
100%
100%
VCS pipeline: direct edit + git commit
100%
100%
List uses --limit not --count
40%
100%
TEAMCITY_URL exported
40%
100%
TEAMCITY_TOKEN exported
100%
100%
Scripting output flags
30%
100%
VCS root lookup command
80%
100%
Build chain failure investigation script
URL query param stripping
100%
100%
Correct run subcommand
75%
100%
run tree for chain inspection
0%
100%
Bottom-up deepest failure
83%
100%
Composite build handling
10%
80%
--raw flag on log fetch
100%
100%
Log redirect to temp file
100%
100%
--failed flag on log command
0%
100%
Failure classification in explanation
37%
100%
Bottom-up strategy in explanation
90%
100%
Kotlin DSL fix-and-validate workflow script
DSL validation command
53%
100%
No mvn compile for DSL
100%
100%
Git push before build trigger
100%
100%
No --local-changes for DSL fix
100%
100%
--watch on build start
30%
100%
Branch name verification
100%
100%
Log fetch uses --raw
30%
100%
Log dumped to temp file
100%
100%
Manual build start awareness
100%
100%
No test deletion guardrail
100%
100%
No force-push guardrail
100%
100%
1f2bdbb
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.