Name: teamcity-cli
Rating: 72.8 (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

91%

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

96%Weight 40%Scale 1-5

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

An exceptionally lean, actionable body with clear workflow sequences and validation checkpoints. The only weakness is progressive disclosure: the body references three reference files that are not present in the bundle.

Suggestions

Add the referenced files (references/commands.md, references/workflows.md, references/output.md) to the bundle so the signaled navigation resolves.

If the references are intentionally omitted, remove or inline the link text so the skill is not pointing at missing files.

Dimension	Reasoning	Score
Conciseness	Lean and efficient with no padding or explanations of concepts Claude already knows; every section (commands, gotchas, table, workflows) earns its place.	5 / 5
Actionability	Fully executable commands with specific flags (e.g. `teamcity run log <id> --failed --raw`), a comprehensive command table, and copy-paste-ready workflow sequences covering common cases.	5 / 5
Workflow Clarity	Multi-step workflows are clearly sequenced with explicit validation checkpoints (validate pipelines before push, monitor-until-green with a 3-attempt cap, drill into child builds for chains).	5 / 5
Progressive Disclosure	Well-structured overview with clearly signaled one-level-deep references, but the referenced files (references/commands.md, workflows.md, output.md) do not exist in the bundle, so the navigation is broken.	4 / 5
	Total	19 / 20 Passed

Description

87%Weight 40%Scale 1-5

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-targeted description that clearly answers both what the skill does and when to invoke it. Trigger terms are natural and the niche is distinctive, with only minor gaps in action specificity and synonym coverage.

Dimension	Reasoning	Score
Specificity	Names the teamcity CLI and enumerates several concrete capability domains (builds, logs, jobs, queues, agents, pipelines), though it lists domains rather than multiple distinct actions per item.	4 / 5
Completeness	Explicitly states both what (use the teamcity CLI for builds, logs, jobs, queues, agents, pipelines) and when ("Use when working with TeamCity CI/CD or when user provides a TeamCity build URL") with concrete triggers.	5 / 5
Trigger Term Quality	Includes natural phrases users would say ("TeamCity CI/CD", "TeamCity build URL") with good coverage, though a few common synonyms are missing.	4 / 5
Distinctiveness Conflict Risk	Targets a clear niche (TeamCity CI/CD) with distinct, product-specific triggers and minimal overlap risk with other skills.	5 / 5
	Total	18 / 20 Passed

Validation

81%

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 — 13 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 5 missing	Warning
referenced_paths_exist	Referenced path issues: 5 missing	Warning

	Total	13 / 16 Passed

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

Reviewed: 3 days 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.