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 to package, build, tag, publish, or cross-build a non-release GreptimeDB or GreptimeDB Enterprise image for debugging.

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

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.

The body is a well-structured, highly actionable procedural skill with strong validation checkpoints and appropriate externalization of executable logic into bundle files. Its main weakness is moderate verbosity from repeated release-artifact disclaimers and a Safety Rules section that overlaps inline rules.

Suggestions

State the 'development/local-cluster test image, not a release artifact' disclaimer once in the Goal section and once at final confirmation, removing the other repetitions to save tokens.

Either fold the Safety Rules section into the inline rules where they already appear, or replace the inline restatements with a single pointer to the Safety Rules section, to avoid duplicate coverage of the same prohibitions.

Consider consolidating the Inputs and Batch configuration fields tables, which overlap on platform/build-mode/registry/tag rows, into a single table to reduce redundancy.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and free of basic-concept padding, but the 'development/local-cluster test image, not a release artifact' disclaimer recurs ~4 times and the Safety Rules section restates rules already given inline, which could be tightened without losing clarity.	3 / 5
Actionability	Fully executable, copy-paste-ready commands with real flags throughout — collect_context.py, build_binary.sh, prepare_context.sh, build_image.sh, update_image_env.py, next_image_tag.py — with explicit amd64/arm64/Enterprise variants covering the common cases.	5 / 5
Workflow Clarity	A clearly numbered sequence (inspect tooling → build executable → build/push image → verify) with explicit validation checkpoints (file-architecture check, registry-tag check, image inspect, --help run) and stop-and-ask feedback gates for a batch/push workflow.	5 / 5
Progressive Disclosure	SKILL.md serves as the orchestration overview while executable logic is externalized one level deep into real, well-signaled bundle files (scripts/.py and .sh, assets/Dockerfile), each invoked via explicit path-bearing code blocks; no nested references.	5 / 5
	Total	18 / 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.

The description is concise, third-person, and cleanly states both the capability and explicit trigger conditions. It covers the action space comprehensively and is well-scoped to a distinct niche. It is a strong, low-conflict description.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Builds a development-only GreptimeDB Docker image from a local debug binary', 'optionally pushes it to a development registry', and the verbs 'package, build, tag, publish, or cross-build' — giving comprehensive coverage of the skill's capabilities.	5 / 5
Completeness	Explicitly answers both 'what' (builds a dev-only Docker image from a local debug binary and optionally pushes to a dev registry) and 'when' via a concrete 'Use when the user asks to...' clause with multiple trigger phrases.	5 / 5
Trigger Term Quality	Comprehensive natural-verb coverage a user would actually say ('package, build, tag, publish, or cross-build') plus intent terms ('for debugging', 'non-release', 'GreptimeDB Enterprise'), with synonyms across the action space.	5 / 5
Distinctiveness Conflict Risk	A clearly bounded niche — development-only, local-debug-binary-sourced GreptimeDB/GreptimeDB Enterprise images — with 'non-release' and 'for debugging' qualifiers that minimize overlap with release-image skills.	5 / 5
	Total	20 / 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
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: GreptimeTeam/greptimedb
Path: .agents/skills/greptimedb-development-docker-image/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.