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.
92
91%
Does it follow best practices?
Impact
99%
1.59xAverage score across 3 eval scenarios
Low
Low-risk findings worth noting
The canonical home for this skill is teamcity-cli in JetBrains/teamcity-cli
W011: Third-party content exposure detected (indirect prompt injection risk).
What this means
The skill exposes the agent to untrusted, user-generated content from public third-party sources, creating a risk of indirect prompt injection. This includes browsing arbitrary URLs, reading social media posts or forum comments, and analyzing content from unknown websites.
Why it was flagged
The required workflow in `references/workflows.md` ingests outsider-authored free text at runtime by fetching and re-reading TeamCity build logs via `teamcity run log <run-id> --failed --raw` (and related failure outputs), where log contents can include arbitrary user-/commit-/issue-generated text.
- Repository
- JetBrains/MPS
- Commit
1f2bdbb
- Audited
- Security analysis
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.