Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add SigNoz/agent-skills --skill signoz-explaining-alertsgit clone --depth 1 https://github.com/SigNoz/agent-skillsWrote 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/signoz/agent-skills/signoz-explaining-alerts)<a href="https://agentmods.dev/skills/signoz/agent-skills/signoz-explaining-alerts"><img src="https://agentmods.dev/badge/skills/signoz/agent-skills/signoz-explaining-alerts/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/signoz/agent-skills/signoz-explaining-alerts"><img src="https://agentmods.dev/badge/skills/signoz/agent-skills/signoz-explaining-alerts.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00136 | $0.04880 |
| Opus 5 | $0.00068 | $0.02440 |
| Sonnet 5 | $0.00027 | $0.00976 |
| Haiku 4.5 | $0.00014 | $0.00488 |
Grade A, and why
signoz-explaining-alerts 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 12d 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 — 408 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Alert Explain
Decode an existing SigNoz alert's configuration into a plain-language
explanation. The skill is read-only and stays focused on the rule
itself: what it watches, when it fires, where it notifies. A single
line of fire-frequency data is included to ground the explanation, but
this skill does not investigate any specific fire; that is
signoz-investigating-alerts's job.
Prerequisites
This skill calls SigNoz MCP server tools (signoz_get_alert,
signoz_list_alert_rules, signoz_get_alert_history). Before running
the workflow, confirm the signoz_* tools are available. If they are
not, run signoz-mcp-setup first to initialize or repair the MCP connection.
Do not guess at alert configuration from the rule name alone.
When to use
Use this skill when the user wants to:
- Understand or interpret an existing alert rule.
- Confirm what signal an alert watches and at what threshold.
- Audit whether an alert is reasonably configured.
- Translate raw alert JSON into operational language.
Do NOT use when the user wants to:
- Create a new alert →
signoz-creating-alerts. - Diagnose why an alert fired or correlate signals around a fire window
→
signoz-investigating-alerts. - Modify an existing alert → call
signoz_update_alertdirectly.
Required inputs
| Input | Required | Source if missing |
|---|---|---|
| Alert identifier (rule ID or name) | yes | $ARGUMENTS, recent context, or fuzzy match |
If the input is missing or ambiguous, this skill is best-effort (not strict; read-only operations are cheap to recover from):
- Call
signoz_list_alert_rules, paginate through every page, and find the closest name match. - State the interpretation in the response: "Interpreting your request as alert 'High Error Rate - Checkout' (id 42). If you meant a different one, tell me the name or id."
- Proceed with the explanation. The user can correct after.
Workflow
Step 1: Resolve the alert
If the user provided a rule ID (UUID or legacy numeric ID), skip to Step 2. Otherwise:
What ships with it
2 files 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.
- 12d ago First seen · 408 lines · 136 tokens per session scan A e862dcd3d6b6
signoz-explaining-alerts is a skill published in the GitHub repository SigNoz/agent-skills (16 stars, last pushed 9d ago), licensed MIT. It adds 136 tokens to every session and 4,880 once invoked, about $0.0007 per session on Opus 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.
Other skills, from other repositories
agent-observability
Instrument an LLM agent so failures are diagnosable, traces are replayable, and evals can run against production data. Use when the user is moving an agent past prototype and mentions tracing, spans, OpenTelemetry, LangSmith, Langfuse, Arize, OpenLLMetry, structured logs, GenAI semantic conventions, or asks "how do I…
documentation-and-adrs
Records decisions and documentation. Use when you need to document an architecture decision (ADR) or the reasoning behind a design choice, when changing public APIs, shipping features, or when you need to record context that future engineers and agents will need to understand the codebase.
idea-refine
Refines raw ideas into sharp, actionable concepts through structured divergent and convergent thinking. Use when an idea is still vague, when you need to stress-test assumptions before committing to a plan, or when you want to expand options before converging on one. Triggers on "ideate", "refine this idea", or…
chinese-git-workflow
A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.
chinese-documentation
A Chinese technical-documentation style guide covering spacing, punctuation, numbers, terminology, and links when Chinese and English appear together.
skillshare-implement-feature
Implement a feature from a spec file or description using TDD workflow. Use this skill whenever the user asks to: add a new CLI command, implement a feature from a spec, build new functionality, add a flag, create a new internal package, or write Go code for skillshare. This skill enforces test-first development…