CtrlK
BlogDocsLog inGet started
Tessl Logo

generating-test-reports

Generate structured test reports with pass/fail rollups, coverage summaries, and test artifacts. Use when the user is asking for test-result packaging or delivery, not for root-cause debugging or feature implementation.

59

Quality

69%

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

Fix and improve this skill with Tessl

tessl review fix ./bundled/skills/generating-test-reports/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

51%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.

The body is concise and well-organized as an overview, but it is more descriptive than instructional: it never points to the bundled scripts, template, or reference files, and offers no executable workflow or validation steps for actually producing a report.

Suggestions

Add a 'How to generate' section that invokes the bundled scripts in sequence, e.g. `python scripts/aggregate_results.py ...` then `python scripts/generate_report.py ...`, so the guidance is executable rather than descriptive.

Link the existing bundle from the overview — reference assets/report_template.html for output formatting and references/ (e.g. report_format_schema.json) for the report schema — so progressive disclosure actually routes Claude to the detailed materials.

Include a validation checkpoint (e.g. confirm the generated report against the schema / sample_test_results.json before delivering) to give the report-generation workflow an explicit feedback loop.

DimensionReasoningScore

Conciseness

Lean ~25-line body with clear sections and no padding or explanation of concepts Claude already knows; every line earns its place.

5 / 5

Actionability

The body describes deliverables ('Test execution summary with totals and failure clusters', 'Coverage snapshot and quality-gate status') but gives no commands, code, or steps, and never references the bundled generate_report.py / aggregate_results.py scripts or report_template.html that exist — high-level hints without specific steps to execute.

2 / 5

Workflow Clarity

Sections are categorical (When to Use, Typical Outputs) rather than sequenced; there is no step list for turning artifacts into a report and no validation checkpoint, even though a generate/aggregate pipeline clearly exists in the bundle.

2 / 5

Progressive Disclosure

The body is well-sectioned and not a wall of text, but it provides no navigation to the real bundle files in scripts/, assets/, and references/ — the overview fails to signal the detailed materials that exist one level deep.

3 / 5

Total

12

/

20

Passed

Description

87%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 strong, third-person description that pairs a concrete capability statement with an explicit 'Use when' trigger and a negative boundary. Keyword coverage is good rather than comprehensive, but distinctiveness and completeness are excellent.

DimensionReasoningScore

Specificity

Lists several concrete actions — 'pass/fail rollups, coverage summaries, and test artifacts' — under a clear 'Generate structured test reports' verb; minor gaps in coverage keep it just below a 5.

4 / 5

Completeness

Explicitly answers both what ('Generate structured test reports with pass/fail rollups, coverage summaries, and test artifacts') and when ('Use when the user is asking for test-result packaging or delivery') with concrete trigger phrasing.

5 / 5

Trigger Term Quality

Natural phrases like 'test-result packaging or delivery', 'test reports', 'pass/fail', and 'coverage' give good keyword coverage, though common variants ('test summary', 'test results', tool names like pytest/JUnit) are absent.

4 / 5

Distinctiveness Conflict Risk

A clear niche (test-report packaging) plus an explicit negative boundary ('not for root-cause debugging or feature implementation') minimizes conflict with adjacent skills.

5 / 5

Total

18

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository
foryourhealth111-pixel/Vibe-Skills
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.