GreptimeDB Fuzz CI Failure Investigation
GreptimeTeam/greptimedb
Diagnoses a failed GreptimeDB fuzz CI job by pulling its GitHub Actions logs and fuzz artifacts, then matching the evidence to the local source code.
Analysing GitHub Actions CI failures from a run URL. An agent skill from golemcloud/golem.
Install Analysing CI Failures
$ npx skills add golemcloud/golem --skill analysing-ci-failures -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install golemcloud/golem analysing-ci-failures --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/golemcloud/golem.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/analysing-ci-failures .claude/skills/analysing-ci-failures && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "analysing-ci-failures" agent skill from https://github.com/golemcloud/golem/tree/main/.agents/skills/analysing-ci-failures into .claude/skills/analysing-ci-failures/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analysing-ci-failures", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/golemcloud/golem/tree/main/.agents/skills/analysing-ci-failuresType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add golemcloud/golem --skill analysing-ci-failures -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install golemcloud/golem analysing-ci-failures --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/golemcloud/golem.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/analysing-ci-failures .agents/skills/analysing-ci-failures && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "analysing-ci-failures" agent skill from https://github.com/golemcloud/golem/tree/main/.agents/skills/analysing-ci-failures into .agents/skills/analysing-ci-failures/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analysing-ci-failures", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add golemcloud/golem --skill analysing-ci-failures -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install golemcloud/golem analysing-ci-failures --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/golemcloud/golem.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/analysing-ci-failures .cursor/skills/analysing-ci-failures && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "analysing-ci-failures" agent skill from https://github.com/golemcloud/golem/tree/main/.agents/skills/analysing-ci-failures into .cursor/skills/analysing-ci-failures/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analysing-ci-failures", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/golemcloud/golem.git --path .agents/skills/analysing-ci-failures--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add golemcloud/golem --skill analysing-ci-failures -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install golemcloud/golem analysing-ci-failures --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/golemcloud/golem.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/analysing-ci-failures .gemini/skills/analysing-ci-failures && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "analysing-ci-failures" agent skill from https://github.com/golemcloud/golem/tree/main/.agents/skills/analysing-ci-failures into .gemini/skills/analysing-ci-failures/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analysing-ci-failures", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install golemcloud/golem analysing-ci-failuresInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add golemcloud/golem --skill analysing-ci-failures -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/golemcloud/golem.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/analysing-ci-failures .github/skills/analysing-ci-failures && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "analysing-ci-failures" agent skill from https://github.com/golemcloud/golem/tree/main/.agents/skills/analysing-ci-failures into .github/skills/analysing-ci-failures/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analysing-ci-failures", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add golemcloud/golem --skill analysing-ci-failures -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install golemcloud/golem analysing-ci-failures --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/golemcloud/golem.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/analysing-ci-failures .opencode/skills/analysing-ci-failures && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "analysing-ci-failures" agent skill from https://github.com/golemcloud/golem/tree/main/.agents/skills/analysing-ci-failures into .opencode/skills/analysing-ci-failures/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analysing-ci-failures", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
analysing-ci-failures- GitHub stars
- 1.5k
- Token cost
- ~862 tokens
- SKILL.md length
- 272 words
- Files
- 1
- Skills in repo
- 289
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Analysing GitHub Actions CI failures from a run URL. An agent skill from golemcloud/golem.
- Works in 5 steps: Parse the URL → Download the Job Log → Download CTRF Reports (if available) → …
- The user pastes a GitHub CI run
- SKILL.md covers Step 1: Parse the URL, Step 2: Download the Job Log, Step 3: Download CTRF Reports… and Step 4: Analyse the Log, plus 1 more section
- Calls gh, cargo and rg
What it does
Analysing CI Failures is an agent skill from golemcloud/golem. Analysing GitHub Actions CI failures from a run URL. Use when the user pastes a GitHub CI run or job URL and wants to understand why it failed and how to reproduce locally.
Its SKILL.md is about 860 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Testing & QA, covering Failing and flaky tests and CI/CD. It works with GitHub Actions and GitHub. The repository describes itself as: Golem Cloud is the agent-native platform for building AI agents and distributed applications that never lose state, never duplicate work, and never require you to build…
When your agent uses it
- The user pastes a GitHub CI run
- Job URL and wants to understand why it failed and how to reproduce locally
Example prompts
- “/analysing-ci-failures”
Requirements
- Docker
Workflow steps
5 steps, taken from the step headings in SKILL.md.
- Parse the URL
- Download the Job Log
- Download CTRF Reports (if available)
- Analyse the Log
- Provide a Summary
What it can do on your machine
Read from SKILL.md and the folder at commit c6a3029. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
ghcargorg
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use gh, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Analysing CI Failures loads about 862 tokens when it runs. Until then it costs about 49 tokens; SKILL.md has 272 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 272 words (~862 tokens).
“Diagnose GitHub Actions CI failures by downloading logs and CTRF test reports, then providing a summary of what failed and how to reproduce it locally.”
- name
- analysing-ci-failures
Files
Just SKILL.md in .agents/skills/analysing-ci-failures of golemcloud/golem.
Open the folder on GitHubat commit c6a3029
Compare with similar skills
Analysing CI Failures next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Analysing CI Failures this skillgolemcloud/golem | 1.5k | — | ~862 | Automated safety check: Pass | Custom licence | |
| GreptimeDB Fuzz CI Failure InvestigationGreptimeTeam/greptimedb | 6.7k | — | ~4.4k | Automated safety check: Pass | Apache-2.0 | |
| Babysit PRZenUml/web-sequence | 150 | — | ~871 | Automated safety check: Pass | MIT | |
| Debugging CI FailuresPostHog/posthog | 40k | — | ~5.7k | Automated safety check: Pass | Custom licence | |
| CI Watchdoglatitude-dev/latitude-llm | 4.7k | — | ~1.6k | Automated safety check: Pass | MIT | |
| Megatron-LM CI Failure TriageNVIDIA/Megatron-LM | 18k | — | ~1.6k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Babysit PR
ZenUml/web-sequence
Monitor and diagnose GitHub Actions checks on ZenUML web-sequence PRs, fixing code-caused CI failures when appropriate.
- Official
Debugging CI Failures
PostHog/posthog
Debugs failing GitHub Actions CI runs for PostHog PRs, commits, and branches, and answers broad CI-health questions ("is CI red?", "is master green today?", "what's broken right now?").
CI Watchdog
latitude-dev/latitude-llm
Continuously monitor GitHub PR CI checks and automatically fix failures until all checks pass.
- Official
Megatron-LM CI Failure Triage
NVIDIA/Megatron-LM
Investigates a failing GitHub Actions run or job for Megatron-LM, finds the root cause plus the PR and test author involved, and files a structured bug issue.
Parallel CI Triage
spencerpauly/awesome-cursor-skills
When GitHub Actions fails, fetch failing job logs and assign each failing job to a separate subagent that fixes its slice of the problem in parallel.
More from golemcloud/golem
All 289 skills in this repoMoonbit C Binding
golemcloud/golem
Guide for writing MoonBit bindings to C libraries using native FFI.
Adding Dependencies
golemcloud/golem
Adding or updating crate dependencies in the Golem workspace.
Creating New Builtin Plugins
golemcloud/golem
Adds a built-in WASM plugin that is externally released and provisioned by the registry service.
DB Migration Scripts
golemcloud/golem
Writing database migration SQL scripts. An agent skill from golemcloud/golem.
Debugging Hanging Tests
golemcloud/golem
Diagnosing and fixing hanging worker executor or integration tests.
Golem Add Agent Effect
golemcloud/golem
Adding an Effect-based agent to a Golem component. An agent skill from golemcloud/golem.
Related
Works with
Categories
Questions about Analysing CI Failures
What does Analysing CI Failures do?
Analysing GitHub Actions CI failures from a run URL. An agent skill from golemcloud/golem. Analysing CI Failures is an agent skill from golemcloud/golem. Analysing GitHub Actions CI failures from a run URL.
When should I use Analysing CI Failures?
Analysing CI Failures fits situations like: the user pastes a GitHub CI run; job URL and wants to understand why it failed and how to reproduce locally.
How do I install Analysing CI Failures in Claude Code?
Run `npx skills add golemcloud/golem --skill analysing-ci-failures -a claude-code`. Or copy the skill folder (.agents/skills/analysing-ci-failures in golemcloud/golem) into .claude/skills/analysing-ci-failures in your project. Claude Code loads it when a task matches its description.
How do I install Analysing CI Failures in Codex?
Run `npx skills add golemcloud/golem --skill analysing-ci-failures -a codex`. Or copy the skill folder (.agents/skills/analysing-ci-failures in golemcloud/golem) into .agents/skills/analysing-ci-failures in your project. Codex loads it when a task matches its description.
Can I use Analysing CI Failures in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add golemcloud/golem --skill analysing-ci-failures -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/analysing-ci-failures, .gemini/skills/analysing-ci-failures, .github/skills/analysing-ci-failures and .opencode/skills/analysing-ci-failures in your project.
What does Analysing CI Failures need to run?
Going by SKILL.md and its folder, Analysing CI Failures needs the command-line tools its instructions call (gh, cargo and rg). Our summary lists: Docker.
Does Analysing CI Failures access the network?
SKILL.md contains no URLs. Its commands use gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Analysing CI Failures safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Analysing CI Failures use?
Analysing CI Failures has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Analysing CI Failures use?
About 862 tokens (SKILL.md is roughly 3.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Analysing CI Failures?
Skills that share tags, products or a category with Analysing CI Failures: GreptimeDB Fuzz CI Failure Investigation (GreptimeTeam/greptimedb, 6.7k stars), Babysit PR (ZenUml/web-sequence, 150 stars), Debugging CI Failures (PostHog/posthog, 40k stars) and CI Watchdog (latitude-dev/latitude-llm, 4.7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Analysing CI Failures?
golemcloud (a GitHub organization) maintains it in golemcloud/golem, which has 1,507 GitHub stars. The repository holds 289 skills in this directory. The repository was last updated on October 8, 2026.
Source: golemcloud/golem on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.