regenlisted

Read Fluidify Regen incidents and extract the join keys needed to pivot from an incident into its underlying OTel telemetry. Regen is a self-hosted incident / on-call tool with a REST API but no MCP server; this agent makes incidents first-class and emits a ready-to-run SigNoz filter hint -- the incident side of the incident <-> telemetry loop (SigNoz is the telemetry side). TRIGGER when: user asks about Regen incidents, on-call/paging state, "what's on fire", incident triage, ack/resolve an incident, or invokes "/regen"; or wants the service.name + labels + time window to feed into SigNoz. DO NOT TRIGGER when: user is working on the regen agent code itself; or wants to query the telemetry directly (use the signoz skill -- regen hands off to it).
DROOdotFOO/agent-skills · ★ 1 · AI & Automation · score 75

Install: claude install-skill DROOdotFOO/agent-skills

# Regen Incident reader + correlation extractor for [Fluidify Regen](https://github.com/FluidifyAI/Regen) (self-hosted, AGPLv3 on-call tool). Regen ships a REST API but no MCP server, so this agent reads incidents first-class and extracts the keys to pivot into SigNoz telemetry. Symmetric with the `signoz` skill: **regen answers "what broke and when"; signoz answers "why," from the traces/metrics/logs.** ## What You Get - Read incidents and ingested alerts (with their `labels`) and timelines - `regen_correlation_keys` -- extracts `service.name`, correlation labels (`chain`, `role`, `address`, `intent_id`, ...), a time window, and a ready-to-run SigNoz filter hint - Optional write tools (ack / resolve / update) behind an explicit flag ## The mini-axol deployment - `REGEN_BASE_URL` = `http://mini-axol.tail9b2ce8.ts.net:3302` -- **Tailscale must be up** (a connection failure is almost always a down tailnet). - Runs in **open mode** behind the Tailscale ACL (Regen OSS falls through to open mode when no cookie/SAML is configured), so no secret is needed -- only `REGEN_BASE_URL`. Guardrail: do not create a Regen user or enable SAML, or open mode closes and the wrapper breaks. - Alerts originate from SigNoz on the same host and carry `service.name`, `chain`, `role`, etc. -- the labels that make the SigNoz pivot exact. ## MCP tools Read (always available): | Tool | Description | | --- | --- | | `regen_list_incidents` | List incidents; filter by `status`, `severi