How do I install the Greptimedb Trigger skill?

Run npx skillmds@latest add tomevault-io/greptimedb-trigger in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Greptimedb Trigger safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Greptimedb Trigger?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Greptimedb Trigger free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Greptimedb Trigger?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Greptimedb Trigger by tomevault-io — Agent Skill

Name: Greptimedb Trigger
Author: tomevault-io

Greptimedb Trigger

Guide for creating GreptimeDB triggers, by which we can trigger external webhook like Alertmanager. This feature can be used as alternative to Prometheus alerting rule. Use when this capability is needed.

tomevault-io 7e4f5c2 2 files · 3.1 KB Updated Sep 17, 2026

File contents

GreptimeDB Trigger Guide

Create GreptimeDB trigger definition as an alternative to Prometheus alerting rule. GreptimeDB trigger maps most concepts from Prometheus alert rules in its own DDL.

The workflow

To create Greptime trigger, we should follow these phases:

Phase 1. Understanding GreptimeDB Trigger

First, we should read greptimedb trigger definitions and how it works from GreptimeDB's documentation.

There are pages available, use WebFetch to load and understand them:

High level information of Trigger https://docs.greptime.com/enterprise/trigger/
The trigger syntax reference https://docs.greptime.com/reference/sql/trigger-syntax/

Phase 2. Create an initial trigger

Create the trigger based on user provided information.

Note that CREATE TRIGGER can also use Greptime TQL to define the rule. The TQL is Greptime's embedded PromQL in SQL, so using TQL makes migration from Prometheus alert rules easier.

In most case, the query in trigger should use aggregation and GROUP BY for time-series and time window. This is like using SQL to simulate PromQL behaviour. If possible, we can use PromQL as TQL to simplify the query.

It can be either existing Prometheus alerting rule yaml, or detailed requirements described by user.

Return the CREATE TRIGGER SQL statement, with some dummy data for the webhook part if user didn't provide webhook information.

Phase 3. Configure webhook for trigger

If the user already has a Prometheus Alertmanager setup, use their Alertmanager information for webhook.

Reference

Prometheus Alertmanager

Alertmanager is typically configured in prometheus.yml like this

...
# Alerting specifies settings related to the Alertmanager
alerting:
  alertmanagers:
    - static_configs:
      - targets:
        # Alertmanager's default port is 9093
        - localhost:9093

We can use the target for our webhook destination.

Step-by-step guide

https://greptime.com/blogs/2025-12-23-trigger-quick-start

Greptime TQL

https://docs.greptime.com/reference/sql/tql/

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: greptimedb-triggerdescription: Guide for creating GreptimeDB triggers, by which we can trigger external webhook like Alertmanager. This feature can be used as alternative to Prometheus alerting rule. Use when this capability is needed.---# GreptimeDB Trigger GuideCreate GreptimeDB trigger definition as an alternative to Prometheus alertingrule. GreptimeDB trigger maps most concepts from Prometheus alert rules in itsown DDL.## The workflowTo create Greptime trigger, we should follow these phases:### Phase 1. Understanding GreptimeDB TriggerFirst, we should read greptimedb trigger definitions and how it works fromGreptimeDB's documentation.There are pages available, use WebFetch to load and understand them:1. High level information of Trigger https://docs.greptime.com/enterprise/trigger/2. The trigger syntax reference https://docs.greptime.com/reference/sql/trigger-syntax/### Phase 2. Create an initial triggerCreate the trigger based on user provided information.Note that `CREATE TRIGGER` can also use Greptime TQL to define the rule. The TQLis Greptime's embedded PromQL in SQL, so using TQL makes migration fromPrometheus alert rules easier.In most case, the query in trigger should use aggregation and `GROUP BY` fortime-series and time window. This is like using SQL to simulate PromQLbehaviour. If possible, we can use PromQL as TQL to simplify the query.It can be either existing Prometheus alerting rule yaml, or detailed requirementsdescribed by user.Return the `CREATE TRIGGER` SQL statement, with some dummy data for the webhookpart if user didn't provide webhook information.### Phase 3. Configure webhook for triggerIf the user already has a Prometheus Alertmanager setup, use their Alertmanagerinformation for webhook.## Reference### Prometheus AlertmanagerAlertmanager is typically configured in `prometheus.yml` like this```yaml...# Alerting specifies settings related to the Alertmanageralerting: alertmanagers: - static_configs: - targets: # Alertmanager's default port is 9093 - localhost:9093```We can use the target for our webhook destination.### Step-by-step guidehttps://greptime.com/blogs/2025-12-23-trigger-quick-start### Greptime TQLhttps://docs.greptime.com/reference/sql/tql/---> Converted and distributed by [TomeVault](https://tomevault.io/claim/greptimeteam) — claim your Tome and manage your conversions.

Frequently asked questions