Skip to content
TrustedSkillsbeta
Back to all skills

Triage Ci Flake

Checked
payloadcms·vlatest·productivity·MIT

Automatically identifies and prioritizes CI build flakes for faster debugging and resolution, boosting development efficiency.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add payloadcms/payload --skill triage-ci-flake -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

payloadcms

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned payloadcms/payload at 01f44da065.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
01f44da065
Manifest
.agents/skills/triage-ci-flake/SKILL.md
Scanned
1 file, 466 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

The triage-ci-flake skill enables AI agents to automatically detect and analyze flaky tests within Continuous Integration pipelines. It helps maintain code quality by identifying unstable test cases that cause false failures, allowing teams to focus on genuine bugs rather than noise.

When to use it

  • Automate Test Stability: Run during nightly builds to catch intermittent failures before they accumulate in the main branch.
  • Reduce Noise: Filter out non-critical CI alerts so engineers can prioritize actual production issues.
  • Improve Pipeline Reliability: Identify flaky tests that block deployments or waste developer time on false positives.
  • Maintain Historical Data: Track patterns of flakiness over time to improve test suite robustness.

Key capabilities

  • Detects flaky tests in CI environments
  • Analyzes test execution logs for instability patterns
  • Provides actionable insights to fix or quarantine unstable tests

Example prompts

  • "Analyze the last 50 CI runs and identify any tests that failed intermittently."
  • "List all flaky tests detected in the current build pipeline along with their failure frequency."
  • "Generate a report of unstable test cases that need immediate attention or quarantine."

Tips & gotchas

Ensure your CI logs are accessible and contain sufficient detail for the agent to distinguish between random failures and actual bugs. This skill works best when integrated early in the development cycle to prevent flakiness from becoming systemic.