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. 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.
- License 许可
- MIT
- 最近更新
- 2026-09-11
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- license
- MIT
- metadata
- { "author": "TestMu AI", "version": "2.0" }
- 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.
02 资源文件 10
- 参考文档reference/ci-cd.md1.9 KB
- 参考文档reference/cli.md2.8 KB
- 参考文档reference/frameworks.md2.7 KB
- 参考文档reference/security.md1.3 KB
- 参考文档reference/troubleshooting.md1.9 KB
- 参考文档reference/yaml-patterns.md1.6 KB
- 脚本scripts/build-command.js2.0 KB
- 脚本scripts/doctor.js2.8 KB
- 脚本scripts/summarize-artifacts.js1.7 KB
- 脚本scripts/validate-config.js2.6 KB
03 SKILL.md 正文
HyperExecute Operator
Quick Start
- Locate the HyperExecute CLI. If missing, ask before downloading it unless the user explicitly approved an autonomous HyperExecute session.
- Run
hyperexecute analyzewhen the CLI is available; use local inspection only as fallback. - Create or repair
hyperexecute.yamlfrom the analyze output, project test commands, and templates inreference/. - Run
node scripts/doctor.js --config hyperexecute.yamlandnode 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_USERNAMEandLT_ACCESS_KEYfrom local environment variables or CI secrets; never hardcode credentials in YAML or docs. - Use
--job-secret-fileonly 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
--verbosewhen useful, download logs/artifacts/reports, fix one cause at a time. - CI: use CI secrets, add a validation stage before execution, set
CI=truefor 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
- YAML patterns: reference/yaml-patterns.md
- Framework recipes: reference/frameworks.md
- CI/CD integration: reference/ci-cd.md
- Security rules: reference/security.md
- Troubleshooting: reference/troubleshooting.md
04 同仓库更多 Skills
runpodctl
Runpod CLI for managing GPU/CPU workloads from the terminal — pods, serverless endpoints, templates, network volumes, Hub deploys, models, SSH, and file transfer (send/receive). Use for terminal/CI/scripting, Hub browse/deploy, SSH setup, `doctor`, or when the Runpod MCP tools are not connected. For structured tool calls in an MCP-enabled session, prefer runpod-mcp.
runpod
Start here for any Runpod task — running GPU/CPU pods, deploying serverless endpoints, templates, network volumes, building images, or understanding how Runpod works. Routes to the right skill (runpod-mcp, runpodctl, flash, companion-clis, runpod-usage, runpod-templates, runpod-migrate) and indexes two dozen live-verified end-to-end examples (golden paths) — use it when the lane is unclear, and for any multi-step or provisioning task even when it is not.
runpod-usage
How Runpod works and how to work it — pods vs serverless, GPU/VRAM selection, storage, building a container, networking, plus the agentic pod development loop (provision → ssh-exec → set up → poll readiness) and on-pod install hygiene (uv/apt). Use to answer "how does X work", "which GPU", "how do I build a container", or "how do I stand up a workload on a pod". Guidance, not a tool — execute with runpodctl, runpod-mcp, or flash.
runpod-templates
Runpod's official prebuilt pod templates (ComfyUI, PyTorch, and others): what each image ships, which ports and paths it uses, how to pick one, how to pin a version, and what is missing on first boot. Use when a task says "run <X> on a pod" and an official template already covers it, instead of building an image — and when a user needs help with or wants to fix something about a Runpod template they are already running (won't boot, can't reach the UI, missing models, wrong CUDA line, broken ComfyUI workflow metadata on imported workflows): start here and route onward. Deploy with runpodctl or runpod-mcp; end-to-end walkthroughs live in the runpod router's golden paths.
runpod-migrate
Migrate a codebase from the Runpod GraphQL API or REST v1 to REST v2 — inventory which parts use which API version, rewrite the call sites, flag breaking changes, and verify. Use when someone asks to move to v2, asks what v2 would change, or asks which Runpod API their code is on. For managing infrastructure rather than migrating code, use runpod-mcp or runpodctl.
runpod-mcp
Manage Runpod infrastructure — pods, serverless endpoints, jobs, templates, network volumes, container-registry auth, GPU/CPU catalog, and billing — via the Runpod MCP server's structured tool calls. Use when the Runpod MCP tools (create-pod, list-endpoints, …) are connected in this session, or to connect them (hosted OAuth or local npx). Prefer this over runpodctl for plain infra CRUD when MCP is available; use runpodctl for the terminal, file transfer, or SSH setup.