coverage-enhancer
Analyze existing test suites and source code to suggest additional unit tests that improve test coverage. Use this skill when working with test files and source code to identify untested code paths, missing edge cases, uncovered branches, untested error conditions, and gaps in test coverage. Supports major testing frameworks (pytest, Jest, JUnit, Go testing, etc.) and generates targeted test suggestions based on coverage analysis.
Install with Tessl CLI
npx tessl i github:ArabelaTso/Skills-4-SE --skill coverage-enhancer93
Does it follow best practices?
Validation for skill structure
Discovery
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.
This is a well-crafted skill description that excels across all dimensions. It provides specific concrete actions, includes natural trigger terms users would use, explicitly states both what the skill does and when to use it, and carves out a distinct niche in test coverage analysis that won't conflict with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Analyze existing test suites and source code', 'suggest additional unit tests', 'identify untested code paths, missing edge cases, uncovered branches, untested error conditions, and gaps in test coverage', 'generates targeted test suggestions based on coverage analysis'. | 3 / 3 |
Completeness | Clearly answers both what ('Analyze existing test suites and source code to suggest additional unit tests') AND when ('Use this skill when working with test files and source code to identify untested code paths, missing edge cases...'). Has explicit 'Use this skill when...' clause. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'test suites', 'source code', 'unit tests', 'test coverage', 'test files', 'edge cases', 'pytest', 'Jest', 'JUnit', 'Go testing'. Good coverage of both general terms and specific framework names. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on test coverage analysis and test suggestion generation. The combination of coverage analysis, specific testing frameworks, and test generation creates a distinct trigger profile unlikely to conflict with general coding or documentation skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, highly actionable skill with excellent workflow clarity and progressive disclosure. The main weakness is verbosity - the skill explains concepts Claude already knows (what coverage metrics mean, basic testing concepts) and includes repetitive pattern examples that could be consolidated. The executable code examples and clear workflow are strong points.
Suggestions
Remove explanatory sections about what coverage metrics mean (line coverage, branch coverage definitions) - Claude already knows these concepts
Consolidate the 5 similar coverage patterns into 2-3 representative examples with a note that the same approach applies to other patterns
Remove the 'Best Practices' section which contains generic testing advice Claude already knows (test behavior not implementation, keep tests isolated, etc.)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but verbose. It includes some unnecessary explanations (e.g., explaining what line/branch/function coverage means to Claude) and repeats similar patterns multiple times. The content could be tightened significantly while preserving clarity. | 2 / 3 |
Actionability | Excellent actionability with complete, executable code examples throughout. Every pattern includes ready-to-use test code with pytest syntax, clear assertions, and explanatory comments. The coverage tool commands are copy-paste ready. | 3 / 3 |
Workflow Clarity | Clear 5-step workflow with explicit sequencing (Analyze Tests → Analyze Source → Prioritize → Generate → Integrate Tools). Each step has concrete actions and the prioritization framework provides clear decision-making guidance for coverage gaps. | 3 / 3 |
Progressive Disclosure | Well-structured with clear sections progressing from core capabilities to workflow to patterns to examples. References to language-specific files (references/python_coverage.md, etc.) are one level deep and clearly signaled. Content is appropriately organized. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (704 lines); consider splitting into references/ and linking | Warning |
Total | 10 / 11 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.