Humanize Kimi Output with Deno: A Prometheus Alert Annotation Linter + 5 Free Tools (2026) A developer built alertlint.ts, a single-file Deno/TypeScript linter that checks the summary and description annotations in Prometheus alerting rules for filler phrases, missing template variables, placeholder text and other pager-unfriendly patterns, and can optionally call Moonshot AI's Kimi model via its OpenAI-compatible Chat Completions API to draft annotations before linting them. The tool uses explicit Deno permissions (read and env for linting, plus net for draft mode), returns exit codes 0/1/2 for clean, findings and errors, and was tested against the live endpoint, which returned 401 errors for invalid and missing API keys. Tested 2026-11-16. Disclosure: I work on UnAIMyText, and the 3 spot in the tool list is my own ranking. Copy and modify the linter however you like. Black Friday is the week our alerts actually matter. Last year, at 3 a.m. on the Saturday after Thanksgiving, my phone lit up with this: This alert indicates that the checkout service is currently experiencing a critical issue requiring immediate attention. Which checkout pods? How bad? What should I look at first? The summary didn't say, and there was no runbook link. Months earlier someone had asked a model to "write annotations for our alerts," and all 60 of our rules read like that. This year I wanted a check in CI that catches annotations like that before they reach a pager. It's one TypeScript file run by Deno. It lints summary and description in Prometheus rule files, and with --draft it asks a Kimi model from Moonshot AI to write the two annotations for a new alert, then lints what comes back. Moonshot's Chat Completions API reference https://platform.moonshot.ai/docs/api/chat is OpenAI-shaped: POST https://api.moonshot.ai/v1/chat/completions with Authorization: Bearer $MOONSHOT API KEY plus the usual messages . I default to kimi-k3.1-pro , the model in the docs' examples, and MOONSHOT MODEL overrides it. From the docs: response format: {"type": "json object"} forces a JSON object, but the docs say you must describe the fields in the prompt. The system message names summary and description . reasoning effort of low , high or max default choices 0 .message.content . The reasoning arrives separately in reasoning content , which I ignore. I hit the real endpoint with a made-up key and got a 401 with "Invalid Authentication" . Without the header it's also 401 , with "Incorrect API key provided" . The linter exits 2 for both. Deno runs TypeScript as is, with fetch built in. The only import is jsr:@std/yaml@1.3.0 , pinned. Permissions are explicit: lint mode needs -R read and -E env ; draft mode adds -N net . Per alerting rule: severity label or runbook url , and runbook URLs that aren't http s {{ $labels. }} or {{ $value }} , so the page can't tell you which instance or how bad robust , comprehensive , proactively , leverage , in order to , ensure that , critical issue , immediate attention , currently experiencing , seamless TODO , TBD , FIXME and insert ... leftovers, and {{ without a matching }} The period rule is house style. Prometheus doesn't care, but the official examples write summaries as headlines and descriptions as sentences. Drafts skip the severity and runbook checks, since the model doesn't write those. Exit codes: 0 when everything passes, 1 when there are findings, and 2 for usage mistakes, unreadable files, invalid YAML, files with no alerting rules, network failures and API errors. // alertlint.ts checks the summary and description annotations in Prometheus // alerting rules, or asks a Kimi model Moonshot AI to draft them and checks the draft. // // Usage: // deno run -RE alertlint.ts rules.yml more.yml lint rule files // cat rules.yml | deno run -RE alertlint.ts - read from stdin // deno run -RE -N alertlint.ts --draft DiskAlmostFull "notes..." // add --json for machine-readable output // // Exit: 0 clean, 1 lint findings, 2 usage/parse/network/API errors import { parse } from "jsr:@std/yaml@1.3.0"; const MAX SUMMARY = 80; const MAX DESC WORDS = 60; const FILLER = /\b seamless ly ?|robust|comprehensive|proactive ly ?|leverag e|es|ing |ensures? that|in order to|critical issue|immediate attention|currently experiencing \b/gi; const OPENER = /^ this alert|please note|it appears|seems |heads up|attention \b/i; const HEDGE = /\b may|might|could potentially|possibly \b/i; const EMOJI = /\p{Extended Pictographic}/u; const PLACEHOLDER = /\b TODO|TBD|FIXME \b|\ insert ^\ |description \ /i; const TEMPLATE VAR = /\{\{\s \$labels\.\w+|\$value|humanize\w \s+\$value /; type Finding = { alert: string; issue: string }; type Rule = { alert?: string; labels?: Record