Write Flare Alert Rules and SLO Burn-Rate Alerts

    1

    Choose the right Flare alert type, set threshold, window and noise controls, define SLO burn-rate alerts, and ship rules as reviewable JSON with dry-run and test before anything pages.

    Free

    Security scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Write Flare Alert Rules and SLO Burn-Rate Alerts

    Example session with this skill installed

    Alert me when the checkout API error rate goes up. Page on-call if it's bad, Slack if it's just elevated.

    • Read your context and instructions
    • Compiled the write flare alert

    Proposed two rules: checkout-errors-high (exception/log count, Critical, pages the on-call channel) and checkout-errors-elevated (Warning, Slack). Both use a 5-minute window, 15-minute cooldown, and a recovery threshold so they do not flap. Rules written to alerts/checkout.json, dry-run clean (2 create, 0 error). Tested with flare alerts test: observed values and thresholds shown. Nothing was sent to any channel; say the word and I will run send-test.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Turn "tell me when X breaks" into well-formed alert rules in a self-hosted Flare instance, without noisy pages and without sending anything real until you say so.

    What your agent will do

    • Pick the right alert type for the problem: log count, metric threshold, exception count, anomaly, SLO burn rate, release errors or crash-free sessions, and explain why.
    • Set threshold, window, cooldown and severity sensibly, then add only the noise controls that earn their place: recovery threshold, minimum data points, absent-data alerting, maintenance windows, evaluation interval.
    • Set up SLO burn-rate alerts the standard multi-window way (fast burn pages, slow burn warns) and explain the error-budget maths.
    • Write the rules as reviewable JSON (channels referenced by name), validate with flare alerts import --dry-run, and check them against live data with flare alerts test, which sends nothing.
    • Keep rules in git with flare alerts export/import or the whole configuration with flare config export/apply.
    • Wire notification channels (webhook/Slack, Telegram, email, PagerDuty, Teams, Discord) and only send a real test notification after asking.

    Good to know

    • Free. Rule examples come from Flare's API models; the skill insists on a dry run and a test before trusting them.
    • Creating, importing or applying rules changes your Flare instance. The skill shows you the plan first.

    Rule JSON examples are derived from Flare's API request models and were not run against a live instance; the skill makes the agent validate every rule with flare alerts import --dry-run and flare alerts test before relying on it. SLO objects themselves are created in the dashboard (or a config file exported from an existing SLO); this skill does not invent an SLO file format. Flare evaluates by polling, so alerts can lag by one poll interval plus ingest latency, and one rule produces one aggregate value, not one incident per group.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Free forever

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 14 days ago

    • Free with an Agensi account

    Requires

    Flare instance
    Flare CLI
    Notification channel

    Permissions

    Terminal / Shell
    Listed14 days ago

    What's inside

    Frequently Asked Questions

    Choose the right Flare alert type, set threshold, window and noise controls, define SLO burn-rate alerts, and ship rules as reviewable JSON with dry-run and test before anything pages.

    This skill uses the open SKILL.md standard. Use it through an MCP-compatible agent connected to Agensi, and check the compatibility information on this page for confirmed agents and required capabilities.

    Connect your AI agent to Agensi through MCP, then ask it to use Write Flare Alert Rules and SLO Burn-Rate Alerts on your task. Your agent loads the latest approved version each time. Paid skills require a purchase or active subscription. Skill files are not available for download; your licence does not allow you to save, copy or export any part of a skill.

    New in DevOps & Cloud