Skip to content
SkillCheatSheet Sign in

greptimedb-release

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

66/ 100C

Code score by group

  • Spec20/20
  • Description11/20
  • Procedure6/15
  • Done criteria4/15
  • Resources8/10
  • Scripts5/8
  • Safety7/7
  • Upkeep5/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

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" a GreptimeDB version (e.g. v1.1.0, v1.0.3).

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-release
License
Apache-2.0
GitHub stars
6,805
SKILL.md lines
120
Other files
1

Add greptimedb-release to your agent

npx skills add GreptimeTeam/greptimedb --skill greptimedb-release

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.

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-fuzz-ci-failure-investigation

    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…

    71B
  3. 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

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.