mcpbeat Sign in

Write E2e Agent Skill

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

584 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
3695
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/DataDog/datadog-agent --skill write-e2e

The instruction itself

3 sections, as written by the author

Write end-to-end tests for the Datadog Agent using the test/e2e-framework/ framework.

Parse $ARGUMENTS to determine what to test.

Where to find what you need

| What | Where | Read first? |

|------|-------|:---:|

| E2E test writing guidelines and rules | test/new-e2e/codereview_guideline.md | ✅ |

| Framework API (environments, provisioners, agentparams) | test/e2e-framework/AGENTS.md | ✅ |

| Fakeintake API (payload types, client methods, extending) | test/fakeintake/AGENTS.md | ✅ |

| Setup, prerequisites, running tests | docs/public/how-to/test/e2e.md | |

| Real tests to use as patterns | test/new-e2e/tests/ (see lookup table in e2e-framework AGENTS.md) | |

| Check system overview | root AGENTS.md § "Check System" | |

| Test placement / team ownership | CODEOWNERS | |

| CI job definitions | .gitlab/test/e2e/e2e.yml, .gitlab/windows/test/e2e/windows.yml | |

| CI trigger rules | .gitlab-ci.yml (search for .on_*_or_e2e_changes) | |

| Examples | test/new-e2e/examples/ | |

Read every file marked "Read first?" before writing any test. Browse examples and a few real tests

that match your use case. Make sure to follow _all_ the guidelines specified.

Checklist

  • Read the feature's implementation to understand what payloads it sends
  • Check if E2E tests already exist under test/new-e2e/tests/
  • Place tests in the right <area> directory (check CODEOWNERS);

one file per platform target (e.g., disk_nix_test.go, disk_win_test.go)

  • Verify compilation: cd test/new-e2e && go vet ./tests/<area>/...
  • Run the test locally before pushing — compilation alone is not enough:

dda inv new-e2e-tests.run --targets=./tests/<area>/...

See test/e2e-framework/AGENTS.md § "Validating E2E tests" if it fails

  • Check CI wiring: grep -n 'TARGETS:.*<area>' .gitlab/test/e2e/e2e.yml

Output

Show the user: files created, how to compile-check, how to run locally

(dda inv new-e2e-tests.run --targets=./tests/<area>/...), and whether

CI changes are needed.

Other skills for the same job

different authors, same section of the catalogue
Webapp Testing
by anthropics
vendor ×12

Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.

6k tokens scripts
Finishing A Development Branch
by ZhanlinCui
×7

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup

1k tokens
Test Driven Development
by w95
×7

Use when implementing any feature or bugfix, before writing implementation code

2k tokens
Systematic Debugging
by ratacat
×7

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

10k tokens scripts
Verification Before Completion
by ZhanlinCui
×6

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always

1k tokens
Backtest Expert
by BaggaT236
×3

Expert guidance for systematic backtesting of trading strategies. Use when developing, testing, stress-testing, or validating quantitative trading strategies. Covers "beating ideas to death" methodology, parameter robustness testing, slippage modeling, bias prevention, and interpreting backtest results. Applicable when user asks about backtesting, strategy validation, robustness testing, avoiding overfitting, or systematic trading development.

15k tokens scripts
Adaptyv
by christophacham
×3

Cloud laboratory platform for automated protein testing and validation. Use when designing proteins and needing experimental validation including binding assays, expression testing, thermostability measurements, enzyme activity assays, or protein sequence optimization. Also use for submitting experiments via API, tracking experiment status, downloading results, optimizing protein sequences for better expression using computational tools (NetSolP, SoluProt, SolubleMPNN, ESM), or managing protein design workflows with wet-lab validation.

16k tokens
Aeon
by christophacham
×3

This skill should be used for time series machine learning tasks including classification, regression, clustering, forecasting, anomaly detection, segmentation, and similarity search. Use when working with temporal data, sequential patterns, or time-indexed observations requiring specialized algorithms beyond standard ML approaches. Particularly suited for univariate and multivariate time series analysis with scikit-learn compatible APIs.

19k tokens

How to use it

Copy the folder

Take datadog/write-e2e from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.