CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

Quality

94%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

92%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

An excellent operational runbook: fully executable commands, a clearly numbered workflow with stop conditions and verification at every risky step, and proactive delegation of the changelog sub-task to a sibling skill. The only weakness is slight repetition across sections that could be tightened.

DimensionReasoningScore

Conciseness

Dense, command-first operational content with no padding about concepts Claude already knows; the explanatory asides (FETCH_HEAD staleness, CI flag semantics) are non-obvious gotchas that earn their place. Minor trimmable repetition remains — prerelease handling is explained in both §3 and §5, and remote resolution appears in both Prerequisites and Conventions.

4 / 5

Actionability

Every step ships a copy-paste command with exact flags ('gh release create ... --prerelease', 'git show FETCH_HEAD:Cargo.toml | grep ...'), and placeholders like <remote> and <verified-release-sha> are defined with resolution/verification commands. Fully executable guidance covering the common cases.

5 / 5

Workflow Clarity

Clearly sequenced §0–§6 with explicit validation checkpoints ('must equal the version being released, or stop', 'stop if it differs'), verify commands after each outward-facing step, a failure rollback path with double confirmation, and conditional handling for latest vs non-latest releases. The destructive rollback includes show-before-delete guidance, so no cap applies.

5 / 5

Progressive Disclosure

A well-organized self-contained runbook with no bundle files; all content is needed for the single release flow, and it actively delegates the heavy changelog process to the clearly-signaled sibling 'greptimedb-release-note' skill — an appropriate one-level-deep split. Section structure makes navigation easy.

5 / 5

Total

19

/

20

Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: it names the domain, lists the three concrete deliverables of the flow, and gives an explicit 'Use when' clause with quoted trigger verbs and example versions. Only minor synonym coverage is missing from the trigger terms.

DimensionReasoningScore

Specificity

Enumerates multiple concrete actions — 'tag + GitHub release + docs release-note PR' — scoped to a specific repo, giving comprehensive coverage of the release flow. It exceeds the 'several specific actions with minor gaps' anchor because no scope area is missing.

5 / 5

Completeness

Explicitly answers both: what ('Runbook for publishing a new GreptimeDB version (tag + GitHub release + docs release-note PR)') and when ('Use when asked to "release" / "publish" a GreptimeDB version') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural phrases users would say ('release', 'publish', 'a GreptimeDB version', concrete examples 'v1.1.0, v1.0.3'). A few natural variants are missing (e.g. 'ship', 'cut a release', 'new version'), so it stops short of the comprehensive-synonym anchor.

4 / 5

Distinctiveness Conflict Risk

Clear niche — publishing GreptimeDB releases on the named upstream repo — with distinct, product-specific triggers; minimal conflict risk with generic or even sibling skills.

5 / 5

Total

19

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

GreptimeTeam/greptimedb

Path

.agents/skills/greptimedb-release/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.