pipelines-health-check
Check health of MSBuild CI pipelines, VS repo PR insertion statuses, and VMR codeflow PRs. Use when asked about pipeline health, build failures, infrastructure issues, CI status, insertion PR status, VMR codeflow status, or for periodic health monitoring.
72
88%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Low
Low-risk findings worth noting
Low
Low-risk findings.
1 low severity finding. Worth noting, but not necessarily harmful.
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
High likelihood: runtime calls to public/free-form outsider content via Azure DevOps timelines and GitHub PR metadata/comments (e.g., `check-vmr-codeflow.ps1` parses GitHub issue/PR comment bodies and PR titles, and `check-pipeline-health.ps1`/`check-vmr-codeflow.ps1` ingest task error messages), then these JSON fields are ultimately passed into the agent/subagent prompts as plain text (e.g., `{prTitle}`, `{checks.failedChecks[*].description}`, `{failedTasks...errors}`), enabling indirect prompt injection.
- Repository
- dotnet/msbuild
- Commit
c88db8e
- 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.