write-e2e
Write E2E tests for the Datadog Agent using the new-e2e framework with fakeintake assertions
68
62%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.claude/skills/write-e2e/SKILL.mdQuality
Discovery
40%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 targets a very specific niche (Datadog Agent E2E testing with fakeintake), 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 an explicit 'Use when...' clause, e.g., 'Use when the user needs to write, modify, 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', 'fake intake', and 'integration tests' 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'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (E2E tests for Datadog Agent) and a key 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 | Describes what it does (write E2E tests using the new-e2e framework with fakeintake assertions) but has no explicit 'Use when...' clause or equivalent trigger guidance, which per the rubric caps completeness at 2, and the 'what' is also fairly thin, placing this at 1. | 1 / 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', 'e2e test', or 'fake intake'. | 2 / 3 |
Distinctiveness Conflict Risk | Highly specific to the 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 | 8 / 12 Passed |
Implementation
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 skill that excels at conciseness and progressive disclosure through its lookup table format. The workflow checklist is clear with appropriate validation checkpoints. The main weakness is that actionability relies heavily on delegated files — the skill body itself doesn't include a concrete test code example or skeleton, which would make it more immediately useful.
Suggestions
Add a minimal but complete Go test skeleton showing the typical structure (suite setup, environment provisioning, fakeintake assertion) so Claude has an executable starting pattern without needing to read referenced files first.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every section is lean and purposeful. No unnecessary explanations of what E2E testing is or how Go works. The lookup table format is extremely token-efficient for conveying where to find resources. | 3 / 3 |
Actionability | Provides concrete commands for compilation (`go vet`), running tests (`dda inv new-e2e-tests.run`), and CI checking (`grep`), but lacks executable code examples of an actual test skeleton. The skill delegates most actionable content to referenced files (AGENTS.md), so the body itself is more of a navigation guide than a concrete how-to. | 2 / 3 |
Workflow Clarity | The checklist provides a clear, well-sequenced workflow from understanding the feature through writing, compiling, running locally, and verifying CI wiring. It includes explicit validation checkpoints (step 4: compile check, step 5: run locally before pushing) with a feedback loop reference for failures. | 3 / 3 |
Progressive Disclosure | The lookup table cleanly organizes references to external files with clear descriptions of what each contains. All references are one level deep and well-signaled. The SKILL.md serves as an effective overview/router to detailed materials. | 3 / 3 |
Total | 11 / 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.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
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
- Commit
0f36ad4
- 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.