Agent skill

Run E2E CI

by LedgerHQ in LedgerHQ/ledger-live

Trigger the on-demand E2E / Coin Tester CI workflows (Desktop E2E, Mobile E2E, Coin Tester) on a branch and post a PR comment.

MITAuto-check passedTesting & QA

Install Run E2E CI

skills CLI
$ npx skills add LedgerHQ/ledger-live --skill run-e2e-ci -a claude-code

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

GitHub CLI
$ gh skill install LedgerHQ/ledger-live run-e2e-ci --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/LedgerHQ/ledger-live.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/run-e2e-ci .claude/skills/run-e2e-ci && 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
run-e2e-ci
GitHub stars
622
Token cost
~1.9k tokens
SKILL.md length
766 words
Files
1
Skills in repo
50
Repo updated
First seen
Licence
MIT

At a glance

Trigger the on-demand E2E / Coin Tester CI workflows (Desktop E2E, Mobile E2E, Coin Tester) on a branch and post a PR comment.

  • The on-demand E2E / Coin Tester CI workflows (Desktop E2E
  • SKILL.md covers Scope it down first — filtered…, Dispatch and Post the run on the PR
  • Calls gh and node
  • Coin Tester) on a branch and post a PR comment

What it does

Run E2E CI is an agent skill from LedgerHQ/ledger-live. Trigger the on-demand E2E / Coin Tester CI workflows (Desktop E2E, Mobile E2E, Coin Tester) on a branch and post a PR comment. Use when asked to "run e2e", "trigger e2e on CI", or "run coin testers" for a PR/branch.

Its SKILL.md is about 1.9k 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 Solana and Bitcoin. The repository describes itself as: Mono-repository for Ledger Wallet apps and related packages. The licence is MIT.

When your agent uses it

  • The on-demand E2E / Coin Tester CI workflows (Desktop E2E
  • Coin Tester) on a branch and post a PR comment
  • Asked to run e2e
  • Trigger e2e on CI

Example prompts

  • “run e2e”
  • “trigger e2e on CI”
  • “run coin testers”
  • “/run-e2e-ci”

What it can do on your machine

Read from SKILL.md and the folder at commit 30d7883. 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
    • node

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

  • Network

    No URLs in SKILL.md. Its commands use gh, which can reach the network depending on how they are called.

    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

Run E2E CI loads about 1.9k tokens when it runs. Until then it costs about 57 tokens; SKILL.md has 766 words of instructions outside code blocks.

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

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 passed

The automated check found no risky patterns in SKILL.md.

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 LedgerHQ/ledger-live at commit 30d7883, republished under its MIT licence (© LedgerHQ). 766 words, ~1,902 tokens.

Download SKILL.mdSave it as .claude/skills/run-e2e-ci/SKILL.md (or your agent's skills folder).
name
run-e2e-ci
description
Trigger the on-demand E2E / Coin Tester CI workflows (Desktop E2E, Mobile E2E, Coin Tester) on a branch and post a PR comment. Use when asked to "run e2e", "trigger e2e on CI", or "run coin testers" for a PR/branch.

Run E2E / Coin Tester on CI

When: for changes that impact the e2e apps (desktop/mobile/coin logic), once the PR is getting ready for review. Desktop & Mobile E2E only run on a schedule + manual dispatch, so trigger them deliberately. Coin Tester already auto-runs on PRs for affected coins — only dispatch it to force a chain or re-run.

Scope it down first — filtered is the default, full suite is the exception

Always run the smallest subset that covers the change. The full suite is slow, expensive, and competes for shared on-chain accounts, so run it only for genuinely cross-cutting changes — and when you do, say why in the PR comment. Derive the scope from the diff:

What the diff touchesHow to scope
One coin module (libs/coin-modules/coin-solana)test_filter=@solana + Coin Tester chain=solana
A coin family (**/families/evm)test_filter=@family-evm (or @generic-coin-framework)
A specific spec / flow (swap, subAccount, newSendFlow)test_filter with the tag or spec path
Everything one team ownsteam=<slug> — ANDs with test_filter, Smoke and the device
Platform-specific (Android manifest, iOS plist)narrow Mobile tests_type (Android Only / iOS Only); skip the other surfaces
Desktop-only or Mobile-only changerun only that surface; skip the others + Coin Tester
Shared / cross-cutting (build tooling, TS upgrade, currency core)full suite — and add a one-line rationale

Filter tags: @bitcoin, @family-evm, @solana, @generic-coin-framework, @smoke, … See the test-filter guide for the grammar and the mobile (whole spec files by path/@-tag) vs desktop (test titles) matching difference.

team vs test_filter. test_filter is an OR over its patterns; the team dropdown is an AND that narrows the run to one team's specs. Combine them: team=bst + test_filter=@bitcoin runs only the bitcoin specs BST owns. Slugs: bst, buy-and-sell, coin-integration, earn, engagement, swap, wallet-xp (all is the default and changes nothing). List them with their spec counts:

bash
node e2e/tooling/filter/resolve.mjs --list-teams --check-dir e2e/desktop/tests --runner playwright
node e2e/tooling/filter/resolve.mjs --list-teams --check-dir e2e/mobile/specs  --runner detox

Selection is per spec file, so a spec two teams share runs for both. bst and coin-integration each own about half the suite — pair those with a coin tag or you have not narrowed much. Do not put @team-<slug> in test_filter: it is rejected, with a message pointing at the dropdown.

Dispatch

These are workflow_dispatch workflows — no slash-command triggers them. Dispatch with gh, which must run outside the sandbox (dangerouslyDisableSandbox: true).

gh workflow run --ref <branch> is all you need: the workflows checkout inputs.ref || github.sha, so the optional "Specify branch" (ref) field can stay blank — it falls back to the commit --ref points to. Run-names echo the branch, so use gh run list to confirm.

bash
BR=<branch>            # PR head branch
TAGS=<derived-filter>  # e.g. "@solana" — see the table above. Drop -f test_filter ONLY for a justified full suite.
CHAIN=<derived-chain>  # e.g. "solana" or "evm,solana" — derive from the diff; omit -f chain to auto-detect.

# Filtered runs (preferred). Narrow tests_type when the change is platform-specific.
gh workflow run test-ui-e2e-only-desktop.yml --ref "$BR" -f test_filter="$TAGS"
gh workflow run test-mobile-e2e-reusable.yml --ref "$BR" -f test_filter="$TAGS" -f tests_type="iOS & Android" -f speculos_device=nanoX

# Scope to one team (optional, ANDs with the filter above). Omit -f team for the default "all".
gh workflow run test-ui-e2e-only-desktop.yml --ref "$BR" -f team=swap -f test_filter="$TAGS"
gh workflow run test-mobile-e2e-reusable.yml --ref "$BR" -f team=swap -f test_filter="$TAGS" -f tests_type="iOS & Android" -f speculos_device=nanoX

gh workflow run test-coin-tester.yml --ref "$BR" -f chain="$CHAIN"   # or omit -f chain to auto-detect affected coins

gh run list --branch "$BR" --limit 6   # grab the run IDs

Mobile requires tests_type (Android Only|iOS Only|iOS & Android) and speculos_device (nanoS|nanoSP|nanoX|stax|flex|nanoGen5). Desktop defaults to Speculos nanoSP. Coin Tester auto-detects affected coins (or -f chain="evm,solana").

team is optional on both and defaults to all. Some combinations are refused outright, failing the run in the first minute rather than running the wrong thing:

  • invert_filter with team, or with smoke_tests. --grep-invert is applied to the whole pattern, so anything the resolver folds into it is inverted too: with a team you get every other team's specs, and with Smoke you get the whole suite minus the smoke tests. Invert only ever applies to test_filter, so use it alone.
  • @team-<slug> typed into test_filter. Use the dropdown; the error says so.
Show full SKILL.md (246 more words)Show less

-f team= only exists on branches that already carry the input — a branch cut before it landed will reject the flag.

Verify the filter took effect: open the run's Summary → Workflow Context. Desktop prints Filtered pattern; Mobile prints both Filtered pattern (your raw input) and Resolved filtered pattern (what the runner selects with). Both print a Team line.

A filter that matches 0 specs is wasted, and the failure mode depends on whether a team is set:

  • No team — resolve.mjs warns "filter has no matches"; on Mobile the test jobs are then skipped and the run still reports success, on Desktop it fails ("No tests executed").
  • With a team — unknown teams and teams that own nothing fail in the first minute (look for Unknown E2E team / E2E selection is empty). On Mobile, an empty team ∩ filter is also a hard error (E2E selection is empty). On Desktop, the resolver can only warn when the team ∩ filter looks empty; the run may still proceed and fail later with "No tests executed".

Fix the filter and re-dispatch.

Post the run on the PR

Fill the Scope column with the actual filter used (never a hardcoded "full suite"), and add a rationale line stating what you scoped to and why the other surfaces were skipped. Post with gh pr comment <pr> --body ... (--edit-last to update):

markdown
## 🧪 Triggered test workflows

Manually dispatched on `<branch>` (commit <short-sha>, `git rev-parse --short HEAD`), scoped to <scope>:

| Workflow | Scope | Run |
|---|---|---|
| [Desktop] E2E Only | `<@tag>` filter + `team=<slug>`, Speculos nanoSP | [run <id>](https://github.com/LedgerHQ/ledger-live/actions/runs/<id>) |
| [Mobile] E2E Only | `<@tag>` filter + `team=<slug>`, <tests_type>, nanoX | [run <id>](https://github.com/LedgerHQ/ledger-live/actions/runs/<id>) |
| [Coin] Test Coin modules | `chain=<...>` (or affected coins) | [run <id>](https://github.com/LedgerHQ/ledger-live/actions/runs/<id>) |

Scope rationale: <which surfaces changed, what you filtered to, and why the rest were skipped>.

Only write "full suite" when you deliberately ran everything, and keep the rationale line explaining why the change is cross-cutting enough to need it.

© LedgerHQ, MIT. 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/run-e2e-ci of LedgerHQ/ledger-live.

Open the folder on GitHubat commit 30d7883

Compare with similar skills

Run E2E CI 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.

Run E2E CI compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Run E2E CI this skillLedgerHQ/ledger-live622—~1.9kAutomated safety check: PassMIT
Trust Wallet SDKtrustwallet/tw-agent-skills104—~364Automated safety check: PassMIT
Payram Crypto PaymentsPayRam/payram-mcp158—~2kAutomated safety check: NotesNone
Lifisendaifun/skills130—~4.6kAutomated safety check: PassApache-2.0
Finance District MCPaeonfun/aeon767—~1.1kAutomated safety check: PassMIT
Emblem AI Agent WalletLeoYeAI/openclaw-master-skills2.2k—~6.1kAutomated safety check: NotesMIT

Similar skills

  • Trust Wallet SDK

    trustwallet/tw-agent-skills

    Trust Wallet open-source libraries — Wallet Core (HD wallets, address derivation, tx signing in Swift/Kotlin/TypeScript/Go for 140+ chains), Web3 Provider (dApp connection for…

    104 GitHub stars~364 tokensUpdated 3 mo ago
    MobileAuto-check passed
  • Payram Crypto Payments

    PayRam/payram-mcp

    Self-hosted crypto and stablecoin payment gateway. An agent skill from PayRam/payram-mcp.

    158 GitHub stars~2k tokensUpdated yesterday
    Backend & APIsAuto-check: notes
  • Lifi

    sendaifun/skills

    Integrate LI.FI for cross-chain swaps, bridging, payments, route discovery, and transfer status tracking across Solana, EVM, Bitcoin, and Sui.

    130 GitHub stars~4.6k tokensUpdated 2 mo ago
    Backend & APIsAuto-check passed
  • Multichain non-custodial agent wallet via Finance District - check balances, prices, and best DeFi yields, move funds, swap, and make x402 paid API calls across EVM, Solana, Bitcoin, and Sui.

    767 GitHub stars~1.1k tokensUpdated today
    Backend & APIsAuto-check passed
  • Emblem AI Agent Wallet

    LeoYeAI/openclaw-master-skills

    Connect to EmblemVault and manage crypto wallets via Emblem AI - Agent Hustle.

    2.2k GitHub stars~6.1k tokensUpdated 2 mo ago
    Backend & APIsAuto-check: notes
  • Web Application Testing

    anthropics/skills

    Official

    Tests local web applications with Python Playwright scripts, checking frontend behavior, capturing screenshots and reading browser console logs.

    180k GitHub starsUsed in 51 repos~966 tokens
    Testing & QAAuto-check passed

More from LedgerHQ/ledger-live

All 50 skills in this repo
  • Impacting PRs

    LedgerHQ/ledger-live

    Find which open PRs are impacted by a migration/sunset/refactor and notify their authors — blocking review when the old path is already gone from develop, heads-up comment when it is only deprecated…

    622 GitHub stars~3.3k tokensUpdated today
    Auto-check passed
  • Cloud Sync Module

    LedgerHQ/ledger-live

    Write, review or debug a cloudSyncModule.ts — a CloudSyncDataManager that syncs one slice of user data through Ledger Sync (Cloud Sync).

    622 GitHub stars~2.4k tokensUpdated today
    Auto-check passed
  • Codeownership

    LedgerHQ/ledger-live

    Maintain CODEOWNERS file and team directories. An agent skill from LedgerHQ/ledger-live.

    622 GitHub stars~687 tokensUpdated today
    Auto-check passed
  • Coin Families Contract

    LedgerHQ/ledger-live

    Coin-specific families logic must live in families/. An agent skill from LedgerHQ/ledger-live.

    622 GitHub stars~1k tokensUpdated today
    Auto-check passed
  • Data Layer Advanced

    LedgerHQ/ledger-live

    Structure a Ledger Wallet data layer where one API response serves several entities.

    622 GitHub stars~509 tokensUpdated today
    Auto-check passed
  • Debug Rn Native Crash

    LedgerHQ/ledger-live

    Investigate native React Native crashes (Fabric/Hermes/iOS) in ledger-live-mobile when JS error logs are missing or unhelpful.

    622 GitHub stars~1.2k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Run E2E CI

What does Run E2E CI do?

Trigger the on-demand E2E / Coin Tester CI workflows (Desktop E2E, Mobile E2E, Coin Tester) on a branch and post a PR comment. Run E2E CI is an agent skill from LedgerHQ/ledger-live. Trigger the on-demand E2E / Coin Tester CI workflows (Desktop E2E, Mobile E2E, Coin Tester) on a branch and post a PR comment.

When should I use Run E2E CI?

Run E2E CI fits situations like: the on-demand E2E / Coin Tester CI workflows (Desktop E2E; coin Tester) on a branch and post a PR comment; asked to run e2e; trigger e2e on CI.

How do I install Run E2E CI in Claude Code?

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

How do I install Run E2E CI in Codex?

Run `npx skills add LedgerHQ/ledger-live --skill run-e2e-ci -a codex`. Or copy the skill folder (.agents/skills/run-e2e-ci in LedgerHQ/ledger-live) into .agents/skills/run-e2e-ci in your project. Codex loads it when a task matches its description.

Can I use Run E2E CI 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 LedgerHQ/ledger-live --skill run-e2e-ci -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/run-e2e-ci, .gemini/skills/run-e2e-ci, .github/skills/run-e2e-ci and .opencode/skills/run-e2e-ci in your project.

What does Run E2E CI need to run?

Going by SKILL.md and its folder, Run E2E CI needs the command-line tools its instructions call (gh and node).

Does Run E2E CI access the network?

SKILL.md contains no URLs. Its commands use gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Run E2E CI safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Run E2E CI use?

Run E2E CI is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Run E2E CI use?

About 1.9k tokens (SKILL.md is roughly 7.6k 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 Run E2E CI?

Skills that share tags, products or a category with Run E2E CI: Trust Wallet SDK (trustwallet/tw-agent-skills, 104 stars), Payram Crypto Payments (PayRam/payram-mcp, 158 stars), Lifi (sendaifun/skills, 130 stars) and Finance District MCP (aeonfun/aeon, 767 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Run E2E CI?

LedgerHQ (a GitHub organization) maintains it in LedgerHQ/ledger-live, which has 622 GitHub stars. The repository holds 50 skills in this directory. The repository was last updated on October 8, 2026.

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