CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

test-value

Improve test value and feedback cost when auditing slow, flaky, redundant or brittle tests; choosing tests during implementation; or reviewing test changes before a commit or PR. Keep ordinary implementation and pre-commit use scoped to the affected behavior, not a repository-wide audit.

Quality

83%

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

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.

A lean, well-structured judgment skill: a decision table, explicit questions, and concrete verification probes make the guidance actionable despite the absence of code, and the two reference files are properly disclosed one level deep. The main cost is the long "Learn from use" maintenance section and prose-embedded rather than loop-form validation checkpoints.

DimensionReasoningScore

Conciseness

The body is dense, compressed guidance with no padding or explanation of concepts Claude already knows; however, the five-paragraph "Learn from use" section is lengthy self-maintenance meta-guidance that could be trimmed.

4 / 5

Actionability

Concrete decision tools throughout: an eight-row evidence-to-decision table, three explicit questions for new or changed tests, and executable verification procedures ("reproduce the original failure with the regression and verify the fix passes"; "try a valid alternative and the original bad result; the former should pass and the latter fail"). Minor gaps remain, as guidance stays at the principle level in a few places.

4 / 5

Workflow Clarity

A clear sequence (choose scope, establish an independent basis, decide, check discrimination, control feedback cost, report) with explicit validation checkpoints ("Confirm that the intended tests actually executed, including filters, collection and skips"; retire tests only "after checking for remaining consumers"). Checkpoints are embedded in prose rather than an explicit validate-fix-retry loop, keeping it below anchor 5.

4 / 5

Progressive Disclosure

SKILL.md is a genuine overview with two clearly signaled, conditionally gated, one-level-deep references ("Read [audit.md](references/audit.md)"; "Read [decision-examples.md](references/decision-examples.md) when dealing with…"); both files exist and nest no further references, and content is appropriately split.

5 / 5

Total

17

/

20

Passed

Description

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

A strong description that explicitly covers what the skill does and gives three concrete trigger scenarios with natural vocabulary including test-pathology synonyms. Its main limitations are the abstract framing of "improve test value and feedback cost" and minor overlap with general code-review skills in the pre-commit trigger.

DimensionReasoningScore

Specificity

Names the test-value domain and several concrete activities ("auditing slow, flaky, redundant or brittle tests", "choosing tests during implementation", "reviewing test changes before a commit or PR"), with minor gaps — "improve test value and feedback cost" is an outcome statement rather than a concrete action.

4 / 5

Completeness

Explicitly answers both what ("Improve test value and feedback cost" via auditing, choosing and reviewing tests) and when (three concrete trigger scenarios: "when auditing…; choosing tests during implementation; or reviewing test changes before a commit or PR").

5 / 5

Trigger Term Quality

Natural user phrasings are present ("slow, flaky, redundant or brittle tests", "auditing", "reviewing test changes", "commit or PR") including synonyms for test pathologies, but common variations like "test suite", "coverage" or "CI failures" are missing.

4 / 5

Distinctiveness Conflict Risk

A clear test-value/testing-judgment niche with distinct triggers, but "reviewing test changes before a commit or PR" carries minor overlap risk with generic code-review and PR-review skills.

4 / 5

Total

17

/

20

Passed

Validation

87%

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

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository

tt-a1i/archify

Path

.agents/skills/test-value/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.