Results for “alert-remediation”

Use to turn a one-off support search into a standing monitor or alert that stays useful instead of being muted within a fortnight. Trigger for "alert me when a customer mentions X", "notify the team when complaints spike", "keep watching for this", "set up a daily monitor for", turning an ad-hoc sweep into something recurring, or an existing alert nobody reads any more.

Repairs failed task verification by choosing a strategy: retry with adjustments, decompose into sub-tasks, prune infeasible tasks, or escalate to the user.

Reduces SOC alert fatigue by tuning detection rules, consolidating duplicate alerts, implementing risk-based alerting, and measuring alert quality metrics to maintain analyst effectiveness.

Error Recovery Playbook

Inspects a skill's SKILL.md and its observations/runs.md log, identifies failure patterns, and proposes a targeted amendment to improve the skill. Trigger on: "improve this skill", "fix this skill", "update this skill", "why does X keep failing", "this skill is wrong", "add this to the skill", or automatically when observations/<skill-name>/runs.md contains 3 or more failure entries. Outputs the amendment as a diff the user can review before applying. Records the amendment rationale in observations/<skill-name>/runs.md after user confirmation.

Alert design and on-call practices — severity, runbooks, SLO burn-rate alerting, escalation. Use when designing alerts, writing runbooks, reducing alert fatigue, setting up escalation policies, implementing SLO-based alerting, or improving on-call processes.

Diagnose and fix Vue 3 runtime errors, warnings, async failures, and SSR/hydration issues with targeted debugging guides.

Trigger or resolve a PagerDuty incident for on-call escalation

Creates safety alert decks with hazard stripes, tiered cards, and policy code blocks for incident reviews and risk communication.

Generates specific, implementable fixes for each vulnerability finding, producing code patches, configuration changes, dependency updates, and IaC fixes with before/after code and verification steps.

Runbook skill for failures: cron error, PA failure, cascade, gateway disconnect, semantic DB stale. Walks: detect → classify → diagnose → notify → log. Replaces ad-hoc failure handling. Triggers: "cron failed", "X is broken", "cascade", "incident", "gateway down", "PA failure".

skill-trigger-reminders

Autonomously repairs failed task verification by choosing retry, decompose, prune, or escalate strategies before surfacing to the user.

Use when paired-end reads need to be reordered so mates appear consecutively, or when preparing BAM files for featureCounts by adding dummy reads for singletons.

Use when tuning RL reward function weights, fixing reward hacking, or addressing P&L gradient issues

Resume an interrupted AgenTeam run with verify-first strategy.

friendly-notifications

Updates AGENTS.md after a repeated verified failure. Do not use for one-off preferences or speculative rules.

Mitigate a production incident or urgent regression first, then route to root-cause remediation and a postmortem.