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.
99
100%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
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.
This is a strong skill description that clearly identifies the tool (TeamCity CLI), lists specific capabilities (builds, logs, jobs, queues, agents, pools, projects, pipelines), and provides explicit trigger conditions (working with TeamCity CI/CD or receiving a TeamCity build URL). It is concise, uses third-person voice, and is highly distinguishable from other CI/CD-related skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'builds, logs, jobs, queues, agents, pools, projects, and pipelines' and specifies it 'drives the `teamcity` CLI', which is a concrete mechanism. | 3 / 3 |
Completeness | Clearly answers both 'what' (drives the teamcity CLI for builds, logs, jobs, queues, agents, pools, projects, and pipelines) and 'when' (when working with TeamCity CI/CD or when a user provides a TeamCity build URL) with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms: 'TeamCity', 'CI/CD', 'TeamCity build URL', 'builds', 'logs', 'jobs', 'queues', 'agents', 'pools', 'projects', 'pipelines' — these are terms users would naturally use when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — 'TeamCity' is a specific CI/CD platform, the `teamcity` CLI is named explicitly, and the mention of 'TeamCity build URL' creates a very clear niche that is unlikely to conflict with other CI/CD skills (e.g., Jenkins, GitHub Actions). | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent skill file that is lean, actionable, and well-structured. It assumes Claude's competence, provides concrete commands and flags, highlights non-obvious gotchas, and uses progressive disclosure effectively with clear references to detailed documentation. The command table provides comprehensive coverage in a scannable format.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every line earns its place. No explanations of what TeamCity is or how CI/CD works. The gotchas are terse, specific, and non-obvious. The command table is dense and scannable. | 3 / 3 |
Actionability | Provides concrete, copy-paste-ready commands throughout (quick start, workflows, gotchas). Specific flags are called out (--raw, --watch, --failed, --limit vs --count), and anti-patterns are explicitly named. | 3 / 3 |
Workflow Clarity | Multi-step workflows are clearly sequenced with arrows showing progression. The pipeline lifecycle includes an explicit validation step before push. The failure investigation workflow has a clear drill-down sequence. The gotcha about 'pipeline push does not validate' reinforces the validation checkpoint. | 3 / 3 |
Progressive Disclosure | Clean overview with well-signaled one-level-deep references to commands.md, workflows.md, and output.md. The SKILL.md stays concise while pointing to detailed materials for each area. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- JetBrains/teamcity-cli
- Commit
ae2d089
- 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.