Name: teamcity-cli
Rating: 79.2 (1 reviews)
Author: JetBrains

teamcity-cli

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.

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

The canonical home for this skill is teamcity-cli in JetBrains/teamcity-cli

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a tight, actionable overview that delegates detail to three clearly-labeled reference files, with executable commands, explicit gotchas, and sequenced workflows that include validation and retry bounds.

Dimension	Reasoning	Score
Conciseness	Lean and efficient — quick command examples, a gotchas list, a compact command table, and workflows, with no explanation of what TeamCity or CI/CD is. Every section earns its tokens.	3 / 3
Actionability	Concrete executable commands throughout (e.g. `teamcity run log <id> --failed --raw`, `teamcity run tree <run-id>`) that are copy-paste ready, plus explicit flag guidance (--limit vs --count).	3 / 3
Workflow Clarity	Sequences are explicit with arrows (investigate → log → tests), validation checkpoints are present ("always run `teamcity pipeline validate` first"), and the monitor workflow has a bounded retry loop (max 3 attempts).	3 / 3
Progressive Disclosure	Clear overview in SKILL.md with one-level-deep, well-signaled references (commands.md, workflows.md, output.md) — all verified to exist — each annotated with what it contains.	3 / 3
	Total	12 / 12 Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A concise, well-structured description that clearly states what the skill does and when to invoke it, with natural trigger terms and a distinct TeamCity-specific niche. No fluff or over-claims.

Dimension	Reasoning	Score
Specificity	Names concrete capability areas the CLI covers — "builds, logs, jobs, queues, agents, and pipelines" — listing multiple specific actions rather than vague abstractions.	3 / 3
Completeness	Explicitly answers both: what to do ("Use `teamcity` CLI for builds, logs, jobs...") and when to use it ("Use when working with TeamCity CI/CD or when user provides a TeamCity build URL").	3 / 3
Trigger Term Quality	Includes natural terms a user would say ("TeamCity CI/CD", "TeamCity build URL") plus the tool name, giving good coverage of how the need arises in practice.	3 / 3
Distinctiveness Conflict Risk	The TeamCity-specific trigger (TeamCity CI/CD, TeamCity build URL) carves a clear niche unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: JetBrains/MPS
Path: .agents/skills/teamcity-cli/SKILL.md
Commit: 52c9d63

Reviewed: about 5 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

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.