Is flaky-ci-forensics-83f723 safe to install?

SaferSkills independently audited flaky-ci-forensics-83f723 (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.

CategoryWeightCategory scoreContribution

Securityprompt, exec, net, exfil, eval

35%

100

35.0 pts

Supply chainhash, typosquat, maintainer, lockfile

20%

100

20.0 pts

Maintenancestaleness, pinning, CI

15%

100

15.0 pts

TransparencySKILL.md, perms, README

15%

100

15.0 pts

Communityinstalls, verify, response

15%

100

15.0 pts

Findings & checks · 0 flagged

Securityscore 100 · 0 findings

✓—All security checks passedNo findings in this category for the latest scan.pass

Supply chainscore 100 · 0 findings

✓—All supply chain checks passedNo findings in this category for the latest scan.pass

Maintenancescore 100 · 0 findings

✓—All maintenance checks passedNo findings in this category for the latest scan.pass

Transparencyscore 100 · 0 findings

✓—All transparency checks passedNo findings in this category for the latest scan.pass

Communityscore 100 · 0 findings

✓—All community checks passedNo findings in this category for the latest scan.pass

The primary manifest — the file an agent reads to learn what this artifact does.

.claude/skills/flaky-ci-forensics/SKILL.md · 1 file

.claude/skills/flaky-ci-forensics/SKILL.md1.6 KB · Markdown

name: flaky-ci-forensics

description: Analyze flaky CI/test failures from JUnit XML, test history, and CI logs. Use when a team needs to distinguish true regressions from flakes, estimate rerun cost, choose quarantine versus fix-now actions, or produce a prioritized triage plan.

Flaky CI Forensics

This is a Claude Code install mirror for flaky-ci-forensics. Keep the canonical implementation in flaky-ci-forensics/.

Trigger

Use when the user provides CI logs, JUnit XML, test history, or asks whether failing tests are flaky, should be rerun, should be quarantined, or need a fix-now plan.

Workflow

Preserve the exact evidence: test names, failure messages, commit, retry count, runner metadata, and whether the same commit passed on retry.
If file artifacts exist, run the canonical analyzer from the repository root:

python3 flaky-ci-forensics/scripts/flaky_ci_forensics.py \
  --junit flaky-ci-forensics/scripts/fixtures/junit.xml \
  --log flaky-ci-forensics/scripts/fixtures/ci.log \
  --history flaky-ci-forensics/scripts/fixtures/history.csv

Classify failures into the canonical buckets from flaky-ci-forensics/references/flaky-test-rules.md.
Return the standard report: CI decision, failure cluster, cost and frequency, likely root cause, minimal fix plan, instrumentation, and guardrails.

Guardrails

Do not label deterministic assertion mismatches as flaky without retry-pass or environment evidence.
Do not quarantine auth, billing, payment, migration, security, deletion, or compliance coverage without explicit approval.
Quarantine recommendations need owner, expiry, and tracking issue.

flaky-ci-forensics-83f723— agent skill

Is flaky-ci-forensics-83f723 safe to install?

Flaky CI Forensics

Trigger

Workflow

Guardrails

Audit the pieces. Scan the whole. Decide.