greptimedb-release-note

Generate a GreptimeDB release changelog with git cliff (correct range, subtract already-released patch PRs, rebuild contributors, add human-curated highlights), output to a file, and prepare the docs-repo blog PR. Use when asked to write/generate a GreptimeDB release note or changelog.

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

81%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.

A dense, well-sequenced runbook with executable commands, explicit validation, and useful feedback loops for a fragile release-process task. Its main gap is that the Python subtract/rebuild steps are described rather than given as code, slightly limiting actionability.

Suggestions

Provide the actual Python script (or a concrete code block) for subtracting already-released patch PRs and rebuilding contributor sections, rather than describing it as 'a small Python script is the reliable way'.

Tighten the repeated 'ask the user' / flaky-network prose into a single concise note to reduce token cost without losing the checkpoint.

Consider extracting the long §8 docs-repo blog PR workflow into a separate reference file so the main SKILL.md stays a lean overview.

Dimension	Reasoning	Score
Conciseness	Largely lean and assumes Claude's knowledge of git/gh; project-specific topology facts (minor vs patch tag ancestry) earn their place, though a few prose passages (e.g. the flaky-network note, repeated 'ask the user' reminders) could be trimmed.	4 / 5
Actionability	Overwhelmingly executable with concrete git-cliff/gh/git commands throughout, but the core subtract-PRs step and §4 contributor rebuild are described in prose ('a small Python script is the reliable way') rather than provided as copy-paste code.	4 / 5
Workflow Clarity	Eight clearly sequenced sections with explicit validation (§5 Verify), feedback loops (flaky-network re-run-until-complete, iterate highlights with the user), and checkpoint prompts ('Double-check with the user', 'ask the user which they prefer').	5 / 5
Progressive Disclosure	Well-organized into numbered sections with no bundle files needed for a single workflow; at ~180 lines it exceeds the simple-skill exception, so it lands at good structure with minor inlining rather than a 5.	4 / 5
	Total	17 / 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 highly specific, third-person description that covers both the full action pipeline and an explicit trigger clause, well-scoped to GreptimeDB release notes. Only minor trigger-synonym coverage is missing.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'generate a GreptimeDB release changelog with git cliff', 'subtract already-released patch PRs', 'rebuild contributors', 'add human-curated highlights', 'output to a file', 'prepare the docs-repo blog PR' — giving comprehensive coverage.	5 / 5
Completeness	Clearly states what it does (the full changelog + docs PR pipeline) and gives an explicit 'Use when asked to write/generate a GreptimeDB release note or changelog' trigger.	5 / 5
Trigger Term Quality	Natural phrases like 'write/generate a GreptimeDB release note or changelog' map well to what a user would say, though a few common variants (e.g. 'release notes' plural, 'changelog generation') are absent.	4 / 5
Distinctiveness Conflict Risk	Tightly scoped to GreptimeDB release notes/changelogs with git cliff, a clear niche with distinct triggers and minimal overlap with other skills.	5 / 5
	Total	19 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
relative_links	Relative link issues: 1 suspicious	Warning

	Total	15 / 16 Passed

Repository: GreptimeTeam/greptimedb
Path: .agents/skills/greptimedb-release-note/SKILL.md
Commit: 7fd0a7b

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.