GreptimeDB is an observability database that stores metrics, logs, and traces in a columnar engine over object storage, using a shared table model for the data. It is for operating telemetry backends, correlating related signals with SQL, and querying metrics with PromQL.
Borrowing it
Nothing to install: this file belongs to GreptimeTeam/greptimedb. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/GreptimeTeam/greptimedb/main/.agents/skills/greptimedb-release-note/SKILL.mdgit clone --depth 1 https://github.com/GreptimeTeam/greptimedbWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/greptimeteam/greptimedb/greptimedb-release-note)<a href="https://agentmods.dev/skills/greptimeteam/greptimedb/greptimedb-release-note"><img src="https://agentmods.dev/badge/skills/greptimeteam/greptimedb/greptimedb-release-note/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/greptimeteam/greptimedb/greptimedb-release-note"><img src="https://agentmods.dev/badge/skills/greptimeteam/greptimedb/greptimedb-release-note.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Tool Misuse · line 181 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00087 | $0.05608 |
| Opus 5.5 | $0.00035 | $0.02243 |
| Sonnet 5.5 | $0.00017 | $0.01122 |
| Haiku 4.5 | $0.00009 | $0.00561 |
Grade A, and why
greptimedb-release-note scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 21d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 348 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GreptimeDB Release Note / Changelog
Generate the changelog for a GreptimeDB release. Tooling: git cliff (config:
cliff.toml in the greptimedb repo) and gh. Run inside the greptimedb checkout.
Prerequisites: git cliff, gh (check gh auth status), and Python (the
subtract-PRs / rebuild-contributors step in §3–§4 is scripted). This skill writes
<remote> for the git remote pointing at GreptimeTeam/greptimedb (often upstream,
sometimes origin); resolve it with
git remote -v | grep -i 'GreptimeTeam/greptimedb' | awk '{print $1}' | head -1.
1. GitHub token (never print it)
git cliff enriches commits with PR titles/authors via the GitHub API; for hundreds of
commits you need a token or you hit rate limits. Pass it inline and never read or echo the
token:
GITHUB_TOKEN=$(gh auth token) git cliff ...
Alternatively the user sources an env file that exports GITHUB_TOKEN (don't read it). Without
a token it still runs, but may be rate-limited / incomplete.
2. Determine the previous version (skip nightlies)
From gh release list --repo GreptimeTeam/greptimedb, ignore *-nightly-* and build-suffixed
tags (e.g. v1.3.0-alpha.1-3c0e2a8d5-20260928-1790639248).
- Patch
vX.Y.Z(Z>0): previous =vX.Y.(Z-1). - New minor
vX.Y.0: previous = the latestvX.(Y-1).*(forv1.0.0, the biggest0.x). - Pre-release
vX.Y.Z-{alpha,beta,rc}.N: previous = the latest pre-release tag of the samevX.Y.Z(e.g.v1.3.0-beta.1forv1.3.0-beta.2). If there is none (the first alpha), see "First pre-release" in §3: the previous minor's.0may not be published yet, and since v1.2 a.0tag sits onrelease/vX.Y, not onmain. Double-check with the user.
3. Pick the range and generate
Key topology fact: patch tags (v1.0.1, v1.0.2) live on release/vX.Y and are NOT
ancestors of main (they are cherry-picks with different SHAs). Up to v1.1 the .0 tag was
the point where release/vX.Y left main; from v1.2 the branch is cut before the .0, and
pre-releases and the .0 itself are tagged on the branch with backports. Verify with
git merge-base --is-ancestor <tag> <remote>/main.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 21d ago Changed · +163 lines · +17 tokens per session f2eeb565117d
- 2mo ago First seen · 185 lines · 70 tokens per session scan A f91d50f00b23
greptimedb-release-note is a skill published in the GitHub repository GreptimeTeam/greptimedb (6,789 stars, last pushed yesterday), licensed Apache-2.0. It adds 87 tokens to every session and 5,608 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
greptimedb-release-note compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| greptimedb-release-noteGreptimeTeam/greptimedb | Skill | 6.8k | yesterday | Apache-2.0 | A | 87 | Codex |
| opentelemetry-net-instrumentationAaronontheweb/dotnet-skills | Skill | 1.3k | 9d ago | MIT | A | 56 | Claude Code |
| systematic-debuggingmonoscope-tech/monoscope | Skill | 2.0k | yesterday | AGPL-3.0 | A | 21 | Claude Code, Codex |
| test-driven-developmentmonoscope-tech/monoscope | Skill | 2.0k | yesterday | AGPL-3.0 | A | 17 | Claude Code, Codex |
| verification-before-completionmonoscope-tech/monoscope | Skill | 2.0k | yesterday | AGPL-3.0 | A | 43 | Claude Code, Codex |
| monitoring-expertpersonamanagmentlayer/pcl | Skill | 44 | 11d ago | Apache-2.0 | B | 70 | Claude Code |
| opentelemetrybobmatnyc/claude-mpm-skills | Skill | 78 | 3mo ago | MIT | A | 29 | Claude Code |