test-coverage

MUST be used whenever fixing test coverage for a Flows app to meet the 80% line coverage hard gate. This skill finds AND fixes coverage gaps — it configures tooling, writes missing tests, covers untested paths, and refactors code for testability. It does not just report. Triggers: test coverage, fix tests, write tests, add tests, coverage fix, 80% coverage, coverage gate, missing tests, testability, vitest coverage, jest coverage.

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

85%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 highly actionable and well-sequenced with validation checkpoints, but it is a monolithic single file with some redundancy and bulky inlined templates that have not been split into reference files.

Suggestions

Move the per-file-type test templates (hooks, services/utils, components) and the testability-fix table into reference files under references/, linking to them from the steps to reduce inlined bulk.

De-duplicate the repeated coverage exclude array and the repeated coverage re-run commands by defining them once and referencing back.

Tighten repeated guidance such as the context-injection-vs-vi.mock advice, which is restated across Steps 4 and 6.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands and code templates, but contains redundant repetition (the exclude array shown twice, coverage re-run commands repeated, context-injection guidance restated).	4 / 5
Actionability	Fully executable — concrete bash commands, full TypeScript test templates for hooks/services/components, and exact config snippets that are copy-paste ready and cover the common cases.	5 / 5
Workflow Clarity	Seven clearly sequenced steps with explicit validation feedback loops ('Re-run tests after each fix until all tests pass', 'Run coverage again after adding tests') and a final re-run, satisfying the batch/destructive validation requirement.	5 / 5
Progressive Disclosure	No bundle files exist and the skill is a single ~370-line SKILL.md; it has strong section structure but bulky inlined reference-style content (full test templates, the testability-fix table) that could live in separate files with no deeper-reference signaling.	3 / 5
	Total	17 / 20 Passed

Description

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

The description is strong: concrete capabilities, comprehensive natural triggers, and an explicit what/when structure scoped to a specific niche. Its only weakness is mild overlap risk from generic test-writing trigger phrases.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'configures tooling, writes missing tests, covers untested paths, and refactors code for testability' — giving comprehensive coverage of capabilities.	5 / 5
Completeness	Explicitly answers both what ('finds AND fixes coverage gaps...') and when ('MUST be used whenever fixing test coverage for a Flows app to meet the 80% line coverage hard gate' plus a Triggers clause).	5 / 5
Trigger Term Quality	Comprehensive natural trigger terms ('test coverage, fix tests, write tests, add tests, coverage fix, 80% coverage, coverage gate, missing tests, testability') plus framework synonyms ('vitest coverage, jest coverage').	5 / 5
Distinctiveness Conflict Risk	Scoped to a clear niche ('Flows app', '80% line coverage hard gate') with distinct triggers, but generic terms like 'write tests, add tests' create minor overlap with general testing skills.	4 / 5
	Total	19 / 20 Passed

Validation

87%

Warnings & errors only

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

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
metadata_version	'metadata.version' is missing	Warning

	Total	14 / 16 Passed

Repository: cognitedata/builder-skills
Path: skills/test-coverage/SKILL.md
Commit: c87160a

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.