Bundled upstream support
Supporting files are included at skill-relative paths. See UPSTREAM-NOTICE.md for their pinned sources, licenses, hashes, and import changes.
Restored helper safety
scripts/doctor.js --validate-cli passes LT_USERNAME and LT_ACCESS_KEY to the HyperExecute CLI as process arguments, where local process-inspection tools may expose them. Run only on a trusted host and authorized account, and avoid concurrent untrusted users. Treat it as a remote account operation; verify the current CLI's validation behavior and any project data it submits before invoking it.
HyperExecute Operator
When to Use
Use this skill when you need 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,...
Quick Start
- Locate the HyperExecute CLI. If missing, ask before downloading it unless the user explicitly approved an autonomous HyperExecute session.
- Run
hyperexecute analyze when the CLI is available; use local inspection only as fallback.
- Create or repair
hyperexecute.yaml from the analyze output, project test commands, and templates in reference/.
- Run
node scripts/doctor.js --config hyperexecute.yaml and node scripts/validate-config.js hyperexecute.yaml.
- Validate with the official CLI:
./hyperexecute --user "$LT_USERNAME" --key "$LT_ACCESS_KEY" --config hyperexecute.yaml --validate.
- Ask before a real cloud job unless the user has explicitly opted into an autonomous HyperExecute session.
- 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
Example
User request:
Use @hyperexecute-skill for this task: 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.
Limitations
- Use this skill only when the task clearly matches its upstream source and local project context.
- Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.
- Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.
1---2name: hyperexecute-skill3description: "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."4risk: critical5source: https://github.com/LambdaTest/agent-skills/tree/main/hyperexecute-skill6source_repo: LambdaTest/agent-skills7source_type: community8date_added: 2026-07-019license: MIT10license_source: https://github.com/LambdaTest/agent-skills/blob/main/LICENSE11metadata:12 source: https://skillmd.com/skills/iradoweck/hyperexecute-skill13---1415## Bundled upstream support1617Supporting files are included at skill-relative paths. See [UPSTREAM-NOTICE.md](UPSTREAM-NOTICE.md) for their pinned sources, licenses, hashes, and import changes.1819## Restored helper safety2021`scripts/doctor.js --validate-cli` passes `LT_USERNAME` and `LT_ACCESS_KEY` to the HyperExecute CLI as process arguments, where local process-inspection tools may expose them. Run only on a trusted host and authorized account, and avoid concurrent untrusted users. Treat it as a remote account operation; verify the current CLI's validation behavior and any project data it submits before invoking it.2223# HyperExecute Operator24## When to Use2526Use this skill when you need 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,...272829## Quick Start30311. Locate the HyperExecute CLI. If missing, ask before downloading it unless the user explicitly approved an autonomous HyperExecute session.322. Run `hyperexecute analyze` when the CLI is available; use local inspection only as fallback.333. Create or repair `hyperexecute.yaml` from the analyze output, project test commands, and templates in `reference/`.344. Run `node scripts/doctor.js --config hyperexecute.yaml` and `node scripts/validate-config.js hyperexecute.yaml`.355. Validate with the official CLI: `./hyperexecute --user "$LT_USERNAME" --key "$LT_ACCESS_KEY" --config hyperexecute.yaml --validate`.366. Ask before a real cloud job unless the user has explicitly opted into an autonomous HyperExecute session.377. For failures, download logs/artifacts/reports and use `reference/troubleshooting.md`.3839## Operating Rules4041- Treat the official HyperExecute CLI as the source of truth for analyze, validation, execution, logs, reports, and artifacts.42- Use `LT_USERNAME` and `LT_ACCESS_KEY` from local environment variables or CI secrets; never hardcode credentials in YAML or docs.43- Use `--job-secret-file` only for extra job-scoped secrets, preferably outside the repo or ignored by `.gitignore`/`.hyperexecuteignore`.44- Prefer template-driven YAML over generator scripts because test commands, paths, and payload boundaries are project-specific.45- Run safe local checks automatically; run real HyperExecute cloud jobs only after confirmation unless the user opted into autonomous mode.46- In autonomous mode, validate first, run, inspect output, download logs/artifacts when useful, and retry only for actionable config/environment fixes.4748## Workflow4950- First run: analyze project, author YAML, run helper checks, run CLI validate, then request confirmation for the cloud job.51- Debug: reproduce the failing CLI command, add `--verbose` when useful, download logs/artifacts/reports, fix one cause at a time.52- CI: use CI secrets, add a validation stage before execution, set `CI=true` for quieter logs, and keep downloaded artifacts available for failed jobs.53- Performance: tune `autosplit`, `concurrency`, cache keys, retries, smart ordering, and matrix/hybrid scope after one successful run.5455## Helper Scripts5657- `scripts/doctor.js`: checks CLI readiness, credentials, config presence, and optional official validation.58- `scripts/validate-config.js`: lightweight config linting for common mistakes before official CLI validation.59- `scripts/build-command.js`: prints safe validate/run/debug/download commands using environment variable references.60- `scripts/summarize-artifacts.js`: summarizes downloaded logs, reports, and artifacts for triage.6162## References6364- CLI usage and flags: [reference/cli.md](https://github.com/LambdaTest/agent-skills/tree/main/hyperexecute-skill/reference/cli.md)65- YAML patterns: [reference/yaml-patterns.md](https://github.com/LambdaTest/agent-skills/tree/main/hyperexecute-skill/reference/yaml-patterns.md)66- Framework recipes: [reference/frameworks.md](https://github.com/LambdaTest/agent-skills/tree/main/hyperexecute-skill/reference/frameworks.md)67- CI/CD integration: [reference/ci-cd.md](https://github.com/LambdaTest/agent-skills/tree/main/hyperexecute-skill/reference/ci-cd.md)68- Security rules: [reference/security.md](https://github.com/LambdaTest/agent-skills/tree/main/hyperexecute-skill/reference/security.md)69- Troubleshooting: [reference/troubleshooting.md](https://github.com/LambdaTest/agent-skills/tree/main/hyperexecute-skill/reference/troubleshooting.md)7071## Example7273**User request:**7475> Use @hyperexecute-skill for this task: 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.7677## Limitations7879- Use this skill only when the task clearly matches its upstream source and local project context.80- Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.81- Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.