teamcity-cli

Use when working with TeamCity CI/CD or when a user provides a TeamCity build URL — drives the `teamcity` CLI for builds, logs, jobs, queues, agents, pools, projects, and pipelines.

11.62x

Quality

93%

Does it follow best practices?

Impact

93%

11.62x

Average score across 1 eval scenario

Securityby

Low

Low-risk findings worth noting

Quality

Content

93%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.

A lean, highly actionable SKILL.md body that pairs executable commands with sharp gotchas and cleanly offloads detail to three real reference files. Its single soft spot is a few destructive operations in the command table that lack explicit validation/feedback steps.

Dimension	Reasoning	Score
Conciseness	The body is lean throughout—terse quick-start commands, compact gotchas, and a dense command table—with no padding or explanations of what TeamCity/CI-CD is, matching the every-token-earns-its-place anchor.	5 / 5
Actionability	Quick Start and Quick Workflows give copy-paste-ready commands with exact flags (e.g., "run log <id> --failed --raw", "--limit not --count") and cover common cases, matching the fully-executable anchor.	5 / 5
Workflow Clarity	Spelled-out workflows are clearly sequenced with key checkpoints ("pipeline validate" before "pipeline push", "--watch" when starting builds), but a few destructive commands in the table (cancel, restart) lack explicit verify/feedback steps, fitting the minor-validation-gaps anchor rather than the full-checkpoint anchor.	4 / 5
Progressive Disclosure	The body is a clear overview with three well-signaled one-level-deep references (commands.md, workflows.md, output.md) that all exist, and bulk content is appropriately split into those files, matching the clear-overview anchor.	5 / 5
	Total	19 / 20 Passed

Description

92%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 strong, well-structured description that explicitly states both capabilities and trigger conditions with concrete, natural terms. Its only weakness is slightly limited trigger synonyms, which keeps trigger term quality just below maximum.

Dimension	Reasoning	Score
Specificity	Names eight concrete capability areas ("builds, logs, jobs, queues, agents, pools, projects, and pipelines"), matching the comprehensive-coverage anchor rather than the 1-2-action or several-actions anchors.	5 / 5
Completeness	Explicitly answers what ("drives the teamcity CLI for builds, logs, jobs, queues, agents, pools, projects, and pipelines") and when ("Use when working with TeamCity CI/CD or when a user provides a TeamCity build URL"), matching the clear-both anchor.	5 / 5
Trigger Term Quality	Natural triggers like "TeamCity CI/CD" and "TeamCity build URL" give good keyword coverage, but it omits common synonyms such as "build log" or "build failure", so it stops short of the comprehensive-synonyms anchor.	4 / 5
Distinctiveness Conflict Risk	"TeamCity CI/CD" and "TeamCity build URL" carve a clear niche with distinct triggers and minimal overlap with other skills.	5 / 5
	Total	19 / 20 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/teamcity-cli
Path: skills/teamcity-cli/SKILL.md
Commit: d8eff98

Reviewed: 4 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.