CtrlK
BlogDocsLog inGet started
Tessl Logo

write-e2e

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

60

Quality

71%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./.claude/skills/write-e2e/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a well-structured orchestration skill that efficiently directs Claude to the right resources and provides a clear workflow with validation checkpoints. Its main weakness is the lack of any inline code examples or test templates — all concrete test-writing guidance is delegated to external files, which reduces standalone actionability. However, for a skill that coordinates across multiple complex subsystems, this delegation is reasonable.

Suggestions

Add a minimal inline Go test skeleton showing the typical structure (suite setup, environment provisioning, fakeintake assertion) so Claude has an executable starting point without needing to read external files first.

DimensionReasoningScore

Conciseness

The content is lean and efficient. It uses a table for navigation, a numbered checklist for workflow, and avoids explaining concepts Claude already knows (Go testing, CI, etc.). Every section earns its place.

3 / 3

Actionability

The skill provides concrete commands for compilation (`go vet`), running tests (`dda inv new-e2e-tests.run`), and CI checking (`grep`), but delegates all actual test-writing guidance (framework API, fakeintake assertions, code patterns) to external files. There are no executable code examples or test templates in the skill itself.

2 / 3

Workflow Clarity

The checklist provides a clear sequence from understanding the feature through implementation to validation. It includes explicit validation checkpoints (compile check at step 4, local run at step 5 with error recovery reference, CI wiring check at step 6) and a feedback loop for failures.

3 / 3

Progressive Disclosure

The navigation table provides clear, one-level-deep references to specific files for each concern (framework API, fakeintake API, setup docs, examples, real tests). Content is appropriately split between the overview skill and referenced materials, with well-signaled paths.

3 / 3

Total

11

/

12

Passed

Description

57%

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 domain-specific and clearly identifies a narrow technical niche (Datadog Agent E2E testing with specific frameworks), which gives it strong distinctiveness. However, it lacks an explicit 'Use when...' clause and could benefit from listing more concrete actions and natural trigger term variations to improve completeness and discoverability.

Suggestions

Add a 'Use when...' clause, e.g., 'Use when the user asks to write, update, or debug end-to-end tests for the Datadog Agent using the new-e2e framework or fakeintake.'

Include natural keyword variations such as 'end-to-end tests', 'e2e testing', 'integration tests', 'fakeintake mock server', and 'test assertions' to improve trigger term coverage.

List more specific actions beyond 'write tests', such as 'set up test environments, configure fakeintake assertions, validate agent telemetry data, debug test failures'.

DimensionReasoningScore

Specificity

Names the domain (E2E tests for Datadog Agent) and a specific action (write tests), and mentions specific tools (new-e2e framework, fakeintake assertions), but doesn't list multiple concrete actions beyond 'write E2E tests'.

2 / 3

Completeness

Answers 'what' (write E2E tests using new-e2e framework with fakeintake assertions) but lacks an explicit 'Use when...' clause or equivalent trigger guidance, which per the rubric caps completeness at 2.

2 / 3

Trigger Term Quality

Includes relevant technical keywords like 'E2E tests', 'Datadog Agent', 'new-e2e framework', and 'fakeintake', which are terms a user in this domain would use. However, it misses common variations like 'end-to-end', 'integration test', 'testing', or file extensions.

2 / 3

Distinctiveness Conflict Risk

Highly specific to Datadog Agent's new-e2e framework with fakeintake assertions — this is a very narrow niche that is unlikely to conflict with other skills.

3 / 3

Total

9

/

12

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation9 / 11 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

9

/

11

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.