New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Official agent skill

Flaky Test Investigator

by elastic in elastic/kibana

Investigate Scout and FTR flaky test failures in Kibana. An agent skill from elastic/kibana.

OfficialCustom licenceAuto-check passedTesting & QA

Install Flaky Test Investigator

skills CLI
$ npx skills add elastic/kibana --skill flaky-test-investigator -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install elastic/kibana flaky-test-investigator --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/elastic/kibana.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/flaky-test-investigator .claude/skills/flaky-test-investigator && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
flaky-test-investigator
GitHub stars
21k
Token cost
~4.4k tokens
SKILL.md length
2,542 words
Files
3 (incl. references)
Skills in repo
40
Repo updated
First seen
Licence
Custom licence

At a glance

Investigate Scout and FTR flaky test failures in Kibana. An agent skill from elastic/kibana.

  • Works in 8 steps: What the test does (one paragraph) → What failed and when (most recent… → Where it ran (Cloud or local pipelines,… → …
  • Triaging a failed-test issue
  • SKILL.md covers Required input, Investigation and Reporting
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Flaky Test Investigator is an agent skill from elastic/kibana, published by the product's own GitHub organization. Investigate Scout and FTR flaky test failures in Kibana. Use when triaging a failed-test issue, a Buildkite-reported failure, a test path that has been failing intermittently, or any time the user asks to look at a flaky test, deflake a test, or stabilize a test.

Its SKILL.md is about 4.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `agents/openai.yaml` and `references/pipelines.md`).

It sits in Testing & QA, covering Failing and flaky tests. It works with Elasticsearch. The repository describes itself as: Your window into all of your data.

When your agent uses it

  • Triaging a failed-test issue
  • A Buildkite-reported failure
  • A test path that has been failing intermittently
  • Any time the user asks to look at a flaky test

Example prompts

  • “/flaky-test-investigator”

Requirements

  • Docker

Workflow steps

8 steps, taken from the first numbered list in SKILL.md.

  1. What the test does (one paragraph)
  2. What failed and when (most recent failure + count of failures over time)
  3. Where it ran (Cloud or local pipelines, or both)
  4. Root cause hypothesis (a few sentences describing the outcome of the investigation)
  5. Evidence supporting that hypothesis, and evidence against it (if you considered alternative hypotheses, include them alongside their…
  6. Failure screenshot description: what did you observe in the failure screenshot?
  7. Recommended next step (this won't always be a code change). If you are recommending a code fix, give an honest note on expected durability
  8. Open questions the investigation could not resolve

What it can do on your machine

Read from SKILL.md and the folder at commit 30ea56f. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Flaky Test Investigator loads about 4.4k tokens when it runs, and up to ~5.6k if it reads all its reference files. Until then it costs about 72 tokens; SKILL.md has 2,542 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~72
When it runs · the whole SKILL.md, loaded when a task matches
~4.4k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~5.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 2,542 words (~4,351 tokens).

“Investigate a flaky Scout or FTR test failure and determine what should be done about it.”

— opening of SKILL.md by elastic, Custom licence
name
flaky-test-investigator
disable-model-invocation
true

Read the full SKILL.md on GitHub

Files

SKILL.md and 2 other files (references) in .agents/skills/flaky-test-investigator of elastic/kibana.

  • SKILL.md
  • agents/openai.yaml
  • references/pipelines.md

Open the folder on GitHubat commit 30ea56f

Compare with similar skills

Flaky Test Investigator next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Flaky Test Investigator compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Flaky Test Investigator this skillelastic/kibana21k—~4.4kAutomated safety check: PassCustom licence
Pester Failure AnalysisPowerShell/PowerShell56k—~5.1kAutomated safety check: PassMIT
Cucumber and Playwright E2E Testslanggenius/dify158k—~682Automated safety check: PassCustom licence
Diagnose Playwright Failure as Product Bugappsmithorg/appsmith41k—~1.5kAutomated safety check: PassApache-2.0
Apple Container Test RunnerRustPython/RustPython22k—~467Automated safety check: PassMIT
Fix Failing Playwright Specappsmithorg/appsmith41k—~1.3kAutomated safety check: PassApache-2.0

Similar skills

  • Pester Failure Analysis

    PowerShell/PowerShell

    Investigates failing Pester tests in PowerShell CI jobs by following a six-step workflow from pull request status to documented fix recommendations.

    56k GitHub stars~5.1k tokensUpdated yesterday
    Testing & QAAuto-check passed

  • Cucumber and Playwright E2E Tests

    langgenius/dify

    Guides changes and reviews of the Cucumber and Playwright end-to-end suite under `e2e/`: feature files, step definitions, support code, tags, locators and assertions.

    158k GitHub stars~682 tokensUpdated today
    Testing & QAAuto-check passed

  • Diagnose Playwright Failure as Product Bug

    appsmithorg/appsmith

    Investigates a stubbornly failing Playwright test as a possible product bug, using error output, screenshots, traces and server code, and writes a structured bug report.

    41k GitHub stars~1.5k tokensUpdated yesterday
    Testing & QAAuto-check passed

  • Apple Container Test Runner

    RustPython/RustPython

    Runs RustPython tests inside a Linux container built with Apple's container CLI, so macOS users can compare Linux results with their local ones.

    22k GitHub stars~467 tokensUpdated today
    Testing & QAAuto-check passed

  • Fix Failing Playwright Spec

    appsmithorg/appsmith

    Fixes failing Playwright specs by reading the error, classifying the cause in the test code and applying corrections that follow project conventions.

    41k GitHub stars~1.3k tokensUpdated yesterday
    Testing & QAAuto-check passed

  • Perf Regression Triage

    mozilla-firefox/firefox

    Handle a Perfherder performance regression bug end to end: read the alert bug, confirm whether the regression is real, find the cause, and iterate to a fix.

    13k GitHub stars~1.7k tokensUpdated today
    Testing & QAAuto-check passed

More from elastic/kibana

All 40 skills in this repo

  • Cypress To Scout Migration

    elastic/kibana

    Official

    Migrate Kibana Cypress E2E tests (.cy.ts) to Scout (Playwright).

    21k GitHub stars~3.8k tokensUpdated today
    Auto-check passed

  • Activate Connector

    elastic/kibana

    Official

    Creates a connector instance in a running Kibana. An agent skill from elastic/kibana.

    21k GitHub stars~1.9k tokensUpdated today
    Auto-check: notes

  • Codeql

    elastic/kibana

    Official

    Work with CodeQL in Kibana — write, test, and debug custom queries locally, fetch scan results from GitHub, and validate inline suppression comments.

    21k GitHub stars~1.7k tokensUpdated today
    Auto-check passed

  • Debug Oas

    elastic/kibana

    Official

    A skill your agent uses when debugging OpenAPI (OAS) issues for a specific API area in Kibana by scoping validation output with one or more --path filters, then separating structural invalid-OAS…

    21k GitHub stars~1.4k tokensUpdated today
    Auto-check passed

  • Evals Write Spec

    elastic/kibana

    Official

    Write LLM evaluation spec files with datasets, tasks, and evaluators using the @kbn/evals Playwright fixture.

    21k GitHub stars~2.3k tokensUpdated today
    Auto-check passed

  • Kbn GitHub

    elastic/kibana

    Official

    GitHub interactions via gh CLI for the Kibana repo. An agent skill from elastic/kibana.

    21k GitHub stars~1.3k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Flaky Test Investigator

What does Flaky Test Investigator do?

Investigate Scout and FTR flaky test failures in Kibana. An agent skill from elastic/kibana. Flaky Test Investigator is an agent skill from elastic/kibana, published by the product's own GitHub organization. Investigate Scout and FTR flaky test failures in Kibana.

When should I use Flaky Test Investigator?

Flaky Test Investigator fits situations like: triaging a failed-test issue; A Buildkite-reported failure; A test path that has been failing intermittently; any time the user asks to look at a flaky test.

How do I install Flaky Test Investigator in Claude Code?

Run `npx skills add elastic/kibana --skill flaky-test-investigator -a claude-code`. Or copy the skill folder (.agents/skills/flaky-test-investigator in elastic/kibana) into .claude/skills/flaky-test-investigator in your project. Claude Code loads it when a task matches its description.

How do I install Flaky Test Investigator in Codex?

Run `npx skills add elastic/kibana --skill flaky-test-investigator -a codex`. Or copy the skill folder (.agents/skills/flaky-test-investigator in elastic/kibana) into .agents/skills/flaky-test-investigator in your project. Codex loads it when a task matches its description.

Can I use Flaky Test Investigator in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add elastic/kibana --skill flaky-test-investigator -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/flaky-test-investigator, .gemini/skills/flaky-test-investigator, .github/skills/flaky-test-investigator and .opencode/skills/flaky-test-investigator in your project.

What does Flaky Test Investigator need to run?

SKILL.md names no scripts, command-line tools or credentials: Flaky Test Investigator is instructions for the agent only. Our summary lists: Docker.

Does Flaky Test Investigator access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Flaky Test Investigator safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Flaky Test Investigator use?

Flaky Test Investigator has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.

How many tokens does Flaky Test Investigator use?

About 4.4k tokens (SKILL.md is roughly 17k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.2k tokens, read only when the agent opens those files.

What are the alternatives to Flaky Test Investigator?

Skills that share tags, products or a category with Flaky Test Investigator: Pester Failure Analysis (PowerShell/PowerShell, 56k stars), Cucumber and Playwright E2E Tests (langgenius/dify, 158k stars), Diagnose Playwright Failure as Product Bug (appsmithorg/appsmith, 41k stars) and Apple Container Test Runner (RustPython/RustPython, 22k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Flaky Test Investigator?

elastic (a GitHub organization, an official publisher) maintains it in elastic/kibana, which has 21,310 GitHub stars. The repository holds 40 skills in this directory. The repository was last updated on October 11, 2026.

Source: elastic/kibana on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.