Skip to content
SkillCheatSheet Sign in

greptimedb-fuzz-ci-failure-investigation

An AI agent skill from GreptimeTeam/greptimedb, scored 71 out of 100 by code.

71/ 100B

Code score by group

  • Spec20/20
  • Description12/20
  • Procedure12/15
  • Done criteria4/15
  • Resources8/10
  • Scripts5/8
  • Safety7/7
  • Upkeep3/5

It loses the most points in Done criteria (11), the group that checks whether there is a checklist and a step that verifies the work.

What the author says it does

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.

This is the description in the skill's own SKILL.md, written by its author, not by SkillCheatSheet.

Repository
GreptimeTeam/greptimedb
Folder
.agents/skills/greptimedb-fuzz-ci-failure-investigation
License
Apache-2.0
GitHub stars
6,805
SKILL.md lines
471
Other files
0

Add greptimedb-fuzz-ci-failure-investigation to your agent

npx skills add GreptimeTeam/greptimedb --skill greptimedb-fuzz-ci-failure-investigation

The command uses the open skills CLI. A skill is instructions and scripts your agent will follow, so read it first: open the folder on GitHub at the commit that was scored.

Labelled for

More skills from GreptimeTeam/greptimedb

  1. greptimedb-development-docker-image

    Builds a development-only GreptimeDB Docker image from a local debug binary for local-cluster testing, and optionally pushes it to a development registry. Use when the user asks t…

    71B
  2. greptimedb-release-note

    Generate a GreptimeDB release changelog (minor, patch, or alpha/beta/rc pre-release) with git cliff (correct range, subtract already-released patch PRs, rebuild contributors, add…

    71B
  3. greptimedb-release

    Runbook for publishing a new GreptimeDB version (tag + GitHub release + docs release-note PR) on the upstream GreptimeTeam/greptimedb repo. Use when asked to "release" / "publish"…

    66C

All skills in GreptimeTeam/greptimedb

Scores come from a snapshot of 300 public GitHub repositories taken on 12 November 2026. Every score is the result of fixed checks run by code; no AI is involved. How scoring works.