Skip to main content
skill CX Codex

hyperexecute-skill — Claude Code skill: testing and install

This skill prepares and runs HyperExecute test jobs, checks YAML locally, connects CI, and helps investigate failed cloud runs.

MIT 250 installs ★ 393 updated 2026-10-13

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add LambdaTest/agent-skills --skill hyperexecute-skill -a claude-code
Open on GitHub

What hyperexecute-skill does

hyperexecute-skill guides a project through HyperExecute test execution. It inspects the repository, creates or fixes hyperexecute.yaml, performs local checks, runs the CLI, and helps retrieve logs, reports, and artifacts. The workflow covers Playwright, Cypress, Selenium, Pytest, and WebdriverIO projects.

The package includes scripts/doctor.js, scripts/validate-config.js, scripts/build-command.js, and scripts/summarize-artifacts.js. They check CLI readiness, lint common configuration errors, print commands that use environment variables, and summarize downloaded results. CI setup can include a validation stage, secrets, and CI=true for quieter output.

Set LT_USERNAME and LT_ACCESS_KEY through the environment or CI secrets before a cloud run. Without those credentials, HyperExecute cannot start the job; the skill also requests confirmation before a real run unless autonomous mode was approved.

What it helps with

  • inspect a test project before moving it to HyperExecute
  • create and validate hyperexecute.yaml
  • run tests through the HyperExecute CLI
  • triage logs, reports, and artifacts after a failure
  • connect HyperExecute execution to CI

Example prompts for the agent

  • Inspect this project and prepare hyperexecute.yaml for a HyperExecute test run.
  • Check the configuration with node scripts/doctor.js --config hyperexecute.yaml and node scripts/validate-config.js hyperexecute.yaml.
  • Investigate the latest HyperExecute failure and prepare commands to download its logs and artifacts.

How to install hyperexecute-skill

1Skills CLI (Vercel)

npx skills add LambdaTest/agent-skills --skill hyperexecute-skill -a claude-code

2Manually: put the files in place

~/.claude/skills/hyperexecute-skill/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/hyperexecute-skill/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about hyperexecute-skill

How do I install hyperexecute-skill in Claude Code?

Run npx skills add LambdaTest/agent-skills --skill hyperexecute-skill -a claude-code, then check ~/.claude/skills/hyperexecute-skill/SKILL.md.

What does hyperexecute-skill do?

It inspects a project, prepares hyperexecute.yaml, runs local and official CLI checks, manages HyperExecute jobs, and helps investigate their results.

What is required for a cloud test run?

Provide LT_USERNAME and LT_ACCESS_KEY through environment variables or CI secrets. A real job also needs confirmation unless autonomous mode is enabled.

Source text

SKILL.md · MIT
---
name: hyperexecute-skill
description: >
  Operates HyperExecute end-to-end for TestMu AI/LambdaTest cloud test
  execution: analyze projects, create YAML, validate locally, run CLI jobs,
  debug failures, and wire CI. Use when the user mentions HyperExecute,
  hyperexecute.yaml, HyperExecute CLI, autosplit, matrix execution,
  LambdaTest grid, cloud test runs, CI test orchestration, or migrating
  Playwright/Cypress/Selenium/Pytest/WebdriverIO tests to HyperExecute.
languages:
  - YAML
  - JavaScript
category: cloud-testing
license: MIT
metadata:
  author: TestMu AI
  version: "2.0"
---

# HyperExecute Operator

## Quick Start

1. Locate the HyperExecute CLI. If missing, ask before downloading it unless the user explicitly approved an autonomous HyperExecute session.
2. Run `hyperexecute analyze` when the CLI is available; use local inspection only as fallback.
3. Create or repair `hyperexecute.yaml` from the analyze output, project test commands, and templates in `reference/`.
4. Run `node scripts/doctor.js --config hyperexecute.yaml` and `node scripts/validate-config.js hyperexecute.yaml`.
5. Validate with the official CLI: `./hyperexecute --user "$LT_USERNAME" --key "$LT_ACCESS_KEY" --config hyperexecute.yaml --validate`.
6. Ask before a real cloud job unless the user has explicitly opted into an autonomous HyperExecute session.
7. For failures, download logs/artifacts/reports and use `reference/troubleshooting.md`.

## Operating Rules

- Treat the official HyperExecute CLI as the source of truth for analyze, validation, execution, logs, reports, and artifacts.
- Use `LT_USERNAME` and `LT_ACCESS_KEY` from local environment variables or CI secrets; never hardcode credentials in YAML or docs.
- Use `--job-secret-file` only for extra job-scoped secrets, preferably outside the repo or ignored by `.gitignore`/`.hyperexecuteignore`.
- Prefer template-driven YAML over generator scripts because test commands, paths, and payload boundaries are project-specific.
- Run safe local checks automatically; run real HyperExecute cloud jobs only after confirmation unless the user opted into autonomous mode.
- In autonomous mode, validate first, run, inspect output, download logs/artifacts when useful, and retry only for actionable config/environment fixes.

## Workflow

- First run: analyze project, author YAML, run helper checks, run CLI validate, then request confirmation for the cloud job.
- Debug: reproduce the failing CLI command, add `--verbose` when useful, download logs/artifacts/reports, fix one cause at a time.
- CI: use CI secrets, add a validation stage before execution, set `CI=true` for quieter logs, and keep downloaded artifacts available for failed jobs.
- Performance: tune `autosplit`, `concurrency`, cache keys, retries, smart ordering, and matrix/hybrid scope after one successful run.

## Helper Scripts

- `scripts/doctor.js`: checks CLI readiness, credentials, config presence, and optional official validation.
- `scripts/validate-config.js`: lightweight config linting for common mistakes before official CLI validation.
- `scripts/build-command.js`: prints safe validate/run/debug/download commands using environment variable references.
- `scripts/summarize-artifacts.js`: summarizes downloaded logs, reports, and artifacts for triage.

## References

- CLI usage and flags: [reference/cli.md](reference/cli.md)
- YAML patterns: [reference/yaml-patterns.md](reference/yaml-patterns.md)
- Framework recipes: [reference/frameworks.md](reference/frameworks.md)
- CI/CD integration: [reference/ci-cd.md](reference/ci-cd.md)
- Security rules: [reference/security.md](reference/security.md)
- Troubleshooting: [reference/troubleshooting.md](reference/troubleshooting.md)

© TestMu AI · MIT · LambdaTest/agent-skills

Similar skills

All skills for Testing and QA →

From the same set47

The whole set →
webdriverio-skill Generates WebdriverIO end-to-end tests in JavaScript or TypeScript for local runs and TestMu AI cloud. CX Codex +1 265installs cypress-skill Generates production-grade E2E and component tests in JavaScript or TypeScript. Runs tests locally or on TestMu AI cloud, understands Cypress commands, and writes tests with proper selectors and network interception. CX Codex +1 264installs robot-framework-skill robot-framework-skill turns a described scenario into a .robot test in keyword-driven syntax, with SeleniumLibrary for browser flows and RequestsLibrary for API checks. CX Codex +1 253installs detox-skill Generates Detox E2E tests for React Native projects in JavaScript and TypeScript. Sets up tests for local emulators and TestMu AI cloud runs. CX Codex +1 252installs xcuitest-skill Generates XCUITest UI tests for iOS and iPadOS apps. Detects whether to use local Xcode simulators or TestMu AI cloud devices, then builds test code accordingly. CX Codex +1 248installs puppeteer-skill Generates Puppeteer scripts for browser automation, scraping, and PDF output. Activates when you mention Puppeteer, headless Chrome, page.goto, or PDF generation. CX Codex +1 247installs testng-skill Generates Java TestNG tests with groups, data providers, parallel execution, suite XML, and listeners. Use it when building or organising TestNG coverage. CX Codex +1 243installs codeception-skill Generates PHP Codeception acceptance, functional, and unit tests using BDD actor workflows. Useful for web interface validation and browser automation. CX Codex +1 243installs

Project sponsors

Companies that keep this analytics open