Signoz Skills

Migrate Redux or React Context to the correct state option (React Query for server state, nuqs for URL/shareable state, Zustand for global client state). Use…

Migrate Redux or React Context to the correct state option (React Query for server state, nuqs for URL/shareable state, Zustand for global client state). Use…

Use this skill when the user asks for SigNoz queries involving:

Write ClickHouse queries for SigNoz dashboards over OpenTelemetry logs and traces. Use this skill whenever the user asks for SigNoz ClickHouse queries for logs…

Create a new SigNoz alert rule from a natural-language intent — threshold, anomaly, log-volume, error-rate, latency, or absent-data alerts across metrics,…

Build a SigNoz alert from a user's natural-language intent. The skill targets two consumers: an autonomous AI SRE agent that runs without a human in the loop, and a human at a Claude Code / Codex / Cursor prompt. Both go through the same flow — the human just gets a chance to intervene at the preview step.

Create a new SigNoz dashboard from a natural-language intent — import a curated template (PostgreSQL, Redis, JVM, k8s, hostmetrics, APM, LLM, etc.) when one…

This skill calls SigNoz MCP server tools ( signoz:signoz_create_dashboard , signoz:signoz_list_dashboards , signoz:signoz_list_dashboard_templates , signoz:signoz_import_dashboard , signoz:signoz_list_metrics , signoz:signoz_get_field_values , signoz:signoz_aggregate_logs , signoz:signoz_aggregate_traces , etc.). Before running the workflow, confirm the signoz:signoz_* tools are available. If they are not, the SigNoz MCP server is not installed or configured — stop and direct the user to set...

Use this skill first whenever the user asks about SigNoz instrumentation, OpenTelemetry setup, querying, dashboards, alerts, troubleshooting, self-hosted…

Use this skill first whenever the user asks about SigNoz instrumentation, OpenTelemetry setup, querying, dashboards, alerts, troubleshooting, self-hosted…

Describe what an existing SigNoz alert rule does in plain language — the signal it watches, the threshold and evaluation behavior, the notification routing,…

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.

This skill calls SigNoz MCP server tools ( signoz:signoz_get_dashboard , signoz:signoz_list_dashboards ). Before running the workflow, confirm the signoz:signoz_* tools are available. If they are not, the SigNoz MCP server is not installed or configured — stop and direct the user to set it up: https://signoz.io/docs/ai/signoz-mcp-server/ . Do not guess at a dashboard's contents from its title alone.

Explain what an existing SigNoz dashboard shows in plain operational language — the panels, queries, variables, and what to watch for on each. Make sure to use…

This skill calls SigNoz MCP server tools heavily ( signoz:signoz_execute_builder_query , signoz:signoz_query_metrics , signoz:signoz_search_logs , signoz:signoz_search_traces , signoz:signoz_aggregate_logs , signoz:signoz_aggregate_traces , signoz:signoz_get_field_keys , signoz:signoz_get_field_values , signoz:signoz_list_metrics , signoz:signoz_list_services , signoz:signoz_get_service_top_operations , signoz:signoz_get_trace_details ). Before running the workflow, confirm the...

Generate, write, or run an ad-hoc query against SigNoz observability data — metrics, logs, or traces — without wrapping it in a dashboard panel or alert. Make…

Diagnose why a SigNoz alert fired by correlating the alert's own signal with neighbor signals (error rate, latency, throughput, CPU/memory), traces, and logs…

Diagnose why a SigNoz alert fired. The skill correlates the alert's own signal with neighbor signals around the fire window, and surfaces a ranked list of likely causes with supporting evidence. It is the companion to signoz-explaining-alerts — explain decodes the rule statically; investigate diagnoses a specific incident.

Use when the user wants to create, list, get, update, rename, or delete a SigNoz saved Explorer view. Trigger on phrases like "save this query as a view",…

Create, read, update, and delete SigNoz saved Explorer views via the SigNoz MCP server. A saved view is a reusable snapshot of an Explorer query on the Logs, Traces, or Metrics page — name + filters + panel type, scoped to one sourcePage . They are not dashboards and not alerts.

Initialize or repair SigNoz MCP server configuration for Claude Code, Codex, Cursor, VS Code/GitHub Copilot, Claude Desktop, Gemini CLI, Devin CLI, Windsurf,…

Modify an existing SigNoz dashboard — add or remove panels, edit a panel's query, threshold, or unit, rename the dashboard, change a panel type (graph ↔ table…

This skill calls SigNoz MCP server tools ( signoz:signoz_get_dashboard , signoz:signoz_update_dashboard , signoz:signoz_list_dashboards , signoz:signoz_list_metrics ). Before running the workflow, confirm the signoz:signoz_* tools are available. If they are not, the SigNoz MCP server is not installed or configured — stop and direct the user to set it up: https://signoz.io/docs/ai/signoz-mcp-server/ . Do not fall back to raw HTTP calls or hand-edit dashboard JSON without the MCP tools.

Investigate and reduce SigNoz telemetry ingestion cost and metric cardinality across metrics, logs, and traces. Find what drives SigNoz spend (via the Cost…

Use official signoz.io documentation and API references only. Ground every answer in fetched docs content and cite the canonical docs URL.

Look up information in SigNoz documentation. Make sure to use this skill whenever the user asks "how do I", "where in the docs", "what does the docs say…

Run the full end-to-end observability setup for a service after its telemetry is already flowing into SigNoz — sequence SLI/SLO capture, data exploration…

Run the full end-to-end observability setup for a service after its telemetry is already flowing into SigNoz — sequence SLI/SLO capture, data exploration…

Use this skill when the user asks for SigNoz queries involving:

Write raw ClickHouse SQL for a SigNoz dashboard panel — timeseries, value, or table widgets that the builder UI cannot express (custom joins, window functions,…