CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

test-optimization-testing

Validate v5 compatibility when adding or modifying Test Optimization or test framework integration tests in dd-trace-js.

67

Quality

84%

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

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.

A tight, high-signal instruction body that gives concrete commands, env vars, and file pointers for v5 validation with explicit failure/rollback handling. Main improvement room is making the workflow's step ordering explicit and providing one complete example test command.

Suggestions

Number the bullets (or group them under Before/During/After phases) so the validation sequence — setup, run, confirm, restore, report — is explicit rather than inferred from order.

Include one complete example invocation (e.g., the actual npm/yarn test command with MOCHA_VERSION=oldest prefixed) so the run step is copy-paste ready.

DimensionReasoningScore

Conciseness

The ~28-line body is lean with zero padding: no concept explanations, no throat-clearing, and every bullet is operational ('temporarily set only the root package.json version to "5.0.0"'), assuming Claude's competence throughout.

5 / 5

Actionability

Concrete, executable specifics are present (MOCHA_VERSION=oldest, JEST_VERSION=oldest, the package.json version edit, .github/workflows/test-optimization.yml, DD_MAJOR from version.js), but full copy-paste-ready test commands are left as 'its normal command', leaving minor gaps.

4 / 5

Workflow Clarity

Bullets follow a clear temporal order (check versions → write tests → set v5 → run and confirm → restore → report) with explicit validation checkpoints ('Confirm affected tests ran or had justified feature skips'; 'Restore the original package.json version even if validation fails'), but the sequence is implied by bullet order rather than explicitly structured as numbered steps.

4 / 5

Progressive Disclosure

This is a simple single-purpose skill under 50 lines with no bundle files (references/, scripts/, assets/ are absent) and no external references needed; the single-heading bullet list is appropriately organized, so the simple-skill exception applies.

5 / 5

Total

18

/

20

Passed

Description

75%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 concise, well-targeted description that clearly states what the skill does and when to use it, with excellent niche distinctiveness. It is held back from the top tier only by thin action coverage and limited keyword variations.

Suggestions

Enumerate the concrete validation actions in the description (e.g., running affected tests under both current and v5 framework configurations via MOCHA_VERSION/JEST_VERSION) so the 'what' is more than a single verb.

Add one or two natural synonym phrases users might say, such as 'framework version compatibility' or the test framework names (mocha, jest), to broaden trigger coverage.

DimensionReasoningScore

Specificity

The description names the domain concretely ('Test Optimization or test framework integration tests in dd-trace-js') but states only one action — 'Validate v5 compatibility' — matching the anchor for domain plus 1-2 concrete actions without comprehensive coverage of what validation entails.

3 / 5

Completeness

It explicitly answers both parts: the 'what' ('Validate v5 compatibility') and a concrete 'when' trigger phrase ('when adding or modifying Test Optimization or test framework integration tests in dd-trace-js'), matching the top anchor.

5 / 5

Trigger Term Quality

Relevant keywords like 'v5', 'Test Optimization', 'integration tests', and 'dd-trace-js' are natural for this repo's contributors, but common variations and synonyms (e.g., framework names like mocha/jest, 'version compatibility', 'CI matrix') are missing, fitting the 'some relevant keywords but missing variations' anchor.

3 / 5

Distinctiveness Conflict Risk

The niche is highly specific — v5 compatibility validation for Test Optimization tests in a named repository — giving it distinct triggers with minimal overlap risk against any generic testing skill.

5 / 5

Total

16

/

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

DataDog/dd-trace-js

Path

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