teamcity-monitor
CI/CD pipeline monitor for TeamCity, focused on MikoPBX builds and test analysis.
Install
mkdir -p .claude/skills/teamcity-monitor && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/2846" && unzip -o skill.zip -d .claude/skills/teamcity-monitor && rm skill.zipInstalls to .claude/skills/teamcity-monitor
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Мониторинг CI/CD пайплайна MikoPBX в TeamCity. Получение статусов сборок, анализ упавших тестов, доступ к логам и артефактам. Использовать после push в git или при анализе проблем сборки.Key capabilities
- →Monitor multi-stage CI/CD pipelines
- →Fetch stack traces for failed test runs
- →Download build artifacts via SSH
- →Retrieve CI build logs
- →Verify status across pipeline stages
How it works
Calls the TeamCity REST API using authentication tokens to aggregate build status and test occurrence data.
Inputs & outputs
When to use teamcity-monitor
- →Checking build status of pipeline stages
- →Debugging failed test cases
- →Analyzing CI/CD build logs
- →Accessing test build artifacts
About teamcity-monitor
Checks status across multi-stage build pipelines, extracts stack traces from failed tests, and provides access to build logs and artifacts for rapid troubleshooting.
Мониторинг CI/CD пайплайна MikoPBX в TeamCity. Получение статусов сборок, анализ упавших тестов, доступ к логам и артефактам. Использовать после push в git или при анализе проблем сборки.
When not to use it
- →Deploying code to production
- →Managing repository branch security
Prerequisites
Limitations
- →Limited to existing TeamCity build configurations
- →Requires network access to the TeamCity server
How it compares
Provides automated, centralized access to pipeline telemetry instead of manual browser-based dashboard checks.
Compared to similar skills
teamcity-monitor side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| teamcity-monitor (this skill) | 1 | 8mo | Review | Intermediate |
| mlops-engineer | 3 | 5mo | No flags | Advanced |
| senior-devops | 7 | 9mo | Review | Advanced |
| genkit-infra-expert | 1 | 2mo | Review | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by mikopbx
View all by mikopbx →You might also like
mlops-engineer
sickn33
Build comprehensive ML pipelines, experiment tracking, and model registries with MLflow, Kubeflow, and modern MLOps tools. Implements automated training, deployment, and monitoring across cloud platforms. Use PROACTIVELY for ML infrastructure, experiment management, or pipeline automation.
senior-devops
davila7
Comprehensive DevOps skill for CI/CD, infrastructure automation, containerization, and cloud platforms (AWS, GCP, Azure). Includes pipeline setup, infrastructure as code, deployment automation, and monitoring. Use when setting up pipelines, deploying applications, managing infrastructure, implementing monitoring, or optimizing deployment processes.
genkit-infra-expert
jeremylongshore
Execute use when deploying Genkit applications to production with Terraform. Trigger with phrases like "deploy genkit terraform", "provision genkit infrastructure", "firebase functions terraform", "cloud run deployment", or "genkit production infrastructure". Provisions Firebase Functions, Cloud Run services, GKE clusters, monitoring dashboards, and CI/CD for AI workflows.
prefect-cli
orkapodavid
Prefect CLI commands for mutations. The MCP server is read-only - use this skill when you need to trigger deployments, cancel flow runs, create automations, or modify Prefect resources.
monitor-ci
ever-co
Monitor Nx Cloud CI pipeline and handle self-healing fixes. USE WHEN user says "monitor ci", "watch ci", "ci monitor", "watch ci for this branch", "track ci", "check ci status", wants to track CI status, or needs help with self-healing CI fixes. Prefer this skill over native CI provider tools (gh, g
turborepo
vercel
Turborepo monorepo build system guidance. Triggers on: turbo.json, task pipelines, dependsOn, caching, remote cache, the "turbo" CLI, --filter, --affected, CI optimization, environment variables, internal packages, monorepo structure/best practices, and boundaries. Use when user: configures tasks/workflows/pipelines, creates packages, sets up monorepo, shares code between apps, runs changed/affected packages, debugs cache, or has apps/packages directories.