mcpField
H
hyperexecute-skill

hyperexecute-skill

github.com/lambdatestTesting & quality384239 installsUpdated 2w ago
Repository

About hyperexecute-skill

An operator skill for configuring and running HyperExecute test jobs, aimed at developers and CI maintainers. It guides project analysis, YAML creation, validation, cloud-job approval, and artifact-based troubleshooting while keeping credentials out of configuration files.

Key features

  1. 01HyperExecute CLI analysis and validation
  2. 02hyperexecute.yaml authoring guidance
  3. 03Configuration lint and readiness checks
  4. 04Safe command generation
  5. 05Log, report, and artifact triage
  6. 06CI and performance tuning guidance

Use cases

  1. 01Create or repair a HyperExecute configuration
  2. 02Validate settings before a cloud job
  3. 03Diagnose failed test runs from artifacts
  4. 04Add validation and execution steps to CI

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/lambdatest/agent-skills --skill hyperexecute-skill

After installing, type/hyperexecute-skillin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

reference/
ci-cd.md
cli.md
frameworks.md
security.md
troubleshooting.md
yaml-patterns.md
scripts/
build-command.js
doctor.js
summarize-artifacts.js
validate-config.js

Details

From the project README

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

Comments

Markdown supported