Skip to content
TrustedSkillsbeta
Back to all skills

Fix Flaky Tests

Checked
tuist·vlatest·testing

Automatically identifies and resolves flaky test failures, boosting confidence in your test suite's stability and reliability.

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 tuist/agent-skills --skill fix-flaky-tests -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

tuist

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 tuist/agent-skills at 9a6ec783fe.

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

Commit
9a6ec783fe
Manifest
skills/fix-flaky-tests/SKILL.md
Scanned
1 file, 157 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

What it does

This skill helps AI agents identify and resolve flaky tests within a Tuist-managed project. It leverages the Tuist CLI to retrieve reliability metrics, analyze run histories, and pinpoint failure details for individual test cases. The agent can then use this information to understand the root cause of flakiness and ultimately fix the underlying issues, improving overall test suite stability.

When to use it

  • When a specific flaky test case is identified and needs investigation.
  • To proactively discover and address all flaky tests within a project.
  • When troubleshooting intermittent failures that may be caused by flaky tests.
  • To analyze patterns in flaky test runs (e.g., branch-specific failures, CI vs. local discrepancies).
  • To understand the context of failing tests, including failure messages and file paths.

Key capabilities

  • Retrieves reliability metrics for individual test cases (tuist test case show).
  • Lists flaky test run patterns (tuist test case run list --flaky).
  • Displays detailed information about specific flaky runs (tuist test case run show).
  • Identifies all currently flagged flaky tests in a project (tuist test case list --flaky).
  • Provides key fields for triage, including avg_duration, is_quarantined, and failure message categorization.

Example prompts

  • "Find me the reliability metrics for the test case Module/Suite/TestCase."
  • "List all flaky tests in the project with a page size of 50."
  • "Show me the details of this specific flaky test run: <test-case-run-id>."

Tips & gotchas

  • Requires access to and familiarity with the Tuist CLI.
  • The skill relies on tests being properly integrated into a Tuist project for accurate identification and reporting.
  • Understanding failure messages is crucial for identifying the root cause of flakiness, which may involve test logic bugs or infrastructure issues.