SkillCurated by metahubEval warnings

hyperexecute-skill

Name: hyperexecute-skill
Author: LambdaTest

pinned to #54824d6updated 2 weeks ago

7/11Verified publisherCurated by MetaHubActively maintainedLicensedDocumentedStructuredClean repo

Ask your AI client: “install skills/hyperexecute-skill”.

Requires the metahub MCP server installed in your client. Set up MCP.

mh install skills/hyperexecute-skill

metahub onboarded this repo on the author's behalf.

If you own github.com/LambdaTest/agent-skills on GitHub, claim the listing to take over publishing. Your claim preserves the existing eval history and badges; only the curator label is replaced with verified-publisher on your next publish.

Claim this repo

Stars

325

Last commit

2 weeks ago

54824d6

Latest release

published

2 weeks ago

Evaluation report

Warnings

Automated checks the publisher passed at publish time — structure, docs, safety, and whether the artifact behaves as claimed.54824d6· 2 weeks ago

Documentation

Description qualitywarn
8 words · 52 chars — skills use the description as their trigger; aim higher — manifest description is empty; graded the GitHub repo description instead
Aim for 15+ words and include trigger phrases like “use this skill when …”.
README is present and substantial
6,607 chars · 7 sections · 6 code blocks
Tags / topics declaredwarn
No manifest tags and no GitHub repo topics
Add tags to the manifest (or GitHub topics on the repo) so the registry's search and category filters surface this artifact.
README has usage / example sections
found: Getting Started
Homepage / docs URL declared
https://agentskillsforall.com/

Release history

releasecurrent54824d6warn2 weeks ago

View on GitHub

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 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

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

Reviews

No reviews yet. Be the first.

SkillCurated

Verification Before Completion

Evidence before assertions, always

#f2cbfbeActiveMIT+5

obra

253,04922,600Shell

verificationqualityworkflow

SkillCurated

Writing Plans

Turn specs into phased implementation plans

#f2cbfbeActiveMIT+5

obra

253,04922,600Shell

planningarchitectureworkflow

SkillCurated

Test-Driven Development

Red → green → refactor discipline for any feature or bugfix

mh install skills/hyperexecute-skill

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.

hyperexecute-skill

Evaluation report

Documentation

Release history

Contents

HyperExecute Operator

Quick Start

Operating Rules

Workflow

Helper Scripts

References

Reviews

Related

Verification Before Completion

Writing Plans

Test-Driven Development

hyperexecute-skill

Evaluation report

Documentation

Release history

Contents

HyperExecute Operator

Quick Start

Operating Rules

Workflow

Helper Scripts

References

Reviews

Related

Verification Before Completion

Writing Plans

Test-Driven Development