CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

1.59x
Quality

90%

Does it follow best practices?

Impact

99%

1.59x

Average score across 3 eval scenarios

SecuritybySnyk

—

The risk profile of this skill

SKILL.md
Quality
Evals
Security

Quality

Content

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

The body itself is near-ideal: lean, copy-paste-ready commands, terse gotchas, and well-sequenced workflows with validation and retry bounds. The single material defect is that all three referenced detail files are missing from the bundle, which breaks the progressive-disclosure structure in practice.

Suggestions

Ship the referenced bundle files — references/commands.md, references/workflows.md, and references/output.md are cited in the body but do not exist in the bundle; create them so the deferred detail (all commands and flags, full workflow guides, output formats) is actually reachable.

If the skill must remain a single file, inline the highest-value reference content (e.g., common flags for `run list`/`run log`/`run start`) and remove the dead links so navigation never dead-ends.

Add a fallback cue next to each reference, such as pointing to `teamcity <command> --help`, so the guidance degrades gracefully when a bundle file is unavailable.

DimensionReasoningScore

Conciseness

The ~50-line body is lean throughout — gotchas are single-line bullets ("Composite builds have empty logs — drill into child builds for the actual failure"), there is zero explanation of concepts Claude already knows, and every line is operational. Matches anchor 5: every token earns its place.

5 / 5

Actionability

Commands are copy-paste ready with real flags and sensible placeholders: `teamcity run log <id> --failed --raw`, `teamcity pipeline validate [file]`, `teamcity run list --status failure`. The Quick Workflows section covers the common cases (investigate failure, debug chain, fix, monitor, pipeline) end-to-end, matching anchor 5.

5 / 5

Workflow Clarity

Multi-step workflows are explicitly sequenced with validation checkpoints and a bounded feedback loop: "start → watch → fix if failed → push → watch new build → repeat (max 3 attempts)" and "always run `teamcity pipeline validate` first" because "`pipeline push` does not validate". Validation is present for the risky push operations, so no cap applies; this matches anchor 5.

5 / 5

Progressive Disclosure

The structure is exemplary — a concise overview with well-signaled, one-level-deep references ("[Command Reference](references/commands.md) — all commands and flags") — but the bundle contains no references/ directory: commands.md, workflows.md, and output.md do not exist, so all deferred content is unreachable. This exceeds anchor 4's "minor organization gaps" (every link is dead), landing at 3 even though the in-body signaling is stronger than that anchor's example.

3 / 5

Total

18

/

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 strong description: it names the tool, enumerates its functional areas, and gives two explicit, natural trigger conditions. The only room for improvement is verb-level action phrasing and a few more synonym triggers.

DimensionReasoningScore

Specificity

"Use `teamcity` CLI for builds, logs, jobs, queues, agents, and pipelines" names the concrete tool and six specific task areas. It fits anchor 4 (several specific actions, minor gaps) rather than 3, but stops short of 5 because the areas are noun domains rather than verb-level actions (e.g., "view failed builds", "download artifacts").

4 / 5

Completeness

Both halves are explicit: what — "Use `teamcity` CLI for builds, logs, jobs, queues, agents, and pipelines"; when — "Use when working with TeamCity CI/CD or when user provides a TeamCity build URL". This mirrors the anchor-5 exemplar (concrete capability list plus explicit trigger clauses), clearly above anchor 4 where the when-clause is less specific.

5 / 5

Trigger Term Quality

"TeamCity CI/CD" and "TeamCity build URL" are phrases users would naturally say, plus the area keywords (builds, logs, pipelines). A few natural variations like "build failure" or "CI server" are missing, matching anchor 4 rather than 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

"TeamCity CI/CD", "TeamCity build URL", and "teamcity CLI" pin the skill to a specific product with distinct triggers — minimal overlap risk with generic CI or other vendor-specific skills. Clearly the anchor-5 niche case.

5 / 5

Total

18

/

20

Passed

Validation

81%

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

CriteriaDescriptionResult

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

Reviewed

Table of Contents

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.