New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Tech E2E Tests

by agglayer in agglayer/agglayer

Architecture and agent rules for kurtosis-cdk E2E tests. An agent skill from agglayer/agglayer.

Apache-2.0Auto-check: notesTesting & QA

Install Tech E2E Tests

skills CLI
$ npx skills add agglayer/agglayer --skill tech-e2e-tests -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install agglayer/agglayer tech-e2e-tests --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/agglayer/agglayer.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/tech-e2e-tests .claude/skills/tech-e2e-tests && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
tech-e2e-tests
GitHub stars
117
Token cost
~1.1k tokens
SKILL.md length
453 words
Files
1
Skills in repo
7
Repo updated
First seen
Licence
Apache-2.0

At a glance

Architecture and agent rules for kurtosis-cdk E2E tests. An agent skill from agglayer/agglayer.

  • Tasks that involve End-to-end testing
  • SKILL.md covers How CI runs E2E, Rules and Validating E2E on a PR branch
  • Calls gh, curl and docker; reaches github.com

What it does

Tech E2E Tests is an agent skill from agglayer/agglayer. Architecture and agent rules for kurtosis-cdk E2E tests. Load when working on or debugging E2E tests, CI failures in the e2e job, or any task involving bridge testing or kurtosis.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Testing & QA, covering End-to-end testing. It works with GitHub Actions and Docker. The repository describes itself as: Rust implementation of the Agglayer. The licence is Apache-2.0.

When your agent uses it

  • Tasks that involve End-to-end testing

Example prompts

  • “/tech-e2e-tests”

Requirements

  • Docker

What it can do on your machine

Read from SKILL.md and the folder at commit 77667ba. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • gh
    • curl
    • docker
    • make
    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • github.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Tech E2E Tests loads about 1.1k tokens when it runs. Until then it costs about 49 tokens; SKILL.md has 453 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~49
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NoteMentions a .env fileSKILL.md:43
    nment is bootstrapped by sourcing `tests/.env` and

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from agglayer/agglayer at commit 77667ba, republished under its Apache-2.0 licence (© agglayer). 453 words, ~1,102 tokens.

Download SKILL.mdSave it as .claude/skills/tech-e2e-tests/SKILL.md (or your agent's skills folder).
name
tech-e2e-tests
description
Architecture and agent rules for kurtosis-cdk E2E tests. Load when working on or debugging E2E tests, CI failures in the e2e job, or any task involving bridge testing or kurtosis.

E2E test architecture

How CI runs E2E

The CI workflow .github/workflows/test.yml (job call-agglayer-node-e2e-workflow) calls an external reusable workflow at agglayer/e2e/.github/workflows/agglayer-node-e2e.yml. It passes:

  • A freshly built Docker image (via docker-image-override: agglayer_image)
  • A pinned kurtosis-cdk-ref commit
  • A pinned agglayer-e2e-ref commit
  • A kurtosis-cdk-args JSON block configuring the network (including l1_el_type, sequencer_type, and reth_image for the reth-based L1)

The workflow runs bats tests/agglayer/bridges.bats tests/agglayer/rpc-tests.bats --filter-tags agglayer in the agglayer/e2e repo. The bridges.bats file covers L1/L2 bridging; rpc-tests.bats validates reth-specific RPC methods (e.g. eth_getTransactionBySenderAndNonce).

E2E jobs only trigger on merge_group and workflow_dispatch events, not on pull_request. See Validating E2E on a PR branch for how to exercise them before merging.

Rules

  • The agglayer/e2e repo bundles its own bats-support/bats-assert libraries in core/helpers/lib/.

  • The tests use polycli ulxly bridge asset and polycli ulxly claim asset for bridge operations.

  • The test environment is bootstrapped by sourcing tests/.env and core/helpers/common.bash (_setup_vars), which auto-discovers RPC URLs, bridge addresses, and private keys from the running kurtosis enclave.

  • All pinned commits and args live in .github/workflows/test.yml; that is the single source of truth.

  • Always ask whether to rebuild agglayer:local before running. Recommend rebuilding (docker build -t agglayer:local . from the repo root) because skipping means the tests run against a stale image that does not reflect the current code.

  • polycli version must match CI. The reusable workflow agglayer/e2e/.github/workflows/agglayer-node-e2e.yml pins POLYCLI_VERSION (e.g. v0.1.90) as an env var near the top. Install the matching release binary rather than building from source, because make install produces the latest dev build which may have regressions (e.g. gas estimation changes that cause bridge tx reverts). To install a specific version:

    curl -sL "https://github.com/0xPolygon/polygon-cli/releases/download/${POLYCLI_VERSION}/polycli_${POLYCLI_VERSION}_linux_amd64.tar.gz" \
  | tar xz -C ~/go/bin/ && mv ~/go/bin/polycli_* ~/go/bin/polycli

  • polycli lives at ~/go/bin/polycli and is not on the default PATH. Export PATH="$PATH:$HOME/go/bin" before running bats or any polycli commands.

  • External repos are cached under /tmp/agglayer-e2e/. Before cloning, check whether they already exist at the correct refs (compare git -C <dir> rev-parse HEAD with the pinned SHA in .github/workflows/test.yml). Re-clone only if the ref has changed.

  • The kurtosis args file at /tmp/agglayer-e2e/kurtosis-args.json should be checked/regenerated from test.yml each run (ensure "agglayer_image": "agglayer:local" is present in args).

  • When e2e tests fail locally but pass in CI, check tool versions first. Compare local versions of polycli, kurtosis, bats, and foundry/cast against the versions CI installs (defined in agglayer-node-e2e.yml). Version drift is a common root cause of otherwise-mysterious failures (e.g. gas estimation regressions, changed CLI flags).

Show full SKILL.md (68 more words)Show less

For step-by-step local setup, see docs/knowledge-base/e2e-tests.md.

Validating E2E on a PR branch

E2E jobs only run on merge_group and workflow_dispatch events, so they are skipped during normal PR CI. To exercise them before the PR enters the merge queue, trigger a workflow_dispatch run against the PR branch:

bash
gh workflow run test.yml --repo agglayer/agglayer --ref <branch-name>

Monitor the run with:

bash
gh run list --repo agglayer/agglayer --branch <branch-name> --workflow test.yml --limit 1
gh run view <run-id> --repo agglayer/agglayer --json jobs \
  --jq '.jobs[] | "\(.name)\t\(.conclusion)"'

This run includes the full E2E suite (docker build + kurtosis + bats tests) and typically takes ~30 minutes.

© agglayer, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/tech-e2e-tests of agglayer/agglayer.

Open the folder on GitHubat commit 77667ba

Compare with similar skills

Tech E2E Tests next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Tech E2E Tests compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Tech E2E Tests this skillagglayer/agglayer117—~1.1kAutomated safety check: NotesApache-2.0
Dokan Run Test Suitegetdokan/dokan288—~4.7kAutomated safety check: NotesNone
MongoDB Source Connector E2E Harnessairbytehq/airbyte22k—~1.9kAutomated safety check: PassCustom licence
source-mssql E2E Test Harnessairbytehq/airbyte22k—~4.4kAutomated safety check: PassCustom licence
Airbyte source-mysql E2E Testsairbytehq/airbyte22k—~2.6kAutomated safety check: PassCustom licence
Go Redis Client Test Runnerredis/go-redis22k—~786Automated safety check: PassBSD-2-Clause

Similar skills

  • Dokan Run Test Suite

    getdokan/dokan

    Execute the Dokan Playwright test suite (E2E + API), locally or via GitHub Actions.

    288 GitHub stars~4.7k tokensUpdated today
    Testing & QAAuto-check: notes

  • MongoDB Source Connector E2E Harness

    airbytehq/airbyte

    Official

    Starts a throwaway MongoDB 7.0 replica set and runs the Airbyte spec, check, discover and read commands against source-mongodb-v2 images for local end-to-end testing.

    22k GitHub stars~1.9k tokensUpdated today
    Testing & QAAuto-check passed

  • source-mssql E2E Test Harness

    airbytehq/airbyte

    Official

    Stands up a throwaway local SQL Server 2022 backend, applies SQL fixtures and runs Airbyte spec, check, discover and read against source-mssql images.

    22k GitHub stars~4.4k tokensUpdated today
    Testing & QAAuto-check passed

  • Airbyte source-mysql E2E Tests

    airbytehq/airbyte

    Official

    Stands up a throwaway local MySQL 8.0 backend, applies SQL fixtures and sweeps the Airbyte spec, check, discover and read commands against a source-mysql image.

    22k GitHub stars~2.6k tokensUpdated today
    Testing & QAAuto-check passed

  • Go Redis Client Test Runner

    redis/go-redis

    Official

    Explains how to run go-redis tests: the Docker Compose stack, make targets, focusing a single Ginkgo spec, the e2e suite and the version environment variables.

    22k GitHub stars~786 tokensUpdated today
    Testing & QAAuto-check passed

  • E2E Testing

    OpenHands/OpenHands

    This skill should be used when the user asks to "add an E2E test", "run live E2E", "run mock-LLM tests", "debug Playwright CI", "test the Docker image", or changes tests/e2e, Playwright configs, E2E…

    90k GitHub stars~308 tokensUpdated today
    Testing & QAAuto-check passed

More from agglayer/agglayer

  • Verify

    agglayer/agglayer

    Mandatory before any commit or push. An agent skill from agglayer/agglayer.

    117 GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • Commit

    agglayer/agglayer

    Create a git commit following project conventions. An agent skill from agglayer/agglayer.

    117 GitHub stars~385 tokensUpdated today
    Auto-check passed

  • Docs Knowledge Base

    agglayer/agglayer

    Create or update docs/knowledge-base/ chapters in mdbook format for human-first technical documentation.

    117 GitHub stars~344 tokensUpdated today
    Auto-check passed

  • Style Prose

    agglayer/agglayer

    Text formatting conventions for markdown and prose files. An agent skill from agglayer/agglayer.

    117 GitHub stars~319 tokensUpdated today
    Auto-check passed

  • Session Retro

    agglayer/agglayer

    Review the current conversation and propose structured improvements to skills, documentation, and agent rules.

    117 GitHub stars~833 tokensUpdated today
    Auto-check passed

  • Create PR

    agglayer/agglayer

    Create a pull request following project conventions. An agent skill from agglayer/agglayer.

    117 GitHub stars~364 tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Tech E2E Tests

What does Tech E2E Tests do?

Architecture and agent rules for kurtosis-cdk E2E tests. An agent skill from agglayer/agglayer. Tech E2E Tests is an agent skill from agglayer/agglayer. Architecture and agent rules for kurtosis-cdk E2E tests.

When should I use Tech E2E Tests?

Tech E2E Tests fits situations like: tasks that involve End-to-end testing.

How do I install Tech E2E Tests in Claude Code?

Run `npx skills add agglayer/agglayer --skill tech-e2e-tests -a claude-code`. Or copy the skill folder (.agents/skills/tech-e2e-tests in agglayer/agglayer) into .claude/skills/tech-e2e-tests in your project. Claude Code loads it when a task matches its description.

How do I install Tech E2E Tests in Codex?

Run `npx skills add agglayer/agglayer --skill tech-e2e-tests -a codex`. Or copy the skill folder (.agents/skills/tech-e2e-tests in agglayer/agglayer) into .agents/skills/tech-e2e-tests in your project. Codex loads it when a task matches its description.

Can I use Tech E2E Tests in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add agglayer/agglayer --skill tech-e2e-tests -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/tech-e2e-tests, .gemini/skills/tech-e2e-tests, .github/skills/tech-e2e-tests and .opencode/skills/tech-e2e-tests in your project.

What does Tech E2E Tests need to run?

Going by SKILL.md and its folder, Tech E2E Tests needs the command-line tools its instructions call (gh, curl, docker, make and git). Our summary lists: Docker.

Does Tech E2E Tests access the network?

SKILL.md names 1 domain. In commands or code: github.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Tech E2E Tests safe to install?

Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Tech E2E Tests use?

Tech E2E Tests is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Tech E2E Tests use?

About 1.1k tokens (SKILL.md is roughly 4.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Tech E2E Tests?

Skills that share tags, products or a category with Tech E2E Tests: Dokan Run Test Suite (getdokan/dokan, 288 stars), MongoDB Source Connector E2E Harness (airbytehq/airbyte, 22k stars), source-mssql E2E Test Harness (airbytehq/airbyte, 22k stars) and Airbyte source-mysql E2E Tests (airbytehq/airbyte, 22k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Tech E2E Tests?

agglayer (a GitHub organization) maintains it in agglayer/agglayer, which has 117 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on October 7, 2026.

Source: agglayer/agglayer on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.