engram-testing-coverage

TDD and coverage standards for Engram. Trigger: When implementing behavior changes in any package.

Quality

71%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/testing-coverage/SKILL.md

Quality

Content

86%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 concise, well-structured, and provides executable validation commands with a clear TDD sequence. The main gap is an explicit feedback loop for handling failing tests during the loop.

Suggestions

Add an explicit validate-fix-retry step, e.g. '4. If `go test ./...` fails, fix and re-run before proceeding; add edge/error-path tests before closing.'

Specify how to read the coverage output (e.g. expected thresholds or which packages to scrutinize) so the 'Report package coverage and total coverage' instruction is unambiguous.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence, defining the TDD loop, coverage rules, and validation commands with no padding or explanation of concepts Claude already knows.	5 / 5
Actionability	Validation commands are copy-paste ready ('go test ./...', 'go test -cover ./...'), while the TDD loop and coverage rules are actionable instructions rather than code; minor gaps keep it just below fully executable.	4 / 5
Workflow Clarity	The TDD loop is a clear numbered sequence and 'Validation Commands' plus the PR reporting step provide checkpoints, though an explicit validate-fix-retry loop for failing tests is only implied.	4 / 5
Progressive Disclosure	At under 50 lines, single-purpose, with no bundle files, the content is cleanly split into four well-organized sections, meeting the simple-skill exception for a top score.	5 / 5
	Total	18 / 20 Passed

Description

57%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 gives an explicit, scoped trigger and names its domain clearly, but the capability statement is a high-level label rather than a list of concrete actions. Strengthening the 'what' with specific behaviors would lift the lower dimensions.

Suggestions

Replace the label 'TDD and coverage standards for Engram' with concrete actions, e.g. 'Write failing tests, implement minimal passing code, and track Go package coverage for Engram.'

Broaden the trigger with natural phrasings users actually say, e.g. 'Use when adding a feature, fixing a bug, or refactoring branchy logic in any Engram package.'

Dimension	Reasoning	Score
Specificity	It names the domain ('TDD and coverage standards for Engram') but offers only generic labels rather than concrete actions such as writing failing tests or measuring coverage, matching the anchor for minimal/generic actions.	2 / 5
Completeness	Both a 'what' (TDD and coverage standards for Engram) and a 'when' (when implementing behavior changes) are present; the 'what' is somewhat label-like but the explicit trigger clause clears the bar above a 3.	4 / 5
Trigger Term Quality	It includes an explicit trigger ('When implementing behavior changes in any package') but misses common natural variations users would say like 'adding a feature', 'fixing a bug', or 'writing tests'.	3 / 5
Distinctiveness Conflict Risk	Scoping to 'Engram' plus the narrow TDD/coverage focus makes it mostly distinct with only minor overlap risk against other testing-related skills.	4 / 5
	Total	13 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: Gentleman-Programming/engram
Path: skills/testing-coverage/SKILL.md
Commit: 47f281c

Reviewed: 6 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.