migrate-to-teamcity

Migrating CI/CD pipelines to TeamCity. Use when the user wants to migrate, convert, or switch to TeamCity from GitHub Actions (.github/workflows/) or Bamboo (bamboo-specs/*.yml), even if they only say "move our CI". Other CI systems (GitLab, Jenkins, CircleCI, Azure DevOps, Travis, Bitbucket) are not supported yet.

Quality

94%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

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.

A well-structured, highly actionable migration skill body: copy-paste commands, an explicit validation-gated workflow with a retry feedback loop, and clean one-level-deep reference files. The only minor weakness is conciseness, where a couple of dense flag lists and slight checklist/gotcha redundancy could be tightened.

Suggestions

Trim the private-repos gotcha by moving the full headless flag matrix ('--no-manifest --app-id ... --client-id ... --private-key-file ... --stdin' plus SSH-deploy-key variants) into references/gotchas.md, keeping only the primary `github-app` connection command inline.

Reduce redundancy between the Gotchas section and the Workflow checklist — the checklist already cross-references mappings.md and gotchas.md, so drop the restated gotcha prose (e.g. the 'type: script for ./gradlew' point) from the checklist and rely on the cross-reference.

Consider shortening the 'Reading the report' bullets by collapsing the exit-code and --json explanations into one line, since both are ancillary to the core migration flow.

Dimension	Reasoning	Score
Conciseness	Lean overall with no padding of concepts Claude already knows (no explainer of CI/CD or TeamCity), but a few sections could be trimmed — notably the private-repos gotcha inlines several alternative flag combinations ('--no-manifest --app-id ... --client-id ... --private-key-file ... --stdin') that read as over-specification, and the checklist restates some gotchas inline.	4 / 5
Actionability	Fully executable copy-paste-ready commands throughout — Quick Start gives runnable `teamcity` invocations, gotchas cite exact flags ('--branch refs/heads/master', '--vcs-root <id>'), and the checklist gives a concrete command per step covering the common migration cases.	5 / 5
Workflow Clarity	A clear sequenced checklist with an explicit validation checkpoint ('Validate: `teamcity pipeline validate <file>` -- only proceed when it passes') and a feedback loop for error recovery ('on failure read `teamcity run log <id> --failed --raw`, fix, `teamcity pipeline push`, re-run until green'), satisfying the validation requirement for batch/destructive migration work.	5 / 5
Progressive Disclosure	SKILL.md is a concise overview pointing to three real, one-level-deep reference files (references/mappings.md, references/schema.md, references/gotchas.md), all confirmed present and clearly signaled both inline ('See mappings') and in a dedicated References section, with bulk detail pushed to the references.	5 / 5
	Total	19 / 20 Passed

Description

95%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, third-person description that crisply states what the skill does and when to use it, with rich synonym and path-based trigger coverage and an explicit unsupported-systems boundary. The only soft spot is specificity, where the action verbs are somewhat redundant rather than enumerating distinct capabilities.

Dimension	Reasoning	Score
Specificity	Names the domain ('Migrating CI/CD pipelines to TeamCity') and several concrete actions ('migrate, convert, or switch') plus concrete source formats (GitHub Actions .github/workflows/, Bamboo bamboo-specs/*.yml), but the verbs are near-synonyms rather than a diverse set of distinct actions, leaving minor coverage gaps versus a comprehensive list.	4 / 5
Completeness	Explicitly answers both what ('Migrating CI/CD pipelines to TeamCity') and when ('Use when the user wants to migrate, convert, or switch to TeamCity from GitHub Actions ... or Bamboo ..., even if they only say "move our CI"') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Comprehensive natural-term coverage with synonyms ('migrate, convert, or switch'), the colloquial phrase 'move our CI' explicitly called out, and file extensions/paths (.github/workflows/, bamboo-specs/*.yml) that users would actually reference.	5 / 5
Distinctiveness Conflict Risk	Clear niche (migration to TeamCity from two named sources) with distinct triggers; explicitly enumerating unsupported systems (GitLab, Jenkins, CircleCI, Azure DevOps, Travis, Bitbucket) minimizes conflict risk with adjacent CI 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/migrate-to-teamcity/SKILL.md
Commit: de395a9

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