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.

67

Quality

82%

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

SKILL.md
Quality
Evals
Security

Quality

Content

65%

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

The body is admirably concise and well-structured but functions mostly as a 'when to use' guide rather than an actionable instruction set, and it fails to point at the bundled scripts and assets that would make it executable. The main gaps are actionability and progressive disclosure of the provided bundle.

Suggestions

Add a short 'How to use' section that invokes the bundled scripts (e.g. aggregate_results.py → generate_report.py) with concrete commands or a minimal code example to lift actionability.

Reference the bundled files explicitly from the body — link aggregate_results.py, generate_report.py, report_template.html, and sample_test_results.json so the bundle is discoverable.

Spell out a minimal sequenced workflow with a validation checkpoint (e.g. validate aggregated results before rendering the report) to address the workflow-clarity gap for batch report generation.

DimensionReasoningScore

Conciseness

The ~30-line body is lean with no padding or explanation of concepts Claude already knows; every section (Purpose, When to Use, Not For, Typical Outputs, Related Skills) earns its place, matching the level-3 'lean and efficient' anchor.

3 / 3

Actionability

The body describes outputs ("Turning raw pytest, JUnit, or coverage artifacts into a concise report") but provides no executable commands, code, or usage of the bundled scripts, so it stops at the level-2 'some concrete guidance but incomplete' rather than level-3 copy-paste-ready instruction.

2 / 3

Workflow Clarity

No sequenced process or validation checkpoints are given; the body lists when-to-use cases and output types but never sequences the implied aggregate → generate → analyze pipeline, capping it at the level-2 'sequence present but checkpoints missing' rather than the simple-skill level-3 case where a single action is unambiguous and complete.

2 / 3

Progressive Disclosure

Sections are well-organized and the body is a clean overview, but it never signals the bundled scripts, assets, or references (e.g. aggregate_results.py, generate_report.py, report_template.html), so material that should be one level deep is undiscoverable — the level-3 anchor requires clearly signaled one-level references, which are absent.

2 / 3

Total

9

/

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 concise, third-person, and answers both 'what' and 'when' with natural trigger terms and an explicit non-goals boundary. It is a strong description that meets the top anchor on every dimension.

DimensionReasoningScore

Specificity

"Generate structured test reports with pass/fail rollups, coverage summaries, and test artifacts" names multiple specific concrete actions, matching the level-3 anchor rather than the single-domain level-2 example.

3 / 3

Completeness

It states both what (generate structured test reports with rollups/coverage/artifacts) and when ("Use when the user is asking for test-result packaging or delivery"), matching the level-3 anchor that requires explicit triggers; it is not the level-2 case where 'when' is only implied.

3 / 3

Trigger Term Quality

Natural user-facing terms appear — "test reports", "test-result packaging or delivery", "pass/fail", "coverage" — giving good coverage of phrases a user would actually say, beyond the level-2 "some keywords" anchor.

3 / 3

Distinctiveness Conflict Risk

The test-report niche is clear and the explicit "not for root-cause debugging or feature implementation" carve-out makes conflict with adjacent skills unlikely, fitting the level-3 distinct-niche anchor.

3 / 3

Total

12

/

12

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.