greptimedb-fuzz-ci-failure-investigation SKILL.md skillA
greptimedb-fuzz-ci-failure-investigation from greptimeteam/greptimedb is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add greptimeteam/greptimedb/greptimedb-fuzz-ci-failure-investigation@git:20260803.a6107fbPins git:20260803.a6107fb in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- greptimeteam/greptimedb
- Path
.agents/skills/greptimedb-fuzz-ci-failure-investigation/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260803.a6107fb, committed Aug 3, 2026
- First version recorded
- Jul 9, 2026
- Size
- 17,746 bytes
- Repository stars
- 6,792
- License
- Apache-2.0
Investigate a failed GreptimeDB fuzz CI target link by downloading GitHub Actions job logs plus fuzz artifacts such as kind logs, monitor dumps, and CSV dumps, then correlate the failure with local GreptimeDB source code. Use when the user provides a failed fuzz CI target/job URL or asks to diagnose GreptimeDB fuzz CI failures.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# GreptimeDB Fuzz CI Failure Investigation Investigate failed fuzz-test jobs for **`GreptimeTeam/greptimedb`** from a local checkout. The purpose is to download the failed job's CI output and fuzz artifacts, then explain the likely cause by correlating the evidence with GreptimeDB source. Always pass `--repo GreptimeTeam/greptimedb` to `gh`; local remotes may point to forks. Keep the workflow read-only: do not rerun jobs, cancel workflows, push, comment on PRs, or delete artifacts unless the user explicitly asks. ## Scope Use this skill for fuzz CI only. In `.github/workflows/integration.yml`, fuzz failures are the CI jobs that use `.github/actions/fuzz-test`: - `fuzztest` — standalone fuzz targets. - `unstable-fuzztest` — unstable standalone fuzz target. - `distributed-fuzztest` — distributed cluster fuzz targets. - `distributed-fuzztest-with-chaos` — distributed fuzz targets with Chaos Mesh. Each matrix job runs a semantic group of targets on one prepared environment. The group defaults to fail-fast: after the first target failure it captures that target's diagnostics and marks the remaining targets as skipped. The workflow …
Read the whole file at its exact version.
How to install
mdr add greptimeteam/greptimedb/greptimedb-fuzz-ci-failure-investigation@sha256:e509013c6db31980The line at the top of this page pins the label git:20260803.a6107fb, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_lo4xrlwhdblyrvgf)
5 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Jul 9, 2026 and Aug 3, 2026, about one every 25 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260803.a6107fb latest | 2026-08-03 | a6107fb | 17,746 B | A | view · diff |
| git:20260709.ffd6488 | 2026-07-09 | ffd6488 | 17,265 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (17746 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
greptimeteam/greptimedb · 6,792 stars · license Apache-2.0 · pushed 2026-11-07 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_lo4xrlwhdblyrvgf GET https://markdownregistry.com/api/v1/resolve?ref=greptimeteam/greptimedb/greptimedb-fuzz-ci-failure-investigation GET https://markdownregistry.com/api/v1/blob/e509013c6db319809da67c73fe16fd89f1ad8f9b75f305bfa7f052f55b06386e
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.