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-creating-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-creating-dashboards)<a href="https://agentmods.dev/skills/signoz/agent-skills/signoz-creating-dashboards"><img src="https://agentmods.dev/badge/skills/signoz/agent-skills/signoz-creating-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-creating-dashboards"><img src="https://agentmods.dev/badge/skills/signoz/agent-skills/signoz-creating-dashboards.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.00171 | $0.06363 |
| Opus 5 | $0.00086 | $0.03181 |
| Sonnet 5 | $0.00034 | $0.01273 |
| Haiku 4.5 | $0.00017 | $0.00636 |
Grade A, and why
signoz-creating-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 11d 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 — 498 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dashboard Create
Prerequisites
This skill calls SigNoz MCP server tools (signoz_create_dashboard,
signoz_list_dashboards, signoz_list_dashboard_templates,
signoz_import_dashboard, signoz_get_dashboard,
signoz_update_dashboard, signoz_list_metrics,
signoz_get_field_keys, signoz_get_field_values,
signoz_aggregate_logs, signoz_aggregate_traces, etc.).
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 fall back to raw HTTP calls or fabricate dashboard JSON
without the MCP tools.
When to use
Use this skill when the user wants to:
- Create, set up, or build a new dashboard.
- "Monitor" or "set up observability" for a service, database, infrastructure component, or AI/LLM platform.
- Import a curated dashboard template.
- Visualize a set of metrics / traces / logs together on one screen.
Do NOT use when the user wants to:
- Modify an existing dashboard →
signoz-modifying-dashboards. - Understand what an existing dashboard shows →
signoz-explaining-dashboards. - Run a one-off query without persisting it →
signoz-generating-queries.
Required inputs (strict)
Dashboard creation is a write operation. Guessing here clutters the shared workspace with empty or wrongly-scoped dashboards someone else has to clean up. The skill enforces a soft input contract; most fields have sensible defaults, but a few cannot be guessed:
| Input | Required | Source if missing |
|---|---|---|
| Dashboard intent (NL goal) | yes | $ARGUMENTS or recent user turn |
| Technology / domain (e.g. PostgreSQL, Redis, "payment pipeline") | yes | parse from intent; otherwise ask |
| Confirmation to create (plus the modify-or-create choice when duplicates exist) | yes | ask the user (Step 2); still required with zero duplicates and under stated urgency |
| Resource scope for custom builds (service / namespace / cluster) | yes for custom builds | discover via signoz_get_field_keys + signoz_get_field_values; fall back to a dashboard variable |
| Specific metrics / signals for custom builds | inferred | derive from technology + MCP signoz://dashboard/* resources; surface in preview |
| Layout | inferred | apply defaults (see "Defaults" below) |
What ships with it
5 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.
- 11d ago First seen · 498 lines · 171 tokens per session scan A 3518949ffd11
signoz-creating-dashboards is a skill published in the GitHub repository SigNoz/agent-skills (16 stars, last pushed 9d ago), licensed MIT. It adds 171 tokens to every session and 6,363 once invoked, about $0.0009 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…