CtrlK
BlogDocsLog inGet started
Tessl Logo

write-e2e

Write E2E tests for the Datadog Agent using the new-e2e framework with fakeintake assertions

64

Quality

78%

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 ./.claude/skills/write-e2e/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

100%Weight 40%Scale 1-3

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 exemplary lean overview: concise, packed with executable commands, a clearly sequenced workflow with validation checkpoints and a feedback pointer, and well-organized one-level-deep external references.

DimensionReasoningScore

Conciseness

The body is lean and efficient — a terse intro, a compact lookup table, a numbered checklist, and a brief output spec — with no padding or explanation of concepts Claude already knows, matching the 'every token earns its place' anchor.

3 / 3

Actionability

It provides fully executable commands (`go vet ./tests/<area>/...`, `dda inv new-e2e-tests.run --targets=...`, `grep -n 'TARGETS:.*<area>' ...`) that are copy-paste ready once the area placeholder is substituted, matching the 'fully executable code/commands' anchor.

3 / 3

Workflow Clarity

The 6-step checklist is clearly sequenced with two explicit validation checkpoints (compile-check at step 4, run-locally at step 5) and a feedback-loop pointer ('See ... Validating E2E tests if it fails'), matching the 'clear sequence with explicit validation steps' anchor.

3 / 3

Progressive Disclosure

The body is a clear overview that externalizes detail into a well-signaled, one-level-deep lookup table of repo references (AGENTS.md files, docs, CODEOWNERS, CI files) with explicit navigation guidance, matching the 'clear overview with well-signaled references' anchor.

3 / 3

Total

12

/

12

Passed

Description

57%Weight 40%Scale 1-3

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 concrete and occupies a clearly distinct niche, but it only names a single action, uses a narrow set of trigger terms, and lacks any explicit 'Use when...' trigger guidance, capping completeness at 2.

Suggestions

Add an explicit trigger clause, e.g. 'Use when writing or updating end-to-end tests for the Datadog Agent, or when asked to add E2E coverage for a check or feature.'

Broaden trigger-term coverage with natural variants a user would say, such as 'end-to-end tests', 'integration tests', or 'test the Agent on Linux/Windows'.

Expand the action list beyond 'Write E2E tests' to name additional concrete actions like 'add fakeintake payload assertions' or 'wire tests into CI'.

DimensionReasoningScore

Specificity

Names a concrete domain and tooling ('Write E2E tests', 'new-e2e framework', 'fakeintake assertions') but describes a single action rather than listing multiple concrete actions, matching the 'names domain and some actions' anchor rather than score 3.

2 / 3

Completeness

It clearly states what the skill does but has no 'Use when...' clause or equivalent trigger guidance, which per the judging guidelines caps completeness at 2; the strong 'what' keeps it above score 1.

2 / 3

Trigger Term Quality

Relevant keywords ('E2E tests', 'Datadog Agent') are present but the vocabulary is narrow and technical ('new-e2e', 'fakeintake'), missing common natural variations a user might say, so it fits 'some relevant keywords but missing common variations' rather than score 3.

2 / 3

Distinctiveness Conflict Risk

The narrow, tool-specific niche ('Datadog Agent' + 'new-e2e framework' + 'fakeintake assertions') gives it distinct triggers unlikely to overlap with other skills, matching the 'clear niche' anchor.

3 / 3

Total

9

/

12

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.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository
DataDog/datadog-agent
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.