CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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 human-curated highlights and upgrade notes), output to a file, and prepare the docs-repo blog PR. Use when asked to write/generate a GreptimeDB release note or changelog.

Quality

93%

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

85%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 exceptionally actionable, project-specific operational runbook: every step is executable, edge cases and fallbacks are anticipated, and validation/verification gates are explicit. The two weaknesses are the monolithic single-file layout — a complex multi-path skill like this would benefit from splitting per-release-type recipes and the docs-PR workflow into reference files — and minor rationale verbosity.

Suggestions

Split the per-release-type recipes (§3 new minor / patch / pre-release) and the §8 docs-repo blog workflow into one-level-deep reference files (e.g. references/release-types.md, references/docs-pr.md), keeping SKILL.md as a concise overview that links to them.

Add a short decision table at the top (release type → base / tip / subtract already-shipped PRs?) so the reader can jump straight to the right recipe instead of scanning all of §3.

Trim rationale passages (the flaky-network note, §6 curation explanations) to single-sentence gotchas so every token earns its place.

DimensionReasoningScore

Conciseness

The body is dense with non-obvious project knowledge ('patch tags ... are NOT ancestors of main', 'check-release-note-sync requires the post ... to equal the GitHub release body byte for byte') and explains no general concepts. A few rationale passages — the flaky-network note and parts of the §6 curation prose — run longer than the instruction alone needs, matching the level-4 'minor instances of over-explanation that could be trimmed' anchor rather than level 5.

4 / 5

Actionability

Fully executable, copy-paste-ready commands throughout: exact `git cliff` ranges with GITHUB_TOKEN invocation, `git merge-base` splits, a complete `git rev-list` loop for collecting PR numbers, `gh api ... --jq` fetches, and the worktree/pinned-pnpm build sequence — with hand-written fallback (b) covering the flaky-API case and all four release-type variants addressed.

5 / 5

Workflow Clarity

Clear §1–§8 sequence with explicit validation checkpoints and error-recovery loops: 'pin the intended release commit and record its SHA', §5 'Cross-check the result against git log <base>..<tip>: no subtracted PR remains', 'If the build fails, fix it or stop; don't mark the PR ready for review', and 're-run until it completes' with fallback (b). The batch subtraction step is explicitly verified, so the missing-validation cap does not apply.

5 / 5

Progressive Disclosure

A single 316-line file with no bundle files or one-level-deep references: the per-release-type recipes (new minor / patch / pre-release / first alpha) and the entire §8 docs-PR workflow are inline content that belongs in separate reference files. Section headers give it good internal structure, but 'content that should be separate is inline' matches the level-3 anchor; the under-50-line simple-skill exception does not apply.

3 / 5

Total

17

/

20

Passed

Description

100%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: concrete and comprehensive on capabilities, explicit about when to trigger, uses natural synonyms ('release note'/'changelog'), and occupies a distinct niche with virtually no conflict risk. Third-person voice is consistent and there is no fluff despite the density.

DimensionReasoningScore

Specificity

Enumerates multiple concrete, comprehensive actions: 'correct range, subtract already-released patch PRs, rebuild contributors, add human-curated highlights and upgrade notes', 'output to a file', and 'prepare the docs-repo blog PR' — matching the level-5 anchor's breadth of specific capabilities.

5 / 5

Completeness

Explicitly answers both: the 'what' is a detailed action list, and the 'when' is the concrete trigger clause 'Use when asked to write/generate a GreptimeDB release note or changelog' — exactly the level-5 anchor pattern.

5 / 5

Trigger Term Quality

Covers the natural terms a user would say in this domain — 'release note' and 'changelog' as synonyms, 'write/generate' as the natural verbs, plus 'GreptimeDB', 'minor, patch, or alpha/beta/rc pre-release'. Both dominant user phrasings are present, so it clears the level-4 'a few natural terms missing' anchor.

5 / 5

Distinctiveness Conflict Risk

Pinned to a clear niche ('GreptimeDB release changelog' with git cliff and the docs-repo blog PR); no other plausible skill shares these triggers, so conflict risk is minimal.

5 / 5

Total

20

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 suspicious

Warning

Total

15

/

16

Passed

Repository

GreptimeTeam/greptimedb

Path

.agents/skills/greptimedb-release-note/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.