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.

74

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Overview
Quality
Evals
Security
Files

Quality

Content

85%

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

The body is highly actionable with executable code, a clear multi-step workflow, and well-structured one-level-deep references. Its only weakness is mild verbosity in the Overview, which re-states context already in the description.

Suggestions

Trim the Overview's restatement of what JUnit XML is and the CI-tool list, since both already appear in the description; lead with the hierarchy and schema specifics instead.

Consider moving the Python parser into scripts/parse_junit.py (the code comment already names that path) and referencing it, keeping SKILL.md as overview.

DimensionReasoningScore

Conciseness

Mostly efficient and information-dense, but the Overview re-explains what JUnit XML is and repeats the CI-tool list already in the description; some prose could be tightened.

2 / 3

Actionability

Provides fully executable Python (parse, classify, reliability, per_suite) plus a Node.js parser and CI workflow YAML in the reference file — copy-paste ready, not pseudocode.

3 / 3

Workflow Clarity

A clear Step 1→7 sequence with embedded guardrails (handle both root shapes, test with 'is None', group by (classname, name), treat time=0 as not measured); the task is read-only analysis so no destructive validation loop is required.

3 / 3

Progressive Disclosure

SKILL.md is an overview that points one level deep to references/junit-xml-parsing.md (a real, verified file) for the Node.js parser and CI wiring, with clearly signaled links.

3 / 3

Total

11

/

12

Passed

Description

100%

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

The description is specific, third-person, and complete with an explicit 'Use when' trigger and clear disambiguation from adjacent skills. It is a strong, concise trigger description with no notable weaknesses.

DimensionReasoningScore

Specificity

Lists multiple concrete actions: 'Parses JUnit-format XML reports... into structured... per-suite and per-case metrics tables', 'groups failures by classname for trend analysis', and 'distinguishes new failures vs flakes'. This matches the anchor for listing several specific concrete actions, not just naming a domain.

3 / 3

Completeness

Explicitly answers both what (parse/aggregate/distinguish flakes) and when ('Use when the downstream consumer is a dashboard, script, or aggregator'), with an explicit 'Use when' clause present.

3 / 3

Trigger Term Quality

Covers natural terms a user would say ('JUnit', 'XML reports', 'CI', 'dashboard', 'flaky', 'aggregator') with good variation; not jargon-only or generic.

3 / 3

Distinctiveness Conflict Risk

Clear niche (JUnit XML machine-readable analytics) and explicitly disambiguated from 'test-run-summary-author' and a cross-run aggregator, so it is unlikely to trigger for the wrong skill.

3 / 3

Total

12

/

12

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