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, and agents.
Install with Tessl CLI
npx tessl i github:JetBrains/teamcity-cli --skill teamcity-cli91
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillEvaluation — 97%
↑ 3.73xAgent success when using this skill
Validation for skill structure
Discovery
89%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 solid skill description with excellent trigger terms and completeness. The main weakness is that the capabilities are listed as general categories (builds, logs, jobs) rather than specific actions (trigger builds, download logs, cancel jobs). The description effectively distinguishes itself from other CI/CD tools.
Suggestions
Expand capability descriptions with specific actions: 'trigger builds, view logs, manage queues, monitor agents' instead of just listing nouns
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (TeamCity CI/CD) and lists general action areas (builds, logs, jobs, queues, agents), but doesn't describe concrete actions like 'trigger builds', 'view build logs', or 'manage agent pools'. | 2 / 3 |
Completeness | Explicitly answers both what (use teamcity CLI for builds, logs, jobs, queues, agents) and when (working with TeamCity CI/CD or when user provides a TeamCity build URL). Has clear 'Use when' clause. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'TeamCity', 'CI/CD', 'build URL', 'builds', 'logs', 'jobs', 'queues', 'agents'. Good coverage of terms a user working with TeamCity would naturally mention. | 3 / 3 |
Distinctiveness Conflict Risk | Very distinct niche - specifically targets TeamCity CI/CD platform with explicit tool name ('teamcity' CLI) and TeamCity-specific triggers like 'TeamCity build URL'. Unlikely to conflict with other CI/CD skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted skill that excels at conciseness and actionability, providing dense, executable guidance without unnecessary explanation. The progressive disclosure is excellent with clear navigation to detailed references. The main weakness is the workflow section, which presents command sequences without explicit validation or error recovery steps.
Suggestions
Add validation checkpoints to workflows, e.g., 'Verify build ID exists with `teamcity run view <id>` before running log commands'
Include brief error handling guidance for common failure scenarios (e.g., what to do if authentication fails or build ID not found)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. No unnecessary explanations of what TeamCity is or how CI/CD works. Every line provides actionable information, and the table format maximizes information density. | 3 / 3 |
Actionability | Provides concrete, copy-paste ready commands throughout. Quick Start shows exact syntax, workflows show command chains, and the table provides comprehensive command coverage. The note about not guessing flags and using --help is practical guidance. | 3 / 3 |
Workflow Clarity | Workflows are presented as command chains but lack explicit validation checkpoints. The 'Investigate failure' workflow shows a sequence but doesn't include verification steps or error handling guidance for when commands fail or return unexpected results. | 2 / 3 |
Progressive Disclosure | Excellent structure with a concise overview and clear one-level-deep references to detailed documentation. The three reference links are well-signaled with descriptive labels, and content is appropriately split between quick-start material and detailed references. | 3 / 3 |
Total | 11 / 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 | |
- 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.