SkillsAdd

lambdatest/agent-skills

hyperexecute-skill

Operates HyperExecute end-to-end for TestMu AI/LambdaTest cloud test 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.

First seen Feb 26, 2026

Installation

$ npx skills add lambdatest/agent-skills --skill hyperexecute-skill
View on skills.sh ↗ GitHub repository ↗

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

agent-browser Shared topics
vercel-labs/agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, includ…

810.4K installs
azure-aigateway Shared topics
microsoft/azure-skills

Configure Azure API Management as an AI Gateway for AI models, MCP tools, and agents. WHEN: sem…

566.3K installs
azure-compute Shared topics
microsoft/azure-skills

Azure VM/VMSS router. WHEN: create / provision / deploy / spin-up VM, recommend VM size, compar…

510K installs
supabase-postgres-best-practices Shared topics
supabase/agent-skills

Postgres best practices maintained by Supabase, for Postgres running anywhere. Load this skill …

391.6K installs
prisma-cli Shared topics
prisma/skills

Prisma ORM CLI commands reference covering init, generate, migrate, db, dev, complete, studio, …

267K installs
supabase Shared topics
supabase/agent-skills

Use when doing ANY task involving Supabase. Triggers: Supabase products (Database, Auth, Edge F…

263K installs

Also in this package

Other skills from lambdatest/agent-skills · top by installs.

npx skills add lambdatest/agent-skills
playwright-skill 452 appium-skill 378 pytest-skill 338 vitest-skill 8 selenium-skill 267 jest-skill 238 cicd-pipeline-skill 229 cucumber-skill 227 phpunit-skill 222 junit-5-skill 221

Browse all from lambdatest/agent-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Also listed on

Alternate registries and mirrors of this skill.

Repository health

Stars 366
License LICENSE
Default branch main
Open issues 3
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

Version2.0
LicenseMIT
More metadata
author
TestMu AI
version
2.0

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 3,729 B
  • docs SUMMARY.md 444 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 204 installs

SKILL.md

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 "$LTUSERNAME" --key "$LTACCESS_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 LTUSERNAME and LTACCESS_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)