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-dashboardsgit 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-dashboards)<a href="https://agentmods.dev/skills/signoz/agent-skills/signoz-explaining-dashboards"><img src="https://agentmods.dev/badge/skills/signoz/agent-skills/signoz-explaining-dashboards/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-dashboards"><img src="https://agentmods.dev/badge/skills/signoz/agent-skills/signoz-explaining-dashboards.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00134 | $0.02449 |
| Opus 5 | $0.00067 | $0.01224 |
| Sonnet 5 | $0.00027 | $0.00490 |
| Haiku 4.5 | $0.00013 | $0.00245 |
Grade A, and why
signoz-explaining-dashboards 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 — 214 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dashboard Explain
Prerequisites
This skill calls SigNoz MCP server tools (signoz_get_dashboard,
signoz_list_dashboards). Before running the workflow, confirm the
signoz_* tools are available. If they are not, the SigNoz MCP server
is not installed or configured; run signoz-mcp-setup first to initialize or
repair the MCP connection. Do not guess at a dashboard's contents from its
title alone.
When to use
Use this skill when the user asks to:
- Understand, explain, or interpret an existing dashboard
- Get a walkthrough of what panels show and why they matter
- Know what to watch for or what healthy/unhealthy looks like on a dashboard
- Understand the variables, filters, or queries on a dashboard
Do NOT use when:
- User wants to modify an existing dashboard →
signoz-modifying-dashboards
Instructions
Step 1: Identify the target dashboard
Use a supplied id or a dashboard resource that includes its id directly.
For any name-only request, call signoz_list_dashboards and resolve the name to
an id, matching on spec.display.name. Cover the whole listing: narrow with
the filter argument, re-run unfiltered when it comes back empty, and page by
raising offset by limit until you have covered total. Never pass a
dashboard name to signoz_get_dashboard or conclude it is missing from the
first page.
If multiple dashboards match, present the candidates and ask which one to explain.
Step 2: Fetch the full dashboard configuration
Call signoz_get_dashboard with the dashboard id. This is mandatory; you
need the complete JSON to explain the dashboard accurately. Never guess based on
the title alone.
Examine the response to understand:
spec.display.name,.description,tags: the dashboard identity and author-provided contextspec.variables: dashboard-level filters (dropdowns the user can change)spec.panels(a map keyed by panel id): the panels, their plugin kinds, titles, and queriesspec.layouts: Grid entries placing panels in the 12-column grid viacontent.$ref- each Grid's
spec.display.title: the section a panel belongs to
What ships with it
3 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 · 214 lines · 134 tokens per session scan A 10498f9ce62d
signoz-explaining-dashboards is a skill published in the GitHub repository SigNoz/agent-skills (16 stars, last pushed 10d ago), licensed MIT. It adds 134 tokens to every session and 2,449 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…