CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

engram-testing-coverage

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

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/testing-coverage/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 an efficient, well-structured instruction-only skill: a concrete TDD loop, actionable coverage rules, and an unusually clear division of verification ownership between local runs and PR CI, complete with real commands. Its only weaknesses are mild wordiness in the policy section and the absence of an example local verification command.

DimensionReasoningScore

Conciseness

The body is lean and directive with no explanations of concepts Claude already knows; the Verification Ownership section's policy sentences ("Verification is evidence about the candidate; CI is the automated execution venue...") are slightly abstract and could be tightened, keeping it just below 5.

4 / 5

Actionability

Concrete commands are given (`go test ./...`, `go test -tags e2e ./internal/server/...`) alongside specific directives like "run a focused regression test and tests for the affected package(s) locally"; the minor gap is that no example of the focused local command is shown, so it is mostly rather than fully executable.

4 / 5

Workflow Clarity

The TDD loop is a clearly numbered sequence with an inherent fail-test-then-implement feedback loop, and verification checkpoints are explicit ("Do not report CI evidence until those checks actually run", "Report checks that could not run as missing evidence"). It is not 5 because no explicit recovery step exists for a failing local run; not 3 because checkpoints are present and explicit.

4 / 5

Progressive Disclosure

The skill is under 50 lines, single-purpose, and requires no external references; its four clean sections (When to Use, TDD Loop, Coverage Rules, Verification Ownership) are well-organized, which per the rubric's simple-skill guidance earns a 5.

5 / 5

Total

17

/

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 correctly pairs a domain statement with an explicit trigger clause, but it undersells the skill's actual content: no concrete actions are named and the trigger vocabulary is narrower than the body's own use cases (bug fixes, refactoring). It is functional but generic for its niche.

Suggestions

Replace "TDD and coverage standards" with concrete capabilities, e.g., "Enforce test-driven development and targeted coverage verification for Engram changes: write failing tests first, cover error and edge paths, run focused package tests locally."

Broaden the trigger to the use cases the body already lists: "Trigger: when implementing behavior changes, fixing bugs, or refactoring branch-heavy logic in any Engram package."

Add natural user phrasings ("adding a feature", "writing tests", "code coverage") so the description matches what a user would actually say when they need this skill.

DimensionReasoningScore

Specificity

"TDD and coverage standards for Engram" names the domain but "standards" is generic — no concrete capabilities (e.g., write failing tests, measure branch coverage) are stated, matching the anchor 'Names the domain but actions are minimal or generic'.

2 / 5

Completeness

Both a what ("TDD and coverage standards for Engram") and an explicit when ("Trigger: When implementing behavior changes in any package") are present. Not 5 because the what is vague ("standards") and the when covers only behavior changes, not bug fixes or refactoring that the body itself lists.

4 / 5

Trigger Term Quality

Relevant keywords exist ("TDD", "coverage", "behavior changes", "package"), but common natural phrasings like "adding a feature", "fixing a bug", or "writing tests" are missing, so keyword coverage is partial rather than good.

3 / 5

Distinctiveness Conflict Risk

Scoping to a named project (Engram) with a defined trigger makes it mostly distinct with only minor overlap risk against generic testing or code-review skills; the trigger "implementing behavior changes" is broad enough to prevent a 5.

4 / 5

Total

13

/

20

Passed

Validation

100%

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

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.