generating-test-reports

tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill generating-test-reports

This skill generates comprehensive test reports with coverage metrics, trends, and stakeholder-friendly formats (HTML, PDF, JSON). It aggregates test results from various frameworks, calculates key metrics (coverage, pass rate, duration), and performs trend analysis. Use this skill when the user requests a test report, coverage analysis, failure analysis, or historical comparisons of test runs. Trigger terms include "test report", "coverage report", "testing trends", "failure analysis", and "historical test data".

54%

Overall

Validation — 88%

Implementation — 7%

Activation — 100%

SKILL.md

Review

Evals

Validation

88%

Warnings & errors only

Criteria	Description	Result
metadata_version	'metadata' field is not a dictionary	Warning
license_field	'license' field is missing	Warning

	Total	14 / 16 Passed

Implementation

This skill content describes what test reporting is rather than instructing Claude how to do it. It lacks any executable code, specific commands, tool names, or concrete implementation details. The content reads like marketing copy explaining the concept rather than actionable guidance Claude can follow.

Suggestions

Replace abstract descriptions with concrete, executable code examples showing how to parse test results from specific frameworks (pytest, jest, etc.) and generate reports

Add specific commands or scripts for aggregating coverage data, e.g., 'coverage json -o coverage.json' or parsing pytest output

Include actual output format templates or schemas for the HTML/PDF/JSON reports Claude should generate

Remove the 'How It Works' and 'When to Use This Skill' sections entirely - this meta-information wastes tokens on things Claude can infer

Dimension	Reasoning	Score
Conciseness	The content is verbose and explains concepts Claude already knows (what test reports are, what coverage means). Sections like 'How It Works' and 'When to Use This Skill' describe rather than instruct, wasting tokens on obvious information.	1 / 3
Actionability	No concrete code, commands, or executable guidance provided. Examples describe what 'the skill will' do abstractly rather than showing actual commands, scripts, or tool invocations Claude should use to generate reports.	1 / 3
Workflow Clarity	Steps are vague descriptions ('Aggregate test results', 'Calculate code coverage') without specifying how to actually perform these actions. No validation checkpoints, no specific tools or commands, no error handling guidance.	1 / 3
Progressive Disclosure	Content has some structure with clear section headers, but everything is inline with no references to external files. The content that exists could be much more concise, and there's no separation of quick-start vs advanced content.	2 / 3
	Total	5 / 12 Passed

Activation

100%

This is a well-crafted skill description that excels across all dimensions. It provides specific capabilities, explicit trigger terms, clear guidance on when to use it, and occupies a distinct niche in test reporting. The description uses proper third-person voice and avoids vague language.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: 'generates comprehensive test reports', 'aggregates test results', 'calculates key metrics (coverage, pass rate, duration)', 'performs trend analysis', and specifies output formats (HTML, PDF, JSON).	3 / 3
Completeness	Clearly answers both what (generates test reports, aggregates results, calculates metrics, performs trend analysis) AND when ('Use this skill when the user requests a test report, coverage analysis, failure analysis, or historical comparisons').	3 / 3
Trigger Term Quality	Explicitly lists natural trigger terms users would say: 'test report', 'coverage report', 'testing trends', 'failure analysis', 'historical test data'. These are terms users would naturally use when needing this functionality.	3 / 3
Distinctiveness Conflict Risk	Has a clear niche focused specifically on test reporting and coverage metrics. The explicit trigger terms and specific domain (test frameworks, coverage metrics, trend analysis) make it unlikely to conflict with general documentation or code analysis skills.	3 / 3
	Total	12 / 12 Passed

Reviewed

16 days ago

Table of Contents

Validation Implementation Activation

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.