agentleFS
Sign inStart free
katalon-labskatalon-labs/true-skills/.github/skills/analyze-failures/SKILL.md

analyze-failures

Skill10 starsChanged 5 months agoMITView on GitHub

Triage Katalon True Platform/TestOps test failures and file defects. Use when you need to investigate failed test results, classify each failure as product defect vs automation defect vs environment/data issue, cluster failures by common signature, find likely root cause from execution data, and optionally create ALM-linked defects for real product bugs. This is failure diagnosis and defect filing; for the overall ship/no-ship release call use release-analyze, and for repairing the tests themselves use test-maintenance. Written for the manual tester and the automation tester looking at a red run and needing to know whether the application broke or the test did.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill for the failure-analysis part of the report/analysis stage: turn a set of failed results into a diagnosis and, when …

    line 8
  2. Very specific:

    Available via MCP: read results (read_test_result, read_execution_test_results, find_test_results, read_execution), defect context …

    line 12
  3. Very specific:

    Read references/failure-triage.md before classifying.

    line 53

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Katalon Analyze Failures

Use this skill for the failure-analysis part of the report/analysis stage: turn a set of failed results into a diagnosis and, when warranted, filed defects. The core value is classification — separating real product bugs from automation and environment noise.

Availability Boundary

  • Available via MCP: read results (read_test_result, read_execution_test_results, find_test_results, read_execution), defect context (fetch_defect_data), ALM discovery + filing (find_alm_integration_projects, create_defect).
  • Not directly available: AI root-cause summarization and automation-error-pattern analytics are TestOps/Studio product features, not MCP calls — narrate their availability, do not claim to call them. create_defect requires a known failed test result ID and ALM integration details; there is no ID-less defect creation.

Triage Workflow

+---------------------+     +----------------------+     +----------------------+
| Collect failures    | --> | Classify each        | --> | Cluster by signature |
| read results        |     | product/auto/env     |     |                      |
+---------------------+     +----------------------+     +----------------------+
                                                                   |
                                                                   v
                                                         +----------------------+
                                                         | File defects (asked) |
                                                         +----------------------+

Steps and tool rules

  1. Collect the failures. find_test_results (recent/specific) or read_execution_test_results for a run; read_test_result per failed case for detail.
  2. Classify each failure into one bucket:
    • Product defect — the application behaved wrong (assertion on real behavior failed, unexpected error/state). Candidate for a filed defect.
    • Automation defect — the test is wrong (bad locator, timing, stale data, broken step). Route to test-maintenance.
    • Environment / data — infra, account, network, fixture, or AUT-state issue. Route to re-run after fix.
  3. Cluster by signature. Group failures with the same error message / step / object so one root cause is not filed as N defects.
  4. Check existing defects. fetch_defect_data to avoid duplicate filings.
  5. File defects only when asked and only for product defects. find_alm_integration_projects -> create_defect with the failed result ID. Ask before creating unless the user explicitly requested defect filing.
  6. Report. Per cluster: classification, likely cause, affected cases, and action (file / repair / re-run).

Prompt recipes

  • Triage the failures in execution 8842: which are product bugs vs flaky tests vs environment?
  • Cluster today's failed results by root cause and tell me what to file.
  • File defects for the confirmed product bugs in the checkout suite and link them to the failed results.

Hand-offs

  • Automation defects / flaky -> test-maintenance.
  • Ship decision from the failure picture -> release-analyze.
  • Coverage gap exposed by a failure -> test-plan.

Read references/failure-triage.md before classifying. Consult the orchestrator's references/unavailable-capabilities.md for defect-filing boundaries.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free