coverage-report-analyzer
Coverage Report Analyzer - Auto-activating skill for Test Automation. Triggers on: coverage report analyzer, coverage report analyzer Part of the Test Automation skill category.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill coverage-report-analyzerOverall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is severely underdeveloped, essentially just restating the skill name without providing any meaningful information about capabilities or usage triggers. It lacks concrete actions, natural user keywords, and explicit guidance for when Claude should select this skill. The duplicate trigger term suggests this may be auto-generated boilerplate.
Suggestions
Add specific concrete actions like 'Parse coverage reports (lcov, cobertura, istanbul), identify untested code paths, calculate coverage percentages, highlight coverage gaps'
Include natural trigger terms users would say: 'code coverage', 'test coverage', 'coverage percentage', 'uncovered lines', 'coverage threshold', '.lcov', 'cobertura.xml'
Add an explicit 'Use when...' clause: 'Use when the user asks about test coverage, wants to analyze coverage reports, needs to identify untested code, or mentions coverage thresholds'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Coverage Report Analyzer') without describing any concrete actions. There are no specific capabilities listed like 'parse coverage reports', 'identify untested code', or 'generate coverage summaries'. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and the 'when' clause is just a circular reference to the skill name. There is no explicit guidance on when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | The trigger terms are just the skill name repeated twice ('coverage report analyzer, coverage report analyzer'). Missing natural user terms like 'code coverage', 'test coverage', 'coverage percentage', 'uncovered lines', or file extensions like '.lcov'. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'coverage report' is somewhat specific to test coverage analysis, which provides some distinctiveness. However, without concrete actions or clear triggers, it could still conflict with general testing or reporting skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill content is essentially a placeholder template with no actual instructional value. It contains only meta-descriptions of what a coverage report analyzer skill might do, without any concrete guidance on how to analyze coverage reports, interpret results, or take action based on coverage data. The content fails on all dimensions by being verbose yet empty of actionable information.
Suggestions
Add concrete code examples showing how to generate and parse coverage reports (e.g., Jest's --coverage output, pytest-cov reports)
Include specific commands for common coverage tools and how to interpret their output formats (lcov, cobertura, etc.)
Define a clear workflow: generate report -> parse results -> identify gaps -> prioritize improvements
Add examples of coverage thresholds, how to configure them, and how to interpret coverage metrics (line, branch, function coverage)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual value. Phrases like 'provides automated assistance' and 'follows industry best practices' are vague filler that Claude doesn't need. | 1 / 3 |
Actionability | There is zero concrete guidance - no code examples, no commands, no specific steps for analyzing coverage reports. The content only describes what the skill supposedly does without showing how to do anything. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps for analyzing coverage reports, no validation checkpoints, and no actual process to follow. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of unhelpful text with no references to detailed materials, no links to examples, and no structured navigation to additional resources. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
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.