Index of every page on this site: llms.txt
All skills
openshift avatar

/e2e-analyze

@0f43b29 official
by openshiftopenshift/hypershift555 stars
592
Run it yourself

Analyze test errors

Use this Skill: https://skilld.dev/gh/openshift/hypershift/e2e-analyze

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈8 tokens for metadata: the name and description. ≈292 when used: this file.

How this Skill uses context

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈33 characters, or 0.4%.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

General instructions

  • Validate that "$3" is an existing directory; fail if it is not. Do NOT create the directory.
  • Extract {BUILD_NUMBER} from "$1" by matching a 10–20 digit sequence; fail if none is found.
  • Use the extracted number as {BUILD_NUMBER}.
  • Use curl to download the file build-log.txt under "$1". Only allow HTTPS URLs (reject HTTP).
  • When fetching, use: curl -fsSL --max-time 20 --retry 3 --retry-connrefused --proto '=https' --max-filesize 100M "${1}/build-log.txt".
  • The build-log.txt file contains e2e failures, store the artifacts related to failure "$2" under directory specified by "$3" to determine a possible root cause for the failure.
  • Use the "gcloud storage" command to fetch given artifacts under "$3" and make sure to use {BUILD_NUMBER} in URLs.
  • Provide evidence for the failure.
  • Try to find additional evidence. For example, in logs and events.
  • Do not delete downloaded artifacts during the cleanup phase.

Output format

  • The output should be formatted as:
    Error: {Error message here}
    Summary: {Failure analysis here}
    Evidence: {Evidence here}
    Additional evidence: {Additional evidence here}

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 warning25d3 checks · Risk SAFE
  • Gen Agent Trust Hub25d

    The skill analyzes CI/CD build logs by downloading them from a provided URL and fetching artifacts via cloud storage tools. It is generally safe but processes external data which introduces a minor risk of indirect prompt injection.

  • Socket25d

    No alerts

  • Snyk25d

    Risk: MEDIUM · 1 issue

Signed by skilld at 0f43b29. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 3 months ago

README badge

README badge for openshift/hypershift/e2e-analyze