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.

2.57x

Quality

—

Does it follow best practices?

Impact

98%

2.57x

Average score across 2 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Quality

Content

100%

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

An efficient, highly actionable skill body: real commands, terse gotchas, sequenced workflows with a validation checkpoint, and clean one-level-deep references to verified bundle files. No verbosity or pedagogical padding.

Dimension	Reasoning	Score
Conciseness	The body is lean: terse Quick Start commands, a Gotchas bullet list, a compact command table, and one-line workflow summaries, with no padding explaining what TeamCity or CI/CD is — every token earns its place.	3 / 3
Actionability	It is dominated by concrete, copy-paste-ready commands with real flags (e.g. `teamcity run log <id> --failed --raw`, `echo $TOKEN \| connection create docker ...`), fully executable rather than abstract direction.	3 / 3
Workflow Clarity	Sequences are explicit (Investigate failure: `run list` → `run log` → `run tests`) with a clear validation checkpoint ("always `teamcity pipeline validate` first" before push) and a feedback loop for build chains (drill to deepest failed child via `run tree`).	3 / 3
Progressive Disclosure	SKILL.md is a tight overview that links one level deep to real, well-signaled references (commands.md, workflows.md, output.md), each verified present, with detailed material appropriately split out and easy to navigate.	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, third-person description that cleanly covers what the skill does and when to invoke it with natural trigger terms. No fluff, no over-claims, and a distinct TeamCity niche that avoids conflict with other skills.

Dimension	Reasoning	Score
Specificity	"drives the `teamcity` CLI for builds, logs, jobs, queues, agents, pools, projects, and pipelines" lists many concrete capability areas rather than vague language, matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	It explicitly answers both what ("drives the `teamcity` CLI for builds, logs, jobs...") and when ("Use when working with TeamCity CI/CD or when a user provides a TeamCity build URL"), the explicit-trigger anchor.	3 / 3
Trigger Term Quality	"TeamCity CI/CD", "TeamCity build URL", and the enumerated nouns (builds, logs, jobs, queues, agents, pools, projects, pipelines) are exactly the natural terms a user would say, giving strong trigger coverage.	3 / 3
Distinctiveness Conflict Risk	The TeamCity-specific niche and build-URL trigger make it clearly distinguishable and unlikely to fire for unrelated skills, matching the clear-niche anchor.	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/teamcity-cli
Commit: 42ce6a2

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.