errors-query
Load BEFORE querying Better Stack exception or error-pattern data with SQL - exception counts, trends, first/last occurrence, affected users, raw stack traces. Contains instructions for querying errors/exceptions.
Install
With your agent
Install OMGSkills skill "betterstackhq/claude-plugin:skills/errors-query" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/BetterStackHQ/claude-plugin /tmp/claude-plugin && ln -s /tmp/claude-plugin/skills/errors-query ~/.claude/skills/errors-queryFrom README
Querying exceptions (Errors sources) Where the query runs Better Stack runs SQL in two places, and the query text differs: Dashboard charts and chart alerts (addcharttodashboard, editchart, createchartalert): write the query as this skill shows it, with the template variables {{source}}, {{time}}, {{starttime}} and {{endtime}}. The dashboard resolves them. Chart queries always read the source's metrics collection. Ad-hoc queries (query, renderchart): there are no template variables. First call the help tool for the data type with the source ID (queryhelp for logs and spans, metricsqueryhelp for metrics, errorsqueryhelp for errors): it names the source's collections and the table to pass. Put the collection where {{source}} stands (e.g.
More from this repo
chart-alerts
Guide for creating and managing Better Stack chart alerts.
chart-generation
Complete reference for chart types, units, and settings on Better Stack dashboards.
chart-styling
Better Stack chart styling and advanced settings reference - series colors and order, number chart coloring thresholds,...