hyperpod-issue-report

Generate comprehensive issue reports from HyperPod clusters (EKS and Slurm) by collecting diagnostic logs and configurations for troubleshooting and AWS Support cases. Use when users need to collect diagnostics from HyperPod cluster nodes, generate issue reports for AWS Support, investigate node failures or performance problems, document cluster state, or create diagnostic snapshots. Triggers on requests involving issue reports, diagnostic collection, support case preparation, or cluster troubleshooting that requires gathering logs and system information from multiple nodes.

What does this entry provide?

hyperpod-issue-report is an agent skill entry in ChatHome Skills, sourced from GitHub Skill Search and scored 58/100. # HyperPod Issue Report Collect diagnostic logs from HyperPod cluster nodes via SSM, store results in S3. Supports both EKS and Slurm clusters with auto-detecti. As an agent skill, it packages a reusable instruction set that AI coding agents such as Codex and Claude Code can load to perform this task without hand-written glue code. ChatHome Skills discovered this entry through its daily ingest of official registries and GitHub discovery queries, and re-verifies repository facts, freshness signals, and install metadata on every run. The quality score weighs official-registry presence, a working install command, license clarity, GitHub star trajectory, and repository freshness — the full formula is on the Sources page. The install command above is ready to copy. Review the last-pushed date and repository status before adding hyperpod-issue-report to a production agent workflow; the snapshot facts below are point-in-time values from the most recent ingest.

Snapshot facts

Source: GitHub Skill Search
Quality: 58/100
Install method: codex
Repo: haozhx23/HyperPod-InstantStart
Repo updated: Oct 23, 2026

Install command

codex skill install haozhx23/HyperPod-InstantStart

Install method: codex

Review the upstream source before running this command.

GitHub project

Quality

Repo stars

Repo updated

Unknown

How is this score calculated?

Weighted across six dimensions, scored 0-100.
Provenance (25): listed in an official or curated registry.
Installability (25): a runnable install command beats a declared transport, which beats a source checkout.
Maintenance (20): recency of the last push; archived entries score zero here.
Adoption (20): repository stars on a log curve.

Security signals

Scan coverage: Install metadata and the indexed document body.

Automated signals from install metadata and a bounded skill body — not a full code security audit and not a recursive source or dependency review.

Discovery note

# HyperPod Issue Report Collect diagnostic logs from HyperPod cluster nodes via SSM, store results in S3. Supports both EKS and Slurm clusters with auto-detection. Uses the bundled

Report an issue with this listing