CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/junit-xml-analysis

Parses JUnit-format XML reports (the de-facto interchange format every CI ingests - Jenkins, GitHub Actions, GitLab, Buildkite, CircleCI) into structured, machine-readable per-suite and per-case metrics tables (passed / failed / errored / skipped, time, classname, message, stack), groups failures by classname for trend analysis, and distinguishes "new failures vs flakes" by cross-referencing the `flakyFailure` and `rerunFailure` rerun elements. Use when the downstream consumer is a dashboard, script, or aggregator - not when the goal is a human-readable prose summary (use test-run-summary-author for that). Single-run, in-XML aggregation only; for cross-run cross-environment roll-ups, use a cross-run test-suite aggregator.

90

Quality

90%

Does it follow best practices?

Impact

Average score across 10 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Overview
Quality
Evals
Security
Files

Quality

Content

86%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, actionable skill body with executable code and clean one-level-deep references. The main improvement opportunity is adding an explicit parse-output validation checkpoint in the workflow.

DimensionReasoningScore

Conciseness

Largely lean and code-first with no library tutorials or basic-concept padding; the Overview and a few explanatory paragraphs (e.g., the falsy-Element caveat) could be tightened slightly, keeping it just short of fully efficient.

4 / 5

Actionability

Provides fully executable, copy-paste-ready Python (parse_junit, classify, reliability, per_suite) covering both root shapes, fault classification, flake detection, and aggregation, with the Node.js parser and CI workflow in the referenced file.

5 / 5

Workflow Clarity

A clearly numbered Steps 1–7 sequence with most checkpoints present, but no explicit output-validation or parse-error recovery loop; given batch XML parsing, an explicit validate-step would lift it to a 5.

4 / 5

Progressive Disclosure

SKILL.md serves as a concise overview with the Node.js parser and CI workflow split into a real one-level-deep reference file (references/junit-xml-parsing.md), referenced twice via clear markdown links and an organized References section.

5 / 5

Total

18

/

20

Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A highly specific, well-triggered description that clearly separates this skill from neighbors via explicit anti-triggers and scope limits. The only minor gap is the absence of a file-extension trigger term like ".xml".

DimensionReasoningScore

Specificity

Lists multiple concrete actions — parsing into per-suite/per-case metrics with explicit fields (passed/failed/errored/skipped, time, classname, message, stack), grouping failures by classname for trend analysis, and distinguishing new vs flakes via rerun elements — giving comprehensive coverage.

5 / 5

Completeness

Explicitly answers both what (parses and aggregates JUnit XML into structured metrics) and when ("Use when the downstream consumer is a dashboard, script, or aggregator"), plus a concrete anti-trigger pointing to test-run-summary-author.

5 / 5

Trigger Term Quality

Strong natural-term coverage ("JUnit XML", "JUnit-format XML reports", "dashboard, script, or aggregator", "flakyFailure", "rerunFailure") with clear synonyms, but no explicit file extension like ".xml" and a few common phrasings are absent.

4 / 5

Distinctiveness Conflict Risk

Clear niche bounded by named alternatives (test-run-summary-author, cross-run test-suite aggregator) and an explicit scope limit ("Single-run, in-XML aggregation only"), minimizing wrong-skill triggering.

5 / 5

Total

19

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

Reviewed

Table of Contents