agentleFS
Sign inStart free
openshiftopenshift/hypershift/.claude/skills/e2e-analyze/SKILL.md

e2e-analyze

Skill551 starsChanged 6 months agoApache-2.0View on GitHub

Analyze test errors

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 2 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use the extracted number as {BUILD_NUMBER}.

    line 10
  2. Distinctive:

    Use curl to download the file build-log.txt under "$1".

    line 11
  3. Very specific:

    When fetching, use: curl -fsSL --max-time 20 --retry 3 --retry-connrefused --proto '=https' --max-filesize 100M "${1}/build-log.txt".

    line 12
  4. Very specific:

    Use the "gcloud storage" command to fetch given artifacts under "$3" and make sure to use {BUILD_NUMBER} in URLs.

    line 14
  5. Distinctive:

    Do not delete downloaded artifacts during the cleanup phase.

    line 17

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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}

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free