SigNoz

Initialize or repair SigNoz MCP server configuration for Agent Plugins v1, Claude Code, Codex, Cursor, VS Code/GitHub Copilot, Claude Desktop, Gemini CLI, Devin CLI, Grok Build, Windsurf, Zed, Antigravity CLI, OpenCode, or another MCP client. Use this skill…

Create a new SigNoz dashboard from a natural-language intent: import a curated template (PostgreSQL, Redis, JVM, k8s, hostmetrics, APM, LLM, etc.) when one fits, or build a custom dashboard from scratch with metric / trace / log panels. Make sure to use this…

Create a new SigNoz alert rule from a natural-language intent: threshold, anomaly, log-volume, error-rate, latency, or absent-data alerts across metrics, logs, traces, and exceptions. Make sure to use this skill whenever the user says "alert me when…",…

Describe what an existing SigNoz alert rule does in plain language: the signal it watches, the threshold and evaluation behavior, the notification routing, and a one-line fire-frequency summary so the user knows whether the alert has been active. Make sure to…

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 whenever the user asks "explain this dashboard", "what does my [X] dashboard show", "walk…

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 sure to use this skill whenever the user asks "show me error rates", "query logs for timeout errors",…

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 around the fire window, and rank likely causes. Make sure to use this skill whenever the user asks…

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", "save this filter", "bookmark this search", "list my saved views", "show me views for…

Triage a reported bug against terraform-provider-signoz: reproduce it, decide whether it is real and where the defect actually lives, add the coverage that proves it, document the shape in the pattern catalog, and hand over a suggested upstream fix. Use…

Regenerate and validate the provider's Terraform Registry documentation, add Example Usage / Import examples for a resource, or author a guide (getting started, authentication, or a vN→vN+1 migration guide). Use this whenever the task touches `docs/`,…

Run the end-to-end integration suite (spins up a real SigNoz via foundry, drives Terraform against a locally-built provider, asserts no drift), test a resource change against a live server, add or debug a `tests/testdata/` scenario, or investigate a…

Set up SigNoz primus for this repo — clone it to a location the user picks (default `.primus` at the repo root) and export `PRIMUS_HOME`. Use when primus is not set up: `PRIMUS_HOME` is unset, `make -f "$PRIMUS_HOME/…" help` fails, or the user says "set up…

End-to-end workflow for adding a new Terraform resource + data source to terraform-provider-signoz via the skaff OpenAPI codegen pipeline. Use this whenever the task is to "add", "create", "generate", "scaffold", or "wire up" a new `signoz_<name>`…

Run the ENTIRE skaff codegen pipeline deterministically from an OpenAPI spec, via a bundled script — every declared resource, all steps in the required order (types → schemas → apitypes → client → flex → services → convertors last). Use whenever you need to…

Re-run the full skaff codegen pipeline against the latest upstream SigNoz OpenAPI spec to catch up on spec drift, then open a PR with the regenerated code + docs. Use this when the task is "the upstream openapi spec changed", "regenerate the provider from the…

Review SigNoz documentation pull requests — post inline findings, verify OpenTelemetry technical accuracy with sources, decide add-to-onboarding labeling, and write a concise checklist-based summary. Use when asked to review docs PRs, check documentation…

Review SigNoz frontend pull requests for duplication, architecture, App Router best practices, performance, maintainability, and accessibility. Use when asked to review JS/TS/React/Next.js changes, check components or hooks, evaluate frontend code quality, or…

Create new SigNoz feature pages following established architecture, shared components, and design patterns. Use when asked to "create a feature page", "build a landing page", "new product page", "scaffold a page like trace-funnels", or any request to build a…

Review SigNoz feature pages and components for visual design quality — hierarchy, typography, spacing, color, and polish. Use when asked to "review this page visually", "make this look better", "improve the design", "fix the UI", audit visual consistency, or…

Run the ENTIRE skaff operator codegen pipeline deterministically, via a bundled script — every kind declared in skaff.yml, all four generators in the required order (types → objects → adapters scaffold → controllers), then controller-gen through primus so…

Set up SigNoz primus for this repo — clone it to a location the user picks (default `.primus` at the repo root) and export `PRIMUS_HOME`. Use when primus is not set up: `PRIMUS_HOME` is unset, `make -f "$PRIMUS_HOME/…" help` fails, or the user says "set up…

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 when refactoring away from Redux/Context, moving state to the right store, or when the user asks to…

Create and update Storybook stories and MDX docs for UI components that have subcomponents and presets. Use when adding new components, subcomponents, or presets to the design system, or when wiring MDX Controls so each piece has its own props table.