Decides what kind of failure a red CI test is before anyone starts fixing it. Extracts seven failure signals from the runner output, stack trace, run history, and environment metadata, then walks an ordered first-match-wins rule set to exactly one verdict: flaky-known, environment-drift, defect, timeout, flaky-pre-incident, or flake-of-unknown-cause. Emits the verdict together with the alternatives that were rejected and the specific condition each one failed, so the triage decision is auditable rather than asserted. Use when a test has just gone red and the next action depends on whether the cause is a product defect, a non-deterministic test, or drifted infrastructure.
94%
Does it follow best practices?
Impact
99%
1.12xAverage score across 10 eval scenarios
Low
Low-risk findings worth noting
The canonical home for this skill is testland/ci-failure-triage
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.
The skill’s required runtime workflow ingests CI runner logs, stack traces, run history, and environment metadata from the job artifacts/outputs that can include arbitrary outsider-authored free text (e.g., failing test output and error messages) before selecting a verdict.
testland/qa
aa16752
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.