Agent skill · software engineering · sickn33
hyperexecute-skill
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.
Why this skill is useful
Adds multiple executable scripts for HyperExecute configuration and validation that enhance cloud test execution capabilities.
What it needs
Requires hyperexecute installed locally. Requires lambda-test account access. About 3k tokens when loaded. Last updated 2026-08-07. 44,571 stars on the source repository.
What this skill does
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 LTUSERNAME and LTACCESSKEY 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 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 "$LTUSERNAME" --key "$LTACCESSKEY" --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 LTUSERNAME and LTACCESSKEY from local environment variables or CI secrets; never hardcode credentials in YAML or docs. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills sickn33/hyperexecute-skill