Builds a quarantine workflow for flaky tests - marks the test with the framework's skip/fixme/retry annotation, records the failure-rate observation and a bisect link in the annotation body, sets an auto-expiry date, and produces a CI report listing every quarantined test that has expired and needs re-evaluation. Use when a flaky test is blocking the trunk and must be removed from the gating path without losing track of it.
75
94%
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.
2 low severity findings. Worth noting, but not necessarily harmful.
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.
Step 4 in the CI workflow reads repository test source code annotations via a grep of `tests/` and then passes each matching “EXPIRED: $line” as free text into GitHub issue bodies (`gh issue create --body "$line"`), and those annotations are authored by outsiders whenever the repo/test content comes from non-user contributions (e.g., merged PRs from others).
The skill fetches instructions or code from an external URL at runtime, and the fetched content directly controls the agent’s prompts or executes code. This dynamic dependency allows the external source to modify the agent’s behavior without any changes to the skill itself.
The workflow in references/ci-quarantine-report.md includes the GitHub Action reference "actions/checkout@v5", which is fetched and executed at workflow runtime and therefore is a runtime external dependency that executes remote code.